From 21878eea72d59d7d2869fb3d58937585a9395ce9 Mon Sep 17 00:00:00 2001 From: Automated Date: Tue, 1 Mar 2022 21:43:54 +0000 Subject: [PATCH] gcloud: Tue Mar 1 21:43:54 UTC 2022 --- gcloud/_version | 6 + gcloud/access-context-manager/policies/create | 4 +- gcloud/active-directory/domains/create | 5 +- gcloud/active-directory/domains/trusts/create | 7 +- gcloud/active-directory/domains/trusts/update | 6 +- gcloud/active-directory/domains/update | 8 +- gcloud/ai-platform/models/delete | 4 +- gcloud/ai/custom-jobs/create | 8 +- gcloud/ai/endpoints/create | 4 +- gcloud/ai/endpoints/deploy-model | 4 +- gcloud/ai/endpoints/predict | 3 +- gcloud/ai/endpoints/raw-predict | 4 +- gcloud/ai/endpoints/undeploy-model | 3 +- gcloud/ai/endpoints/update | 3 +- gcloud/ai/index-endpoints/create | 6 +- gcloud/ai/index-endpoints/undeploy-index | 3 +- gcloud/ai/indexes/create | 6 +- gcloud/ai/indexes/update | 6 +- gcloud/ai/models/upload | 7 +- .../access-context-manager/policies/create | 4 +- .../active-directory/domains/backups/delete | 3 +- .../active-directory/domains/backups/update | 3 +- gcloud/alpha/active-directory/domains/create | 5 +- .../active-directory/domains/trusts/create | 7 +- .../active-directory/domains/trusts/update | 6 +- gcloud/alpha/active-directory/domains/update | 8 +- gcloud/alpha/ai-platform/explain | 2 +- gcloud/alpha/ai-platform/models/delete | 4 +- gcloud/alpha/ai/custom-jobs/create | 7 +- gcloud/alpha/ai/endpoints/create | 3 +- gcloud/alpha/ai/endpoints/deploy-model | 4 +- gcloud/alpha/ai/endpoints/predict | 3 +- gcloud/alpha/ai/endpoints/raw-predict | 4 +- gcloud/alpha/ai/endpoints/undeploy-model | 3 +- gcloud/alpha/ai/endpoints/update | 3 +- gcloud/alpha/ai/index-endpoints/create | 6 +- .../alpha/ai/index-endpoints/undeploy-index | 4 +- gcloud/alpha/ai/indexes/create | 5 +- gcloud/alpha/ai/indexes/update | 6 +- gcloud/alpha/ai/models/upload | 7 +- gcloud/alpha/anthos/auth/login | 2 +- .../apis/remove-iam-policy-binding | 3 +- .../gateways/remove-iam-policy-binding | 5 +- gcloud/alpha/apigee/products/update | 2 +- gcloud/alpha/app/ssl-certificates/create | 4 +- gcloud/alpha/app/ssl-certificates/update | 4 +- gcloud/alpha/artifacts/repositories/help | 9 +- gcloud/alpha/asset/feeds/create | 7 +- gcloud/alpha/asset/feeds/update | 4 +- gcloud/alpha/auth/activate-service-account | 4 +- gcloud/alpha/auth/configure-docker | 22 ++- gcloud/alpha/bigtable/backups/create | 9 +- gcloud/alpha/bigtable/backups/update | 4 +- gcloud/alpha/bms/instances/update | 2 +- gcloud/alpha/bms/networks/update | 4 +- gcloud/alpha/bms/nfs-shares/update | 4 +- gcloud/alpha/bq/datasets/create | 4 +- gcloud/alpha/bq/datasets/delete | 2 +- gcloud/alpha/bq/datasets/describe | 2 +- gcloud/alpha/bq/datasets/list | 2 +- gcloud/alpha/bq/datasets/update | 2 +- gcloud/alpha/bq/jobs/cancel | 2 +- gcloud/alpha/bq/jobs/describe | 2 +- gcloud/alpha/bq/jobs/list | 2 +- gcloud/alpha/bq/tables/create | 8 +- gcloud/alpha/bq/tables/delete | 2 +- gcloud/alpha/bq/tables/describe | 2 +- gcloud/alpha/bq/tables/list | 2 +- gcloud/alpha/bq/tables/show-rows | 2 +- gcloud/alpha/bq/tables/update | 7 +- gcloud/alpha/builds/submit | 2 +- .../certificate-manager/certificates/create | 2 +- .../certificate-manager/certificates/update | 2 +- .../certificate-manager/maps/entries/update | 4 +- gcloud/alpha/code/dev | 4 +- gcloud/alpha/compute/addresses/create | 11 +- gcloud/alpha/compute/addresses/update | 4 +- .../backend-services/add-service-bindings | 4 +- .../backend-services/remove-service-bindings | 2 +- gcloud/alpha/compute/disks/create | 28 ++-- .../compute/disks/stop-async-replication | 16 +- .../compute/external-vpn-gateways/update | 3 +- .../compute/firewall-policies/rules/create | 4 +- .../compute/firewall-policies/rules/update | 4 +- gcloud/alpha/compute/firewall-rules/create | 9 +- gcloud/alpha/compute/forwarding-rules/update | 4 +- .../alpha/compute/future-reservations/update | 4 +- .../instance-groups/managed/create-instance | 15 +- .../instance-groups/managed/describe-instance | 3 +- .../instance-groups/managed/list-errors | 2 +- .../instance-groups/managed/list-instances | 2 +- .../instance-groups/managed/update-instances | 5 +- .../instance-templates/create-with-container | 8 +- .../compute/instances/create-with-container | 12 +- .../get-effective-firewalls | 3 +- .../instances/os-inventory/list-instances | 20 +-- gcloud/alpha/compute/instances/set-iam-policy | 5 +- gcloud/alpha/compute/instances/set-scheduling | 2 +- .../compute/instances/update-access-config | 2 +- .../alpha/compute/instances/update-container | 8 +- .../network-edge-security-services/create | 7 +- .../network-edge-security-services/delete | 3 +- .../network-edge-security-services/describe | 3 +- .../network-edge-security-services/update | 8 +- .../associations/create | 16 +- .../associations/delete | 10 +- .../network-firewall-policies/clone-rules | 3 +- .../compute/network-firewall-policies/create | 7 +- .../network-firewall-policies/rules/delete | 3 +- .../network-firewall-policies/rules/describe | 5 +- .../compute/network-firewall-policies/update | 9 +- .../compute/networks/get-effective-firewalls | 3 +- .../alpha/compute/networks/list-ip-addresses | 4 +- gcloud/alpha/compute/networks/list-ip-owners | 16 +- gcloud/alpha/compute/networks/peerings/create | 10 +- gcloud/alpha/compute/networks/peerings/delete | 2 +- .../compute/networks/peerings/list-routes | 5 +- gcloud/alpha/compute/networks/peerings/update | 7 +- .../org-security-policies/rules/create | 4 +- .../org-security-policies/rules/update | 4 +- .../compute/os-config/guest-policies/create | 3 +- .../os-policy-assignment-reports/describe | 2 +- gcloud/alpha/compute/packet-mirrorings/create | 15 +- gcloud/alpha/compute/packet-mirrorings/delete | 4 +- .../alpha/compute/packet-mirrorings/describe | 4 +- gcloud/alpha/compute/packet-mirrorings/update | 10 +- .../compute/public-advertised-prefixes/create | 2 +- .../compute/public-delegated-prefixes/create | 2 +- gcloud/alpha/compute/routers/nats/create | 15 +- .../alpha/compute/routers/nats/rules/create | 6 +- .../alpha/compute/routers/nats/rules/update | 6 +- gcloud/alpha/compute/routers/nats/update | 25 +-- gcloud/alpha/compute/routes/create | 4 +- .../organizations/list-host-projects | 1 + gcloud/alpha/compute/tpus/create | 9 +- .../compute/tpus/execution-groups/create | 17 +- .../compute/tpus/execution-groups/delete | 2 +- .../compute/tpus/execution-groups/resume | 2 +- gcloud/alpha/compute/vpn-gateways/update | 3 +- .../container/backup-restore/backups/create | 12 +- .../container/backup-restore/restores/create | 4 +- .../container/binauthz/attestations/create | 6 +- .../container/binauthz/attestations/list | 6 +- .../binauthz/attestations/sign-and-create | 13 +- .../alpha/container/binauthz/attestors/create | 3 +- .../binauthz/attestors/public-keys/add | 12 +- .../binauthz/attestors/public-keys/remove | 3 +- .../binauthz/continuous-validation/describe | 8 +- .../binauthz/create-signature-payload | 3 +- gcloud/alpha/container/clusters/create | 2 +- gcloud/alpha/container/clusters/update | 2 +- gcloud/alpha/container/hub/cloudrun/apply | 2 +- .../container/hub/config-management/disable | 2 +- .../container/hub/config-management/enable | 2 +- .../container/hub/identity-service/describe | 3 +- .../container/hub/identity-service/disable | 2 +- .../container/hub/identity-service/enable | 2 +- gcloud/alpha/container/hub/ingress/describe | 2 +- gcloud/alpha/container/hub/ingress/disable | 2 +- gcloud/alpha/container/hub/ingress/enable | 2 +- gcloud/alpha/container/hub/ingress/update | 2 +- .../hub/memberships/generate-gateway-rbac | 32 ++-- .../alpha/container/hub/memberships/register | 54 +++--- .../container/hub/memberships/unregister | 8 +- gcloud/alpha/container/hub/mesh/describe | 2 +- gcloud/alpha/container/hub/mesh/disable | 2 +- gcloud/alpha/container/hub/mesh/enable | 2 +- gcloud/alpha/container/hub/mesh/update | 4 +- .../hub/multi-cluster-services/describe | 2 +- .../hub/multi-cluster-services/disable | 3 +- .../hub/multi-cluster-services/enable | 2 +- .../container/hub/service-directory/describe | 2 +- .../container/hub/service-directory/disable | 2 +- .../container/hub/service-directory/enable | 2 +- gcloud/alpha/container/images/add-tag | 14 +- gcloud/alpha/container/images/delete | 4 +- gcloud/alpha/container/images/describe | 12 +- gcloud/alpha/container/node-pools/create | 11 +- gcloud/alpha/container/node-pools/update | 11 +- gcloud/alpha/container/subnets/list-usable | 7 +- gcloud/alpha/data-catalog/crawlers/create | 3 +- gcloud/alpha/data-catalog/entries/create | 7 +- gcloud/alpha/data-catalog/entry-groups/create | 5 +- .../alpha/data-catalog/tag-templates/create | 3 +- .../database-migration/migration-jobs/create | 2 +- .../database-migration/migration-jobs/update | 2 +- .../dataplex/tasks/add-iam-policy-binding | 2 +- gcloud/alpha/dataplex/tasks/create | 10 +- .../dataplex/tasks/remove-iam-policy-binding | 2 +- gcloud/alpha/dataplex/tasks/update | 3 +- .../autoscaling-policies/set-iam-policy | 4 +- gcloud/alpha/dataproc/jobs/submit/hadoop | 4 +- gcloud/alpha/dataproc/jobs/submit/hive | 6 +- gcloud/alpha/dataproc/jobs/submit/pig | 10 +- gcloud/alpha/dataproc/jobs/submit/spark | 3 +- gcloud/alpha/dataproc/jobs/submit/spark-r | 3 +- gcloud/alpha/dataproc/jobs/submit/spark-sql | 6 +- gcloud/alpha/dataproc/jobs/wait | 2 +- .../dataproc/workflow-templates/add-job/help | 9 +- gcloud/alpha/dataproc/workflow-templates/help | 3 +- .../delivery-pipelines/add-iam-policy-binding | 7 +- .../remove-iam-policy-binding | 7 +- .../deploy/targets/add-iam-policy-binding | 5 +- .../deploy/targets/remove-iam-policy-binding | 5 +- .../deployment-manager/deployments/create | 8 +- gcloud/alpha/dialogflow/intents/create | 4 +- gcloud/alpha/dlp/datasources/bigquery/analyze | 2 +- gcloud/alpha/dlp/datasources/bigquery/inspect | 2 +- .../alpha/dlp/datasources/datastore/inspect | 2 +- gcloud/alpha/dlp/datasources/gcs/inspect | 2 +- gcloud/alpha/dlp/images/redact | 3 +- gcloud/alpha/dlp/text/redact | 4 +- gcloud/alpha/dns/dns-keys/list | 3 +- gcloud/alpha/dns/managed-zones/create | 9 +- gcloud/alpha/dns/policies/create | 14 +- gcloud/alpha/dns/record-sets/create | 7 +- gcloud/alpha/dns/record-sets/export | 2 +- gcloud/alpha/dns/record-sets/transaction/add | 8 +- .../alpha/dns/record-sets/transaction/remove | 8 +- gcloud/alpha/dns/record-sets/update | 7 +- gcloud/alpha/dns/response-policies/create | 10 +- .../alpha/dns/response-policies/rules/create | 17 +- gcloud/alpha/dns/response-policies/rules/help | 19 ++- .../alpha/dns/response-policies/rules/update | 12 +- gcloud/alpha/dns/response-policies/update | 11 +- gcloud/alpha/endpoints/quota/create | 26 +-- gcloud/alpha/endpoints/quota/delete | 24 +-- gcloud/alpha/endpoints/quota/update | 28 ++-- .../endpoints/services/add-iam-policy-binding | 7 +- gcloud/alpha/essential-contacts/compute | 3 +- gcloud/alpha/essential-contacts/create | 17 +- gcloud/alpha/essential-contacts/update | 2 +- gcloud/alpha/filestore/instances/create | 10 +- gcloud/alpha/filestore/instances/restore | 6 +- gcloud/alpha/filestore/instances/update | 2 +- gcloud/alpha/filestore/snapshots/create | 4 +- gcloud/alpha/firestore/indexes/fields/list | 7 +- gcloud/alpha/firestore/indexes/fields/update | 6 +- gcloud/alpha/functions/deploy | 33 ++-- gcloud/alpha/game/servers/clusters/create | 10 +- gcloud/alpha/game/servers/clusters/update | 4 +- gcloud/alpha/game/servers/configs/create | 4 +- gcloud/alpha/game/servers/deployments/create | 3 +- gcloud/alpha/iam/list-grantable-roles | 3 +- gcloud/alpha/iam/policies/create | 51 ++++++ gcloud/alpha/iam/policies/delete | 54 ++++++ gcloud/alpha/iam/policies/get | 46 +++++ gcloud/alpha/iam/policies/help | 18 ++ gcloud/alpha/iam/policies/list | 74 +++++++++ gcloud/alpha/iam/policies/update | 59 +++++++ .../alpha/iam/workload-identity-pools/create | 6 +- .../providers/create-aws | 9 +- .../providers/create-oidc | 9 +- .../workload-identity-pools/providers/delete | 4 +- .../providers/describe | 6 +- .../workload-identity-pools/providers/list | 7 +- .../providers/operations/describe | 3 +- .../providers/undelete | 4 +- .../providers/update-aws | 6 +- .../providers/update-oidc | 11 +- .../alpha/iam/workload-identity-pools/update | 6 +- .../alpha/iap/gateway/add-iam-policy-binding | 4 +- .../iap/gateway/remove-iam-policy-binding | 5 +- gcloud/alpha/iap/oauth-brands/create | 2 +- gcloud/alpha/iap/oauth-brands/list | 2 +- gcloud/alpha/iap/settings/get | 2 +- gcloud/alpha/iap/settings/set | 2 +- gcloud/alpha/iap/web/add-iam-policy-binding | 10 +- gcloud/alpha/iap/web/enable | 6 +- gcloud/alpha/iap/web/get-iam-policy | 3 +- .../alpha/iap/web/remove-iam-policy-binding | 13 +- gcloud/alpha/iap/web/set-iam-policy | 10 +- gcloud/alpha/identity/groups/create | 13 +- gcloud/alpha/identity/groups/memberships/add | 2 +- .../memberships/modify-membership-roles | 5 +- gcloud/alpha/identity/groups/search | 7 +- gcloud/alpha/identity/groups/update | 4 +- gcloud/alpha/kms/asymmetric-decrypt | 11 +- gcloud/alpha/kms/asymmetric-sign | 12 +- gcloud/alpha/kms/decrypt | 14 +- .../ekm-connections/add-iam-policy-binding | 4 +- gcloud/alpha/kms/ekm-connections/create | 10 +- gcloud/alpha/kms/ekm-connections/describe | 4 +- .../alpha/kms/ekm-connections/get-iam-policy | 4 +- gcloud/alpha/kms/ekm-connections/help | 4 +- gcloud/alpha/kms/ekm-connections/list | 4 +- .../ekm-connections/remove-iam-policy-binding | 4 +- .../alpha/kms/ekm-connections/set-iam-policy | 4 +- gcloud/alpha/kms/ekm-connections/update | 13 +- gcloud/alpha/kms/encrypt | 7 +- gcloud/alpha/kms/import-jobs/create | 4 +- gcloud/alpha/kms/keys/create | 50 ++---- .../alpha/kms/keys/remove-rotation-schedule | 3 +- gcloud/alpha/kms/keys/set-rotation-schedule | 4 +- gcloud/alpha/kms/keys/update | 33 ++-- gcloud/alpha/kms/keys/versions/create | 12 +- gcloud/alpha/kms/keys/versions/get-public-key | 8 +- gcloud/alpha/kms/keys/versions/import | 8 +- gcloud/alpha/kms/keys/versions/list | 3 +- gcloud/alpha/kms/keys/versions/update | 18 +- gcloud/alpha/kms/mac-sign | 11 +- gcloud/alpha/kms/mac-verify | 11 +- gcloud/alpha/lifesciences/pipelines/run | 5 +- gcloud/alpha/logging/settings/update | 9 +- gcloud/alpha/logging/sinks/create | 15 +- gcloud/alpha/logging/views/update | 3 +- gcloud/alpha/memcache/instances/create | 4 +- gcloud/alpha/metastore/services/import/gcs | 2 +- .../alpha/metastore/services/imports/create | 2 +- gcloud/alpha/ml-engine/explain | 2 +- gcloud/alpha/ml-engine/models/delete | 4 +- gcloud/alpha/ml/language/classify-text | 2 +- gcloud/alpha/ml/speech/recognize | 10 +- gcloud/alpha/ml/speech/recognize-long-running | 6 + gcloud/alpha/ml/vision/detect-text-pdf | 4 +- gcloud/alpha/ml/vision/detect-text-tiff | 4 +- gcloud/alpha/monitoring/channels/create | 16 +- gcloud/alpha/monitoring/channels/list | 7 +- gcloud/alpha/monitoring/channels/update | 2 +- .../internal-ranges/create | 18 +- .../internal-ranges/update | 13 +- .../policy-based-routes/create | 4 +- gcloud/alpha/policy-troubleshoot/iam | 20 ++- gcloud/alpha/pubsub/lite-reservations/create | 3 +- gcloud/alpha/pubsub/lite-reservations/delete | 2 +- .../alpha/pubsub/lite-reservations/describe | 2 +- gcloud/alpha/pubsub/lite-reservations/list | 4 +- .../pubsub/lite-reservations/list-topics | 2 +- gcloud/alpha/pubsub/lite-reservations/update | 3 +- .../alpha/pubsub/lite-subscriptions/ack-up-to | 4 +- gcloud/alpha/pubsub/lite-subscriptions/create | 8 +- gcloud/alpha/pubsub/lite-subscriptions/delete | 2 +- .../alpha/pubsub/lite-subscriptions/describe | 2 +- gcloud/alpha/pubsub/lite-subscriptions/list | 3 +- gcloud/alpha/pubsub/lite-subscriptions/seek | 8 +- gcloud/alpha/pubsub/lite-subscriptions/update | 4 +- gcloud/alpha/pubsub/lite-topics/create | 6 +- gcloud/alpha/pubsub/lite-topics/delete | 2 +- gcloud/alpha/pubsub/lite-topics/describe | 2 +- gcloud/alpha/pubsub/lite-topics/list | 2 +- .../pubsub/lite-topics/list-subscriptions | 2 +- gcloud/alpha/pubsub/lite-topics/update | 3 +- .../subscriptions/add-iam-policy-binding | 4 +- gcloud/alpha/pubsub/subscriptions/create | 14 +- gcloud/alpha/pubsub/subscriptions/update | 11 +- .../recommender/recommendations/describe | 4 +- gcloud/alpha/recommender/recommendations/list | 2 +- .../recommender/recommendations/mark-active | 4 +- .../recommender/recommendations/mark-claimed | 6 +- .../recommendations/mark-dismissed | 5 +- .../resource-config/terraform/init-provider | 2 +- .../alpha/resource-manager/tags/keys/create | 3 +- .../alpha/resource-manager/tags/values/create | 6 +- gcloud/alpha/scc/findings/list | 2 +- gcloud/alpha/scc/settings/services/disable | 2 +- gcloud/alpha/scc/settings/services/enable | 2 +- gcloud/alpha/scc/settings/services/inherit | 2 +- .../scc/settings/services/modules/disable | 2 +- .../scc/settings/services/modules/enable | 2 +- .../scc/settings/services/modules/update | 4 +- gcloud/alpha/scheduler/jobs/create/app-engine | 3 +- gcloud/alpha/scheduler/jobs/create/http | 4 +- gcloud/alpha/scheduler/jobs/create/pubsub | 4 +- gcloud/alpha/services/api-keys/describe | 9 +- gcloud/alpha/services/api-keys/update | 2 +- .../alpha/services/peered-dns-domains/create | 9 +- .../alpha/services/peered-dns-domains/delete | 6 +- gcloud/alpha/services/quota/create | 18 +- gcloud/alpha/services/quota/delete | 16 +- gcloud/alpha/services/quota/update | 19 +-- gcloud/alpha/services/vpc-peerings/connect | 7 +- gcloud/alpha/services/vpc-peerings/update | 7 +- gcloud/alpha/source/repos/clone | 4 +- gcloud/alpha/source/repos/update | 3 +- .../spanner/backups/add-iam-policy-binding | 10 +- .../spanner/backups/remove-iam-policy-binding | 10 +- gcloud/alpha/spanner/databases/create | 5 +- gcloud/alpha/spanner/databases/ddl/update | 2 +- .../alpha/spanner/databases/sessions/delete | 3 +- gcloud/alpha/spanner/operations/cancel | 10 +- gcloud/alpha/spanner/operations/describe | 10 +- gcloud/alpha/sql/import/sql | 2 +- gcloud/alpha/tasks/create-http-task | 2 +- gcloud/alpha/tasks/queues/create | 11 +- .../tasks/queues/create-app-engine-queue | 12 +- gcloud/alpha/tasks/queues/create-pull-queue | 4 +- gcloud/alpha/tasks/queues/update | 12 +- .../tasks/queues/update-app-engine-queue | 12 +- gcloud/alpha/trace/sinks/create | 4 +- gcloud/anthos/auth/login | 2 +- .../apis/remove-iam-policy-binding | 3 +- .../gateways/remove-iam-policy-binding | 3 +- gcloud/apigee/products/update | 2 +- gcloud/app/firewall-rules/create | 5 +- gcloud/app/firewall-rules/update | 7 +- gcloud/app/ssl-certificates/create | 4 +- gcloud/app/ssl-certificates/update | 4 +- gcloud/artifacts/repositories/help | 8 +- gcloud/asset/feeds/create | 7 +- gcloud/asset/feeds/update | 4 +- gcloud/auth/activate-service-account | 2 +- gcloud/auth/application-default/help | 4 +- gcloud/auth/configure-docker | 22 ++- .../access-context-manager/policies/create | 4 +- .../active-directory/domains/backups/delete | 3 +- .../active-directory/domains/backups/update | 3 +- gcloud/beta/active-directory/domains/create | 5 +- .../active-directory/domains/trusts/create | 7 +- .../active-directory/domains/trusts/update | 6 +- gcloud/beta/active-directory/domains/update | 8 +- gcloud/beta/ai-platform/explain | 2 +- gcloud/beta/ai-platform/models/delete | 4 +- gcloud/beta/ai/custom-jobs/create | 7 +- gcloud/beta/ai/endpoints/create | 3 +- gcloud/beta/ai/endpoints/deploy-model | 4 +- gcloud/beta/ai/endpoints/predict | 3 +- gcloud/beta/ai/endpoints/raw-predict | 4 +- gcloud/beta/ai/endpoints/undeploy-model | 3 +- gcloud/beta/ai/endpoints/update | 3 +- gcloud/beta/ai/index-endpoints/create | 6 +- gcloud/beta/ai/index-endpoints/undeploy-index | 4 +- gcloud/beta/ai/indexes/create | 5 +- gcloud/beta/ai/indexes/update | 6 +- gcloud/beta/ai/models/upload | 7 +- gcloud/beta/anthos/auth/login | 2 +- .../apis/remove-iam-policy-binding | 3 +- .../gateways/remove-iam-policy-binding | 5 +- gcloud/beta/apigee/products/update | 2 +- gcloud/beta/app/firewall-rules/create | 5 +- gcloud/beta/app/firewall-rules/update | 7 +- gcloud/beta/app/ssl-certificates/create | 4 +- gcloud/beta/app/ssl-certificates/update | 4 +- gcloud/beta/artifacts/repositories/help | 9 +- gcloud/beta/asset/feeds/create | 7 +- gcloud/beta/asset/feeds/update | 4 +- gcloud/beta/auth/activate-service-account | 4 +- gcloud/beta/auth/application-default/help | 4 +- gcloud/beta/auth/configure-docker | 22 ++- gcloud/beta/bigtable/backups/create | 9 +- gcloud/beta/bigtable/backups/update | 4 +- gcloud/beta/builds/submit | 2 +- gcloud/beta/builds/worker-pools/create | 7 +- gcloud/beta/builds/worker-pools/update | 5 +- .../certificate-manager/certificates/create | 2 +- .../certificate-manager/certificates/update | 2 +- .../certificate-manager/maps/entries/update | 4 +- gcloud/beta/code/dev | 4 +- gcloud/beta/compute/addresses/create | 11 +- gcloud/beta/compute/addresses/update | 4 +- .../backend-services/add-service-bindings | 4 +- .../backend-services/remove-service-bindings | 2 +- gcloud/beta/compute/disks/create | 12 +- .../beta/compute/external-vpn-gateways/update | 3 +- .../compute/firewall-policies/rules/create | 4 +- .../compute/firewall-policies/rules/update | 4 +- gcloud/beta/compute/firewall-rules/create | 10 +- gcloud/beta/compute/forwarding-rules/update | 4 +- .../instance-groups/managed/create-instance | 15 +- .../instance-groups/managed/describe-instance | 3 +- .../instance-groups/managed/list-errors | 4 +- .../instance-groups/managed/list-instances | 2 +- .../instance-groups/managed/update-instances | 5 +- .../instance-templates/create-with-container | 8 +- .../compute/instances/create-with-container | 12 +- .../get-effective-firewalls | 3 +- .../instances/os-inventory/list-instances | 20 +-- gcloud/beta/compute/instances/set-iam-policy | 5 +- gcloud/beta/compute/instances/set-scheduling | 2 +- .../compute/instances/update-access-config | 2 +- .../beta/compute/instances/update-container | 8 +- gcloud/beta/compute/networks/create | 3 +- .../compute/networks/get-effective-firewalls | 3 +- gcloud/beta/compute/networks/peerings/create | 10 +- gcloud/beta/compute/networks/peerings/delete | 2 +- .../compute/networks/peerings/list-routes | 5 +- gcloud/beta/compute/networks/peerings/update | 7 +- gcloud/beta/compute/networks/update | 4 +- .../networks/vpc-access/connectors/create | 4 +- .../networks/vpc-access/operations/describe | 4 +- .../org-security-policies/rules/create | 4 +- .../org-security-policies/rules/update | 4 +- gcloud/beta/compute/packet-mirrorings/create | 15 +- gcloud/beta/compute/packet-mirrorings/delete | 4 +- .../beta/compute/packet-mirrorings/describe | 4 +- gcloud/beta/compute/packet-mirrorings/update | 10 +- .../compute/public-advertised-prefixes/create | 2 +- .../compute/public-delegated-prefixes/create | 2 +- gcloud/beta/compute/routers/nats/create | 15 +- gcloud/beta/compute/routers/nats/rules/create | 6 +- gcloud/beta/compute/routers/nats/rules/update | 6 +- gcloud/beta/compute/routers/nats/update | 25 +-- gcloud/beta/compute/routes/create | 4 +- .../organizations/list-host-projects | 1 + gcloud/beta/compute/tpus/create | 9 +- .../beta/compute/tpus/execution-groups/create | 17 +- .../beta/compute/tpus/execution-groups/delete | 2 +- .../beta/compute/tpus/execution-groups/resume | 2 +- gcloud/beta/compute/vpn-gateways/update | 3 +- .../container/binauthz/attestations/create | 6 +- .../beta/container/binauthz/attestations/list | 6 +- .../binauthz/attestations/sign-and-create | 13 +- .../beta/container/binauthz/attestors/create | 3 +- .../binauthz/attestors/public-keys/add | 12 +- .../binauthz/attestors/public-keys/remove | 3 +- .../binauthz/attestors/public-keys/update | 3 +- .../binauthz/create-signature-payload | 3 +- gcloud/beta/container/clusters/create | 2 +- gcloud/beta/container/clusters/update | 2 +- gcloud/beta/container/hub/cloudrun/apply | 2 +- .../container/hub/config-management/disable | 2 +- .../container/hub/config-management/enable | 2 +- .../container/hub/identity-service/describe | 3 +- .../container/hub/identity-service/disable | 2 +- .../container/hub/identity-service/enable | 2 +- gcloud/beta/container/hub/ingress/describe | 2 +- gcloud/beta/container/hub/ingress/disable | 2 +- gcloud/beta/container/hub/ingress/enable | 2 +- gcloud/beta/container/hub/ingress/update | 2 +- .../beta/container/hub/memberships/register | 54 +++--- .../beta/container/hub/memberships/unregister | 8 +- gcloud/beta/container/hub/mesh/describe | 2 +- gcloud/beta/container/hub/mesh/disable | 2 +- gcloud/beta/container/hub/mesh/enable | 2 +- .../hub/multi-cluster-services/describe | 2 +- .../hub/multi-cluster-services/disable | 2 +- .../hub/multi-cluster-services/enable | 2 +- gcloud/beta/container/images/add-tag | 14 +- gcloud/beta/container/images/delete | 4 +- gcloud/beta/container/images/describe | 12 +- gcloud/beta/container/node-pools/create | 10 +- gcloud/beta/container/node-pools/update | 11 +- gcloud/beta/container/subnets/list-usable | 7 +- gcloud/beta/data-catalog/entries/create | 7 +- gcloud/beta/data-catalog/entries/update | 10 +- gcloud/beta/data-catalog/entry-groups/create | 5 +- gcloud/beta/data-catalog/tag-templates/create | 3 +- .../beta/data-fusion/add-iam-policy-binding | 6 +- gcloud/beta/data-fusion/get-iam-policy | 2 +- .../data-fusion/remove-iam-policy-binding | 6 +- gcloud/beta/data-fusion/set-iam-policy | 7 +- gcloud/beta/dataflow/flex-template/build | 15 +- gcloud/beta/datapipelines/pipeline/create | 10 +- gcloud/beta/datapipelines/pipeline/update | 3 +- .../autoscaling-policies/set-iam-policy | 4 +- gcloud/beta/dataproc/batches/submit/pyspark | 4 +- gcloud/beta/dataproc/jobs/submit/hadoop | 4 +- gcloud/beta/dataproc/jobs/submit/hive | 6 +- gcloud/beta/dataproc/jobs/submit/pig | 10 +- gcloud/beta/dataproc/jobs/submit/spark | 3 +- gcloud/beta/dataproc/jobs/submit/spark-r | 3 +- gcloud/beta/dataproc/jobs/submit/spark-sql | 6 +- gcloud/beta/dataproc/jobs/wait | 2 +- .../dataproc/workflow-templates/add-job/help | 9 +- gcloud/beta/dataproc/workflow-templates/help | 3 +- gcloud/beta/debug/logpoints/help | 16 +- .../delivery-pipelines/add-iam-policy-binding | 7 +- .../remove-iam-policy-binding | 7 +- .../deploy/targets/add-iam-policy-binding | 5 +- .../deploy/targets/remove-iam-policy-binding | 5 +- .../deployment-manager/deployments/create | 8 +- gcloud/beta/dns/dns-keys/list | 3 +- gcloud/beta/dns/managed-zones/create | 9 +- gcloud/beta/dns/policies/create | 14 +- gcloud/beta/dns/record-sets/create | 7 +- gcloud/beta/dns/record-sets/export | 2 +- gcloud/beta/dns/record-sets/transaction/add | 8 +- .../beta/dns/record-sets/transaction/remove | 8 +- gcloud/beta/dns/record-sets/update | 7 +- gcloud/beta/dns/response-policies/create | 10 +- .../beta/dns/response-policies/rules/create | 17 +- gcloud/beta/dns/response-policies/rules/help | 19 ++- .../beta/dns/response-policies/rules/update | 12 +- gcloud/beta/dns/response-policies/update | 11 +- .../endpoints/services/add-iam-policy-binding | 4 +- gcloud/beta/essential-contacts/compute | 3 +- gcloud/beta/essential-contacts/create | 17 +- gcloud/beta/essential-contacts/update | 2 +- gcloud/beta/events/triggers/create | 4 +- gcloud/beta/filestore/instances/restore | 6 +- gcloud/beta/filestore/instances/update | 2 +- gcloud/beta/firestore/indexes/fields/list | 7 +- gcloud/beta/firestore/indexes/fields/update | 6 +- gcloud/beta/functions/deploy | 33 ++-- gcloud/beta/game/servers/clusters/create | 10 +- gcloud/beta/game/servers/clusters/update | 4 +- gcloud/beta/game/servers/configs/create | 4 +- gcloud/beta/game/servers/deployments/create | 3 +- gcloud/beta/iam/list-grantable-roles | 3 +- gcloud/beta/iam/policies/create | 49 ++++++ gcloud/beta/iam/policies/delete | 52 ++++++ gcloud/beta/iam/policies/get | 44 +++++ gcloud/beta/iam/policies/help | 21 +++ gcloud/beta/iam/policies/list | 72 ++++++++ gcloud/beta/iam/policies/update | 56 +++++++ .../beta/iam/workload-identity-pools/create | 6 +- .../providers/create-aws | 9 +- .../providers/create-oidc | 9 +- .../workload-identity-pools/providers/delete | 4 +- .../providers/describe | 6 +- .../workload-identity-pools/providers/list | 7 +- .../providers/operations/describe | 3 +- .../providers/undelete | 4 +- .../providers/update-aws | 6 +- .../providers/update-oidc | 11 +- .../beta/iam/workload-identity-pools/update | 6 +- gcloud/beta/iap/oauth-brands/create | 2 +- gcloud/beta/iap/oauth-brands/list | 2 +- gcloud/beta/iap/settings/get | 2 +- gcloud/beta/iap/settings/set | 2 +- gcloud/beta/iap/web/add-iam-policy-binding | 10 +- gcloud/beta/iap/web/enable | 6 +- gcloud/beta/iap/web/get-iam-policy | 3 +- gcloud/beta/iap/web/remove-iam-policy-binding | 13 +- gcloud/beta/iap/web/set-iam-policy | 10 +- gcloud/beta/identity/groups/create | 13 +- gcloud/beta/identity/groups/memberships/add | 2 +- .../memberships/modify-membership-roles | 5 +- gcloud/beta/identity/groups/search | 7 +- gcloud/beta/identity/groups/update | 4 +- gcloud/beta/kms/asymmetric-decrypt | 11 +- gcloud/beta/kms/asymmetric-sign | 12 +- gcloud/beta/kms/decrypt | 14 +- .../ekm-connections/add-iam-policy-binding | 6 +- gcloud/beta/kms/ekm-connections/create | 12 +- gcloud/beta/kms/ekm-connections/describe | 6 +- .../beta/kms/ekm-connections/get-iam-policy | 6 +- gcloud/beta/kms/ekm-connections/help | 6 +- gcloud/beta/kms/ekm-connections/list | 6 +- .../ekm-connections/remove-iam-policy-binding | 6 +- .../beta/kms/ekm-connections/set-iam-policy | 6 +- gcloud/beta/kms/ekm-connections/update | 15 +- gcloud/beta/kms/encrypt | 7 +- gcloud/beta/kms/import-jobs/create | 5 +- gcloud/beta/kms/keys/create | 50 ++---- gcloud/beta/kms/keys/remove-rotation-schedule | 3 +- gcloud/beta/kms/keys/set-rotation-schedule | 4 +- gcloud/beta/kms/keys/update | 33 ++-- gcloud/beta/kms/keys/versions/create | 12 +- gcloud/beta/kms/keys/versions/get-public-key | 8 +- gcloud/beta/kms/keys/versions/import | 8 +- gcloud/beta/kms/keys/versions/list | 3 +- gcloud/beta/kms/keys/versions/update | 18 +- gcloud/beta/kms/mac-sign | 11 +- gcloud/beta/kms/mac-verify | 11 +- gcloud/beta/lifesciences/pipelines/run | 5 +- gcloud/beta/logging/sinks/create | 15 +- gcloud/beta/logging/views/update | 3 +- gcloud/beta/memcache/instances/create | 4 +- gcloud/beta/metastore/services/import/gcs | 2 +- gcloud/beta/metastore/services/imports/create | 2 +- gcloud/beta/ml-engine/explain | 2 +- gcloud/beta/ml-engine/models/delete | 4 +- gcloud/beta/ml/language/classify-text | 2 +- gcloud/beta/ml/speech/recognize | 10 +- gcloud/beta/ml/speech/recognize-long-running | 6 + gcloud/beta/ml/vision/detect-text-pdf | 4 +- gcloud/beta/ml/vision/detect-text-tiff | 4 +- gcloud/beta/monitoring/channels/create | 16 +- gcloud/beta/monitoring/channels/list | 7 +- gcloud/beta/monitoring/channels/update | 2 +- .../connectivity-tests/create | 9 +- .../connectivity-tests/delete | 3 +- .../connectivity-tests/describe | 3 +- .../connectivity-tests/list | 3 +- .../connectivity-tests/rerun | 3 +- .../connectivity-tests/update | 6 +- .../network-management/operations/describe | 3 +- .../beta/network-management/operations/list | 3 +- gcloud/beta/policy-troubleshoot/iam | 4 +- gcloud/beta/privateca/certificates/create | 15 +- gcloud/beta/privateca/certificates/describe | 6 +- gcloud/beta/privateca/certificates/revoke | 11 +- gcloud/beta/privateca/certificates/update | 4 +- .../privateca/roots/add-iam-policy-binding | 5 +- gcloud/beta/privateca/roots/create | 33 ++-- gcloud/beta/privateca/roots/describe | 6 +- .../privateca/roots/remove-iam-policy-binding | 5 +- gcloud/beta/privateca/roots/update | 10 +- gcloud/beta/privateca/subordinates/activate | 3 +- .../subordinates/add-iam-policy-binding | 7 +- gcloud/beta/privateca/subordinates/create | 22 +-- gcloud/beta/privateca/subordinates/describe | 6 +- .../subordinates/remove-iam-policy-binding | 7 +- gcloud/beta/privateca/subordinates/update | 6 +- gcloud/beta/pubsub/lite-reservations/create | 3 +- gcloud/beta/pubsub/lite-reservations/delete | 2 +- gcloud/beta/pubsub/lite-reservations/describe | 2 +- gcloud/beta/pubsub/lite-reservations/list | 2 +- .../beta/pubsub/lite-reservations/list-topics | 2 +- gcloud/beta/pubsub/lite-reservations/update | 3 +- .../beta/pubsub/lite-subscriptions/ack-up-to | 4 +- gcloud/beta/pubsub/lite-subscriptions/create | 8 +- gcloud/beta/pubsub/lite-subscriptions/delete | 2 +- .../beta/pubsub/lite-subscriptions/describe | 2 +- gcloud/beta/pubsub/lite-subscriptions/list | 3 +- gcloud/beta/pubsub/lite-subscriptions/seek | 8 +- gcloud/beta/pubsub/lite-subscriptions/update | 4 +- gcloud/beta/pubsub/lite-topics/create | 6 +- gcloud/beta/pubsub/lite-topics/delete | 2 +- gcloud/beta/pubsub/lite-topics/describe | 2 +- gcloud/beta/pubsub/lite-topics/list | 2 +- .../pubsub/lite-topics/list-subscriptions | 2 +- gcloud/beta/pubsub/lite-topics/update | 3 +- .../subscriptions/add-iam-policy-binding | 4 +- gcloud/beta/pubsub/subscriptions/create | 14 +- gcloud/beta/pubsub/subscriptions/update | 11 +- .../recommender/insight-type-config/update | 4 +- .../beta/recommender/recommendations/describe | 4 +- gcloud/beta/recommender/recommendations/list | 2 +- .../recommender/recommendations/mark-claimed | 6 +- .../recommender/recommender-config/update | 4 +- gcloud/beta/scc/findings/list | 2 +- gcloud/beta/scheduler/jobs/create/app-engine | 3 +- gcloud/beta/scheduler/jobs/create/http | 4 +- gcloud/beta/scheduler/jobs/create/pubsub | 4 +- gcloud/beta/secrets/create | 17 +- gcloud/beta/secrets/update | 4 +- .../beta/services/peered-dns-domains/create | 9 +- .../beta/services/peered-dns-domains/delete | 6 +- gcloud/beta/services/vpc-peerings/connect | 7 +- gcloud/beta/services/vpc-peerings/update | 7 +- gcloud/beta/source/project-configs/update | 3 +- gcloud/beta/source/repos/clone | 4 +- gcloud/beta/source/repos/update | 3 +- .../spanner/backups/add-iam-policy-binding | 12 +- .../spanner/backups/remove-iam-policy-binding | 10 +- gcloud/beta/spanner/databases/create | 5 +- gcloud/beta/spanner/databases/ddl/update | 2 +- gcloud/beta/spanner/databases/sessions/delete | 3 +- gcloud/beta/spanner/operations/cancel | 10 +- gcloud/beta/spanner/operations/describe | 10 +- gcloud/beta/sql/import/sql | 2 +- gcloud/beta/tasks/create-http-task | 2 +- gcloud/beta/tasks/queues/create | 11 +- .../beta/tasks/queues/create-app-engine-queue | 10 +- gcloud/beta/tasks/queues/create-pull-queue | 4 +- gcloud/beta/tasks/queues/update | 12 +- .../beta/tasks/queues/update-app-engine-queue | 12 +- gcloud/bigtable/backups/create | 9 +- gcloud/bigtable/backups/update | 4 +- gcloud/builds/submit | 2 +- gcloud/builds/worker-pools/create | 7 +- gcloud/builds/worker-pools/update | 5 +- gcloud/compute/addresses/create | 12 +- gcloud/compute/disks/create | 12 +- gcloud/compute/external-vpn-gateways/update | 4 +- gcloud/compute/firewall-policies/rules/create | 4 +- gcloud/compute/firewall-policies/rules/update | 4 +- gcloud/compute/firewall-rules/create | 10 +- gcloud/compute/forwarding-rules/update | 4 +- .../instance-groups/managed/create-instance | 11 +- .../instance-groups/managed/describe-instance | 3 +- .../instance-groups/managed/list-errors | 4 +- .../instance-groups/managed/list-instances | 4 +- .../instance-groups/managed/update-instances | 7 +- .../instance-templates/create-with-container | 8 +- .../compute/instances/create-with-container | 12 +- .../get-effective-firewalls | 3 +- .../instances/os-inventory/list-instances | 20 +-- gcloud/compute/instances/set-iam-policy | 5 +- gcloud/compute/instances/set-scheduling | 2 +- gcloud/compute/instances/update-access-config | 2 +- gcloud/compute/instances/update-container | 8 +- gcloud/compute/networks/create | 3 +- .../compute/networks/get-effective-firewalls | 3 +- gcloud/compute/networks/peerings/create | 10 +- gcloud/compute/networks/peerings/delete | 2 +- gcloud/compute/networks/peerings/list-routes | 5 +- gcloud/compute/networks/peerings/update | 7 +- gcloud/compute/networks/update | 4 +- .../networks/vpc-access/connectors/create | 4 +- .../networks/vpc-access/operations/describe | 4 +- .../os-policy-assignment-reports/describe | 2 +- gcloud/compute/packet-mirrorings/create | 15 +- gcloud/compute/packet-mirrorings/delete | 3 +- gcloud/compute/packet-mirrorings/describe | 3 +- gcloud/compute/packet-mirrorings/update | 10 +- .../compute/public-advertised-prefixes/create | 2 +- .../compute/public-delegated-prefixes/create | 2 +- gcloud/compute/routers/nats/create | 15 +- gcloud/compute/routers/nats/rules/create | 6 +- gcloud/compute/routers/nats/rules/update | 6 +- gcloud/compute/routers/nats/update | 25 +-- gcloud/compute/routes/create | 4 +- .../organizations/list-host-projects | 1 + gcloud/compute/tpus/create | 9 +- gcloud/compute/tpus/execution-groups/create | 17 +- gcloud/compute/tpus/execution-groups/delete | 3 +- gcloud/compute/vpn-gateways/update | 3 +- gcloud/container/binauthz/attestations/create | 7 +- gcloud/container/binauthz/attestations/list | 6 +- gcloud/container/binauthz/attestors/create | 3 +- .../binauthz/attestors/public-keys/add | 12 +- .../binauthz/attestors/public-keys/remove | 3 +- .../binauthz/attestors/public-keys/update | 3 +- .../binauthz/create-signature-payload | 3 +- gcloud/container/clusters/create | 31 ++-- gcloud/container/clusters/update | 28 +++- gcloud/container/hub/cloudrun/apply | 2 +- gcloud/container/hub/ingress/describe | 2 +- gcloud/container/hub/ingress/disable | 2 +- gcloud/container/hub/ingress/enable | 2 +- gcloud/container/hub/ingress/update | 2 +- gcloud/container/hub/memberships/register | 54 +++--- gcloud/container/hub/memberships/unregister | 8 +- gcloud/container/hub/mesh/describe | 2 +- gcloud/container/hub/mesh/disable | 2 +- gcloud/container/hub/mesh/enable | 2 +- .../hub/multi-cluster-services/describe | 2 +- .../hub/multi-cluster-services/disable | 2 +- .../hub/multi-cluster-services/enable | 2 +- gcloud/container/images/add-tag | 16 +- gcloud/container/images/delete | 4 +- gcloud/container/images/describe | 12 +- gcloud/container/node-pools/create | 1 + gcloud/container/node-pools/update | 1 + gcloud/container/subnets/list-usable | 7 +- gcloud/data-catalog/entries/create | 25 +-- gcloud/data-catalog/entries/delete | 4 +- gcloud/data-catalog/entries/describe | 4 +- gcloud/data-catalog/entries/star | 4 +- gcloud/data-catalog/entries/unstar | 4 +- gcloud/data-catalog/entries/update | 10 +- gcloud/data-catalog/entry-groups/create | 5 +- gcloud/data-catalog/tag-templates/create | 3 +- .../database-migration/migration-jobs/create | 2 +- .../database-migration/migration-jobs/update | 2 +- gcloud/dataflow/flex-template/build | 12 +- gcloud/dataplex/tasks/add-iam-policy-binding | 2 +- gcloud/dataplex/tasks/create | 10 +- .../dataplex/tasks/remove-iam-policy-binding | 2 +- gcloud/dataplex/tasks/update | 3 +- .../autoscaling-policies/set-iam-policy | 4 +- gcloud/dataproc/batches/submit/pyspark | 2 +- gcloud/dataproc/jobs/submit/hadoop | 4 +- gcloud/dataproc/jobs/submit/hive | 6 +- gcloud/dataproc/jobs/submit/pig | 10 +- gcloud/dataproc/jobs/submit/spark | 3 +- gcloud/dataproc/jobs/submit/spark-r | 3 +- gcloud/dataproc/jobs/submit/spark-sql | 6 +- gcloud/dataproc/jobs/wait | 2 +- .../dataproc/workflow-templates/add-job/help | 9 +- gcloud/dataproc/workflow-templates/help | 3 +- gcloud/debug/logpoints/help | 16 +- .../delivery-pipelines/add-iam-policy-binding | 7 +- .../remove-iam-policy-binding | 7 +- gcloud/deploy/targets/add-iam-policy-binding | 5 +- .../deploy/targets/remove-iam-policy-binding | 5 +- gcloud/deployment-manager/deployments/create | 8 +- gcloud/dns/dns-keys/list | 3 +- gcloud/dns/policies/create | 12 +- gcloud/dns/record-sets/create | 7 +- gcloud/dns/record-sets/export | 2 +- gcloud/dns/record-sets/transaction/add | 6 +- gcloud/dns/record-sets/transaction/help | 3 +- gcloud/dns/record-sets/transaction/remove | 7 +- gcloud/dns/record-sets/update | 3 +- gcloud/dns/response-policies/create | 10 +- gcloud/dns/response-policies/rules/create | 17 +- gcloud/dns/response-policies/rules/help | 19 ++- gcloud/dns/response-policies/rules/update | 12 +- gcloud/dns/response-policies/update | 11 +- .../endpoints/services/add-iam-policy-binding | 4 +- gcloud/essential-contacts/compute | 3 +- gcloud/essential-contacts/create | 20 ++- gcloud/essential-contacts/update | 2 +- gcloud/filestore/instances/restore | 6 +- gcloud/filestore/instances/update | 2 +- gcloud/firestore/indexes/fields/list | 7 +- gcloud/firestore/indexes/fields/update | 6 +- gcloud/functions/deploy | 33 ++-- gcloud/game/servers/clusters/create | 10 +- gcloud/game/servers/clusters/update | 4 +- gcloud/game/servers/configs/create | 4 +- gcloud/game/servers/deployments/create | 3 +- gcloud/iam/list-grantable-roles | 3 +- gcloud/iam/workload-identity-pools/create | 6 +- .../providers/create-aws | 9 +- .../providers/create-oidc | 9 +- .../workload-identity-pools/providers/delete | 4 +- .../providers/describe | 6 +- .../workload-identity-pools/providers/list | 7 +- .../providers/operations/describe | 3 +- .../providers/undelete | 4 +- .../providers/update-aws | 6 +- .../providers/update-oidc | 11 +- gcloud/iam/workload-identity-pools/update | 6 +- gcloud/iap/settings/get | 2 +- gcloud/iap/settings/set | 2 +- gcloud/iap/web/add-iam-policy-binding | 10 +- gcloud/iap/web/enable | 6 +- gcloud/iap/web/get-iam-policy | 3 +- gcloud/iap/web/remove-iam-policy-binding | 13 +- gcloud/iap/web/set-iam-policy | 10 +- gcloud/identity/groups/create | 10 +- gcloud/identity/groups/memberships/add | 2 +- .../memberships/modify-membership-roles | 5 +- gcloud/identity/groups/search | 7 +- gcloud/identity/groups/update | 4 +- gcloud/kms/asymmetric-decrypt | 11 +- gcloud/kms/asymmetric-sign | 12 +- gcloud/kms/decrypt | 14 +- .../ekm-connections/add-iam-policy-binding | 141 ++++++++++++++++ gcloud/kms/ekm-connections/create | 81 +++++++++ gcloud/kms/ekm-connections/describe | 57 +++++++ gcloud/kms/ekm-connections/get-iam-policy | 95 +++++++++++ gcloud/kms/ekm-connections/help | 49 ++++++ gcloud/kms/ekm-connections/list | 79 +++++++++ .../ekm-connections/remove-iam-policy-binding | 157 ++++++++++++++++++ gcloud/kms/ekm-connections/set-iam-policy | 80 +++++++++ gcloud/kms/ekm-connections/update | 88 ++++++++++ gcloud/kms/encrypt | 7 +- gcloud/kms/help | 3 + gcloud/kms/import-jobs/create | 3 +- gcloud/kms/keys/create | 50 ++---- gcloud/kms/keys/remove-rotation-schedule | 3 +- gcloud/kms/keys/set-rotation-schedule | 6 +- gcloud/kms/keys/update | 33 ++-- gcloud/kms/keys/versions/create | 12 +- gcloud/kms/keys/versions/get-public-key | 8 +- gcloud/kms/keys/versions/import | 8 +- gcloud/kms/keys/versions/list | 3 +- gcloud/kms/keys/versions/update | 18 +- gcloud/kms/mac-sign | 10 +- gcloud/kms/mac-verify | 11 +- gcloud/logging/sinks/create | 15 +- gcloud/logging/views/update | 3 +- gcloud/memcache/instances/create | 4 +- gcloud/metastore/services/import/gcs | 2 +- gcloud/ml-engine/models/delete | 4 +- gcloud/ml/language/classify-text | 2 +- gcloud/ml/speech/recognize | 10 +- gcloud/ml/speech/recognize-long-running | 6 + gcloud/ml/vision/detect-text-pdf | 4 +- gcloud/ml/vision/detect-text-tiff | 4 +- .../connectivity-tests/create | 9 +- .../connectivity-tests/delete | 3 +- .../connectivity-tests/describe | 3 +- .../connectivity-tests/list | 3 +- .../connectivity-tests/rerun | 3 +- .../connectivity-tests/update | 6 +- gcloud/network-management/operations/describe | 3 +- gcloud/network-management/operations/list | 3 +- gcloud/policy-troubleshoot/iam | 4 +- gcloud/privateca/certificates/create | 10 +- gcloud/privateca/certificates/export | 8 +- gcloud/privateca/certificates/list | 3 +- gcloud/privateca/certificates/revoke | 11 +- gcloud/privateca/certificates/update | 4 +- gcloud/privateca/pools/add-iam-policy-binding | 5 +- gcloud/privateca/pools/create | 9 +- gcloud/privateca/pools/describe | 3 +- gcloud/privateca/pools/get-ca-certs | 3 +- .../privateca/pools/remove-iam-policy-binding | 3 +- gcloud/privateca/pools/update | 10 +- gcloud/privateca/roots/create | 15 +- gcloud/privateca/roots/describe | 10 +- gcloud/privateca/roots/update | 6 +- gcloud/privateca/subordinates/activate | 5 +- gcloud/privateca/subordinates/create | 17 +- gcloud/privateca/subordinates/delete | 4 +- gcloud/privateca/subordinates/describe | 6 +- gcloud/privateca/subordinates/update | 12 +- .../templates/add-iam-policy-binding | 5 +- .../templates/remove-iam-policy-binding | 5 +- gcloud/pubsub/lite-reservations/create | 3 +- gcloud/pubsub/lite-reservations/delete | 2 +- gcloud/pubsub/lite-reservations/describe | 2 +- gcloud/pubsub/lite-reservations/list | 2 +- gcloud/pubsub/lite-reservations/list-topics | 2 +- gcloud/pubsub/lite-reservations/update | 3 +- gcloud/pubsub/lite-subscriptions/ack-up-to | 4 +- gcloud/pubsub/lite-subscriptions/create | 8 +- gcloud/pubsub/lite-subscriptions/delete | 2 +- gcloud/pubsub/lite-subscriptions/describe | 2 +- gcloud/pubsub/lite-subscriptions/list | 2 +- gcloud/pubsub/lite-subscriptions/seek | 8 +- gcloud/pubsub/lite-subscriptions/update | 4 +- gcloud/pubsub/lite-topics/create | 6 +- gcloud/pubsub/lite-topics/delete | 3 +- gcloud/pubsub/lite-topics/describe | 3 +- gcloud/pubsub/lite-topics/list | 3 +- gcloud/pubsub/lite-topics/list-subscriptions | 2 +- gcloud/pubsub/lite-topics/update | 3 +- .../subscriptions/add-iam-policy-binding | 4 +- gcloud/recommender/recommendations/describe | 4 +- gcloud/recommender/recommendations/list | 2 +- .../recommender/recommendations/mark-claimed | 6 +- gcloud/scc/bqexports/create | 111 +++++++++++++ gcloud/scc/bqexports/delete | 67 ++++++++ gcloud/scc/bqexports/get | 65 ++++++++ gcloud/scc/bqexports/help | 29 ++++ gcloud/scc/bqexports/list | 81 +++++++++ gcloud/scc/findings/list | 2 +- gcloud/scc/help | 3 + gcloud/scheduler/jobs/create/app-engine | 3 +- gcloud/scheduler/jobs/create/http | 5 +- gcloud/scheduler/jobs/create/pubsub | 5 +- gcloud/secrets/create | 18 +- gcloud/secrets/update | 4 +- gcloud/service-directory/endpoints/create | 2 +- gcloud/services/api-keys/describe | 9 +- gcloud/services/peered-dns-domains/create | 9 +- gcloud/services/peered-dns-domains/delete | 6 +- gcloud/services/vpc-peerings/connect | 7 +- gcloud/services/vpc-peerings/update | 7 +- gcloud/source/project-configs/update | 3 +- gcloud/source/repos/clone | 4 +- gcloud/source/repos/update | 3 +- gcloud/spanner/databases/create | 4 +- gcloud/spanner/databases/ddl/update | 2 +- gcloud/spanner/databases/sessions/delete | 3 +- gcloud/spanner/operations/cancel | 10 +- gcloud/spanner/operations/describe | 10 +- gcloud/sql/import/sql | 2 +- gcloud/tasks/create-http-task | 2 +- gcloud/tasks/queues/create | 11 +- gcloud/tasks/queues/update | 12 +- 1018 files changed, 4838 insertions(+), 3409 deletions(-) create mode 100644 gcloud/_version create mode 100644 gcloud/alpha/iam/policies/create create mode 100644 gcloud/alpha/iam/policies/delete create mode 100644 gcloud/alpha/iam/policies/get create mode 100644 gcloud/alpha/iam/policies/list create mode 100644 gcloud/alpha/iam/policies/update create mode 100644 gcloud/beta/iam/policies/create create mode 100644 gcloud/beta/iam/policies/delete create mode 100644 gcloud/beta/iam/policies/get create mode 100644 gcloud/beta/iam/policies/list create mode 100644 gcloud/beta/iam/policies/update create mode 100644 gcloud/kms/ekm-connections/add-iam-policy-binding create mode 100644 gcloud/kms/ekm-connections/create create mode 100644 gcloud/kms/ekm-connections/describe create mode 100644 gcloud/kms/ekm-connections/get-iam-policy create mode 100644 gcloud/kms/ekm-connections/help create mode 100644 gcloud/kms/ekm-connections/list create mode 100644 gcloud/kms/ekm-connections/remove-iam-policy-binding create mode 100644 gcloud/kms/ekm-connections/set-iam-policy create mode 100644 gcloud/kms/ekm-connections/update create mode 100644 gcloud/scc/bqexports/create create mode 100644 gcloud/scc/bqexports/delete create mode 100644 gcloud/scc/bqexports/get create mode 100644 gcloud/scc/bqexports/help create mode 100644 gcloud/scc/bqexports/list diff --git a/gcloud/_version b/gcloud/_version new file mode 100644 index 000000000..5f8bf13e4 --- /dev/null +++ b/gcloud/_version @@ -0,0 +1,6 @@ +Google Cloud SDK 375.0.0 +alpha 2022.02.25 +beta 2022.02.25 +bq 2.0.74 +core 2022.02.25 +gsutil 5.6 diff --git a/gcloud/access-context-manager/policies/create b/gcloud/access-context-manager/policies/create index 05206ead7..8dda748a5 100644 --- a/gcloud/access-context-manager/policies/create +++ b/gcloud/access-context-manager/policies/create @@ -32,7 +32,7 @@ EXAMPLES $ gcloud access-context-manager policies create \ --organization=organizations/123 --scopes=folders/345 \ - --title="My Folder Policy" + --title="My Folder Policy" Only projects within this folder can be added to service perimeters within this policy. @@ -42,7 +42,7 @@ EXAMPLES $ gcloud access-context-manager policies create \ --organization=organizations/123 --scopes=projects/567 \ - --title="My Project Policy" + --title="My Project Policy" REQUIRED FLAGS --organization=ORGANIZATION diff --git a/gcloud/active-directory/domains/create b/gcloud/active-directory/domains/create index 7204a3c32..d8449a74a 100644 --- a/gcloud/active-directory/domains/create +++ b/gcloud/active-directory/domains/create @@ -25,8 +25,9 @@ EXAMPLES address range 10.172.0.0/24. $ gcloud active-directory domains create my-domain.com \ - --region=us-central1 --reserved-ip-range="10.172.0.0/24" - --authorized-networks=projects/my-project/global/networks/my-network + --region=us-central1 --reserved-ip-range="10.172.0.0/24" \ + --authorized-networks=projects/my-project/global/networks/\ + my-network POSITIONAL ARGUMENTS Domain resource - Name of the managed Managed Microsoft AD domain you want diff --git a/gcloud/active-directory/domains/trusts/create b/gcloud/active-directory/domains/trusts/create index aa59dca46..7f8ee4ae2 100644 --- a/gcloud/active-directory/domains/trusts/create +++ b/gcloud/active-directory/domains/trusts/create @@ -27,9 +27,10 @@ EXAMPLES my-domain.com and target-domain.com. $ gcloud active-directory domains trusts create my-domain.com \ - --target-domain-name=target-domain.com - --target-dns-ip-addresses=10.177.0.2 --type=EXTERNAL --direction=BIDIRECTIONAL - --selective-authentication=false --async + --target-domain-name=target-domain.com \ + --target-dns-ip-addresses=10.177.0.2 --type=EXTERNAL \ + --direction=BIDIRECTIONAL --selective-authentication=false \ + --async POSITIONAL ARGUMENTS Domain resource - Name of the Managed Microsoft AD domain you want to diff --git a/gcloud/active-directory/domains/trusts/update b/gcloud/active-directory/domains/trusts/update index 54e2686a1..b8821de08 100644 --- a/gcloud/active-directory/domains/trusts/update +++ b/gcloud/active-directory/domains/trusts/update @@ -24,9 +24,9 @@ EXAMPLES The following command updates the target DNS IP address for the AD trust between my-domain.com and my-target-domain.com to 10.177.0.3. - $ gcloud active-directory domains trusts update my-domain.com \ - --target-domain-name=my-target-domain.com - --target-dns-ip-addresses=10.177.0.3 + $ gcloud active-directory domains trusts update my-domain.com \ + --target-domain-name=my-target-domain.com \ + --target-dns-ip-addresses=10.177.0.3 POSITIONAL ARGUMENTS Domain resource - Name of the Managed Microsoft AD trust for which you diff --git a/gcloud/active-directory/domains/update b/gcloud/active-directory/domains/update index 0286ffec7..daa755ae0 100644 --- a/gcloud/active-directory/domains/update +++ b/gcloud/active-directory/domains/update @@ -25,13 +25,13 @@ EXAMPLES us-west1: $ gcloud active-directory domains update my-domain.com \ - --update-labels=env=test,service=foo \ - --add-region=us-west1 + --update-labels=env=test,service=foo --add-region=us-west1 This peers the domain my-domain.com to the network my-network. - $ gcloud active-directory domains update my-domain.com - --add-authorized-networks=projects/my-project/global/networks/my-network + $ gcloud active-directory domains update my-domain.com \ + --add-authorized-networks=projects/my-project/global/networks/\ + my-network POSITIONAL ARGUMENTS Domain resource - Name of the Managed Microsoft AD domain you want to diff --git a/gcloud/ai-platform/models/delete b/gcloud/ai-platform/models/delete index b6537ff1e..b6445023e 100644 --- a/gcloud/ai-platform/models/delete +++ b/gcloud/ai-platform/models/delete @@ -9,8 +9,8 @@ EXAMPLES To delete all models matching the regular expression vision[0-9]+, run: $ gcloud ai-platform models list --uri \ - --filter 'name ~ vision[0-9]+' | - xargs -n 1 gcloud ai-platform models delete + --filter 'name ~ vision[0-9]+' | xargs -n 1 gcloud ai-platform \ + models delete POSITIONAL ARGUMENTS MODEL diff --git a/gcloud/ai/custom-jobs/create b/gcloud/ai/custom-jobs/create index 16c3b1fb5..ff3fa87a1 100644 --- a/gcloud/ai/custom-jobs/create +++ b/gcloud/ai/custom-jobs/create @@ -18,9 +18,11 @@ DESCRIPTION EXAMPLES To create a job under project example in region us-central1, run: - $ gcloud ai custom-jobs create --region=us-central1 --project=example - --worker-pool-spec=replica-count=1,machine-type='n1-highmem-2',container-image-uri='gcr.io/ucaip-test/ucaip-training-test' - --display-name=test + $ gcloud ai custom-jobs create --region=us-central1 \ + --project=example \ + --worker-pool-spec=replica-count=1,machine-type='n1-highmem-2',\ + container-image-uri='gcr.io/ucaip-test/ucaip-training-test' \ + --display-name=test REQUIRED FLAGS --display-name=DISPLAY_NAME diff --git a/gcloud/ai/endpoints/create b/gcloud/ai/endpoints/create index e11cbe390..6ccc1eed7 100644 --- a/gcloud/ai/endpoints/create +++ b/gcloud/ai/endpoints/create @@ -9,8 +9,8 @@ SYNOPSIS EXAMPLES To create an endpoint under project example in region us-central1, run: - $ gcloud ai endpoints create --project=example --region=us-central1 - --display-name=my_endpoint + $ gcloud ai endpoints create --project=example \ + --region=us-central1 --display-name=my_endpoint REQUIRED FLAGS --display-name=DISPLAY_NAME diff --git a/gcloud/ai/endpoints/deploy-model b/gcloud/ai/endpoints/deploy-model index 3d9df2940..219235ff2 100644 --- a/gcloud/ai/endpoints/deploy-model +++ b/gcloud/ai/endpoints/deploy-model @@ -18,8 +18,8 @@ EXAMPLES us-central1, run: $ gcloud ai endpoints deploy-model 123 --project=example \ - --region=us-central1 --model=456 - --display-name=my_deployed_model + --region=us-central1 --model=456 \ + --display-name=my_deployed_model POSITIONAL ARGUMENTS Endpoint resource - The endpoint to deploy a model to. The arguments in diff --git a/gcloud/ai/endpoints/predict b/gcloud/ai/endpoints/predict index 0c7552ca9..910f71225 100644 --- a/gcloud/ai/endpoints/predict +++ b/gcloud/ai/endpoints/predict @@ -16,8 +16,7 @@ EXAMPLES us-central1, run: $ gcloud ai endpoints predict 123 --project=example \ - --region=us-central1 - --json-request=input.json + --region=us-central1 --json-request=input.json POSITIONAL ARGUMENTS Endpoint resource - The endpoint to do online prediction. The arguments in diff --git a/gcloud/ai/endpoints/raw-predict b/gcloud/ai/endpoints/raw-predict index 6ee3b3386..8f1e2aaef 100644 --- a/gcloud/ai/endpoints/raw-predict +++ b/gcloud/ai/endpoints/raw-predict @@ -31,8 +31,8 @@ EXAMPLES To send the image file image.jpeg and set the content type, run: $ gcloud ai endpoints raw-predict 123 --project=example \ - --region=us-central1 - --http-headers=Content-Type=image/jpeg --request=@image.jpeg + --region=us-central1 --http-headers=Content-Type=image/jpeg \ + --request=@image.jpeg POSITIONAL ARGUMENTS Endpoint resource - The endpoint to do online raw prediction. The diff --git a/gcloud/ai/endpoints/undeploy-model b/gcloud/ai/endpoints/undeploy-model index a78c384c7..868f7f946 100644 --- a/gcloud/ai/endpoints/undeploy-model +++ b/gcloud/ai/endpoints/undeploy-model @@ -12,8 +12,7 @@ EXAMPLES region us-central1, run: $ gcloud ai endpoints undeploy-model 123 --project=example \ - --region=us-central1 - --deployed-model-id=456 + --region=us-central1 --deployed-model-id=456 POSITIONAL ARGUMENTS Endpoint resource - The endpoint to undeploy a model from. The arguments diff --git a/gcloud/ai/endpoints/update b/gcloud/ai/endpoints/update index b3dff9896..a54deddf4 100644 --- a/gcloud/ai/endpoints/update +++ b/gcloud/ai/endpoints/update @@ -13,8 +13,7 @@ EXAMPLES To update an endpoint 123 under project example in region us-central1, run: $ gcloud ai endpoints update 123 --project=example \ - --region=us-central1 - --display-name=new_name + --region=us-central1 --display-name=new_name POSITIONAL ARGUMENTS Endpoint resource - The endpoint to update. The arguments in this group diff --git a/gcloud/ai/index-endpoints/create b/gcloud/ai/index-endpoints/create index e6dafca38..3758a5139 100644 --- a/gcloud/ai/index-endpoints/create +++ b/gcloud/ai/index-endpoints/create @@ -11,9 +11,9 @@ EXAMPLES projects/123/global/networks/test-network in region us-central1, run: $ gcloud ai index-endpoints create --display-name=index-endpoint \ - --description=test - --network=projects/123/global/networks/test-network - --project=example --region=us-central1 + --description=test \ + --network=projects/123/global/networks/test-network \ + --project=example --region=us-central1 REQUIRED FLAGS --display-name=DISPLAY_NAME diff --git a/gcloud/ai/index-endpoints/undeploy-index b/gcloud/ai/index-endpoints/undeploy-index index 12a39ac37..a489d1aa0 100644 --- a/gcloud/ai/index-endpoints/undeploy-index +++ b/gcloud/ai/index-endpoints/undeploy-index @@ -11,8 +11,7 @@ EXAMPLES 456 under project example in region us-central1, run: $ gcloud ai index-endpoints undeploy-index 456 --project=example \ - --region=us-central1 - --deployed-index-id=deployed-index-345 + --region=us-central1 --deployed-index-id=deployed-index-345 POSITIONAL ARGUMENTS Index endpoint resource - The index endpoint to undeploy an index. The diff --git a/gcloud/ai/indexes/create b/gcloud/ai/indexes/create index 09c1246bf..2a5fd1317 100644 --- a/gcloud/ai/indexes/create +++ b/gcloud/ai/indexes/create @@ -10,9 +10,9 @@ SYNOPSIS EXAMPLES To create an index under project example in region us-central1, run: - $ gcloud ai indexes create --display-name=index --description=test - --metadata-file=path/to/your/metadata.json - --project=example --region=us-central1 + $ gcloud ai indexes create --display-name=index --description=test \ + --metadata-file=path/to/your/metadata.json --project=example \ + --region=us-central1 REQUIRED FLAGS --display-name=DISPLAY_NAME diff --git a/gcloud/ai/indexes/update b/gcloud/ai/indexes/update index da45421ed..eac1a263c 100644 --- a/gcloud/ai/indexes/update +++ b/gcloud/ai/indexes/update @@ -10,9 +10,9 @@ SYNOPSIS EXAMPLES To update index 123 under project example in region us-central1, run: - $ gcloud ai indexes update --display-name=new-name - --metadata-file=path/to/your/metadata.json --project=example - --region=us-central1 + $ gcloud ai indexes update --display-name=new-name \ + --metadata-file=path/to/your/metadata.json --project=example \ + --region=us-central1 POSITIONAL ARGUMENTS Index resource - Index to update. The arguments in this group can be used diff --git a/gcloud/ai/models/upload b/gcloud/ai/models/upload index 1d6b4707a..b811ed6ad 100644 --- a/gcloud/ai/models/upload +++ b/gcloud/ai/models/upload @@ -23,9 +23,10 @@ EXAMPLES To upload a model under project example in region us-central1, run: $ gcloud ai models upload \ - --container-image-uri="gcr.io/example/my-image" - --description=example-model --display-name=my-model - --artifact-uri='gs://bucket/path' --project=example --region=us-central1 + --container-image-uri="gcr.io/example/my-image" \ + --description=example-model --display-name=my-model \ + --artifact-uri='gs://bucket/path' --project=example \ + --region=us-central1 REQUIRED FLAGS --container-image-uri=CONTAINER_IMAGE_URI diff --git a/gcloud/alpha/access-context-manager/policies/create b/gcloud/alpha/access-context-manager/policies/create index 07b8b4d6d..6f481bdae 100644 --- a/gcloud/alpha/access-context-manager/policies/create +++ b/gcloud/alpha/access-context-manager/policies/create @@ -34,7 +34,7 @@ EXAMPLES $ gcloud alpha access-context-manager policies create \ --organization=organizations/123 --scopes=folders/345 \ - --title="My Folder Policy" + --title="My Folder Policy" Only projects within this folder can be added to service perimeters within this policy. @@ -44,7 +44,7 @@ EXAMPLES $ gcloud alpha access-context-manager policies create \ --organization=organizations/123 --scopes=projects/567 \ - --title="My Project Policy" + --title="My Project Policy" REQUIRED FLAGS --organization=ORGANIZATION diff --git a/gcloud/alpha/active-directory/domains/backups/delete b/gcloud/alpha/active-directory/domains/backups/delete index b1cbf3e4d..98531661b 100644 --- a/gcloud/alpha/active-directory/domains/backups/delete +++ b/gcloud/alpha/active-directory/domains/backups/delete @@ -22,8 +22,7 @@ EXAMPLES $ gcloud alpha active-directory domains backups delete \ projects/my-proj/locations/global/domains/my-domain.com/\ - backups/my-backup \ - --async + backups/my-backup --async POSITIONAL ARGUMENTS Backup resource - Name of the Managed Microsoft AD domain backup you want diff --git a/gcloud/alpha/active-directory/domains/backups/update b/gcloud/alpha/active-directory/domains/backups/update index 764a19eda..261ac76ea 100644 --- a/gcloud/alpha/active-directory/domains/backups/update +++ b/gcloud/alpha/active-directory/domains/backups/update @@ -20,8 +20,7 @@ EXAMPLES $ gcloud alpha active-directory domains backups update \ projects/my-proj/locations/global/domains/my-domain.com/\ - backups/my-backup \ - --update-labels=l1=1,l2=2 + backups/my-backup --update-labels=l1=1,l2=2 POSITIONAL ARGUMENTS Backup resource - Name of the Managed Microsoft AD domain backup you want diff --git a/gcloud/alpha/active-directory/domains/create b/gcloud/alpha/active-directory/domains/create index d3e1e32f8..fe8842958 100644 --- a/gcloud/alpha/active-directory/domains/create +++ b/gcloud/alpha/active-directory/domains/create @@ -25,8 +25,9 @@ EXAMPLES address range 10.172.0.0/24. $ gcloud alpha active-directory domains create my-domain.com \ - --region=us-central1 --reserved-ip-range="10.172.0.0/24" - --authorized-networks=projects/my-project/global/networks/my-network + --region=us-central1 --reserved-ip-range="10.172.0.0/24" \ + --authorized-networks=projects/my-project/global/networks/\ + my-network POSITIONAL ARGUMENTS Domain resource - Name of the managed Managed Microsoft AD domain you want diff --git a/gcloud/alpha/active-directory/domains/trusts/create b/gcloud/alpha/active-directory/domains/trusts/create index b57af183a..bd2f9f93d 100644 --- a/gcloud/alpha/active-directory/domains/trusts/create +++ b/gcloud/alpha/active-directory/domains/trusts/create @@ -27,9 +27,10 @@ EXAMPLES my-domain.com and target-domain.com. $ gcloud alpha active-directory domains trusts create \ - my-domain.com --target-domain-name=target-domain.com - --target-dns-ip-addresses=10.177.0.2 --type=EXTERNAL --direction=BIDIRECTIONAL - --selective-authentication=false --async + my-domain.com --target-domain-name=target-domain.com \ + --target-dns-ip-addresses=10.177.0.2 --type=EXTERNAL \ + --direction=BIDIRECTIONAL --selective-authentication=false \ + --async POSITIONAL ARGUMENTS Domain resource - Name of the Managed Microsoft AD domain you want to diff --git a/gcloud/alpha/active-directory/domains/trusts/update b/gcloud/alpha/active-directory/domains/trusts/update index 4d7198c78..6a18e6114 100644 --- a/gcloud/alpha/active-directory/domains/trusts/update +++ b/gcloud/alpha/active-directory/domains/trusts/update @@ -24,9 +24,9 @@ EXAMPLES The following command updates the target DNS IP address for the AD trust between my-domain.com and my-target-domain.com to 10.177.0.3. - $ gcloud alpha active-directory domains trusts update \ - my-domain.com --target-domain-name=my-target-domain.com - --target-dns-ip-addresses=10.177.0.3 + $ gcloud alpha active-directory domains trusts update \ + my-domain.com --target-domain-name=my-target-domain.com \ + --target-dns-ip-addresses=10.177.0.3 POSITIONAL ARGUMENTS Domain resource - Name of the Managed Microsoft AD trust for which you diff --git a/gcloud/alpha/active-directory/domains/update b/gcloud/alpha/active-directory/domains/update index b5af42266..4f013429d 100644 --- a/gcloud/alpha/active-directory/domains/update +++ b/gcloud/alpha/active-directory/domains/update @@ -25,13 +25,13 @@ EXAMPLES us-west1: $ gcloud alpha active-directory domains update my-domain.com \ - --update-labels=env=test,service=foo \ - --add-region=us-west1 + --update-labels=env=test,service=foo --add-region=us-west1 This peers the domain my-domain.com to the network my-network. - $ gcloud alpha active-directory domains update my-domain.com - --add-authorized-networks=projects/my-project/global/networks/my-network + $ gcloud alpha active-directory domains update my-domain.com \ + --add-authorized-networks=projects/my-project/global/networks/\ + my-network POSITIONAL ARGUMENTS Domain resource - Name of the Managed Microsoft AD domain you want to diff --git a/gcloud/alpha/ai-platform/explain b/gcloud/alpha/ai-platform/explain index cf16a5c16..edae9f520 100644 --- a/gcloud/alpha/ai-platform/explain +++ b/gcloud/alpha/ai-platform/explain @@ -18,7 +18,7 @@ EXAMPLES 'version' and with the name 'model-name', run: $ gcloud alpha ai-platform explain explain --model=model-name \ - --version=version --json-instances=instances.json + --version=version --json-instances=instances.json REQUIRED FLAGS --model=MODEL diff --git a/gcloud/alpha/ai-platform/models/delete b/gcloud/alpha/ai-platform/models/delete index 43add6ff8..72a4a5558 100644 --- a/gcloud/alpha/ai-platform/models/delete +++ b/gcloud/alpha/ai-platform/models/delete @@ -10,8 +10,8 @@ EXAMPLES To delete all models matching the regular expression vision[0-9]+, run: $ gcloud alpha ai-platform models list --uri \ - --filter 'name ~ vision[0-9]+' | - xargs -n 1 gcloud alpha ai-platform models delete + --filter 'name ~ vision[0-9]+' | xargs -n 1 gcloud alpha \ + ai-platform models delete POSITIONAL ARGUMENTS MODEL diff --git a/gcloud/alpha/ai/custom-jobs/create b/gcloud/alpha/ai/custom-jobs/create index caa7cfb03..b67f0e448 100644 --- a/gcloud/alpha/ai/custom-jobs/create +++ b/gcloud/alpha/ai/custom-jobs/create @@ -20,9 +20,10 @@ EXAMPLES To create a job under project example in region us-central1, run: $ gcloud alpha ai custom-jobs create --region=us-central1 \ - --project=example - --worker-pool-spec=replica-count=1,machine-type='n1-highmem-2',container-image-uri='gcr.io/ucaip-test/ucaip-training-test' - --display-name=test + --project=example \ + --worker-pool-spec=replica-count=1,machine-type='n1-highmem-2',\ + container-image-uri='gcr.io/ucaip-test/ucaip-training-test' \ + --display-name=test REQUIRED FLAGS --display-name=DISPLAY_NAME diff --git a/gcloud/alpha/ai/endpoints/create b/gcloud/alpha/ai/endpoints/create index 28add79ab..a68b69f0d 100644 --- a/gcloud/alpha/ai/endpoints/create +++ b/gcloud/alpha/ai/endpoints/create @@ -11,8 +11,7 @@ EXAMPLES To create an endpoint under project example in region us-central1, run: $ gcloud alpha ai endpoints create --project=example \ - --region=us-central1 - --display-name=my_endpoint + --region=us-central1 --display-name=my_endpoint REQUIRED FLAGS --display-name=DISPLAY_NAME diff --git a/gcloud/alpha/ai/endpoints/deploy-model b/gcloud/alpha/ai/endpoints/deploy-model index 925483a78..843be378b 100644 --- a/gcloud/alpha/ai/endpoints/deploy-model +++ b/gcloud/alpha/ai/endpoints/deploy-model @@ -19,8 +19,8 @@ EXAMPLES us-central1, run: $ gcloud alpha ai endpoints deploy-model 123 --project=example \ - --region=us-central1 --model=456 - --display-name=my_deployed_model + --region=us-central1 --model=456 \ + --display-name=my_deployed_model POSITIONAL ARGUMENTS Endpoint resource - The endpoint to deploy a model to. The arguments in diff --git a/gcloud/alpha/ai/endpoints/predict b/gcloud/alpha/ai/endpoints/predict index 4aaf31697..4456fcde9 100644 --- a/gcloud/alpha/ai/endpoints/predict +++ b/gcloud/alpha/ai/endpoints/predict @@ -16,8 +16,7 @@ EXAMPLES us-central1, run: $ gcloud alpha ai endpoints predict 123 --project=example \ - --region=us-central1 - --json-request=input.json + --region=us-central1 --json-request=input.json POSITIONAL ARGUMENTS Endpoint resource - The endpoint to do online prediction. The arguments in diff --git a/gcloud/alpha/ai/endpoints/raw-predict b/gcloud/alpha/ai/endpoints/raw-predict index 94e3f57f8..bcccf9cfe 100644 --- a/gcloud/alpha/ai/endpoints/raw-predict +++ b/gcloud/alpha/ai/endpoints/raw-predict @@ -31,8 +31,8 @@ EXAMPLES To send the image file image.jpeg and set the content type, run: $ gcloud alpha ai endpoints raw-predict 123 --project=example \ - --region=us-central1 - --http-headers=Content-Type=image/jpeg --request=@image.jpeg + --region=us-central1 --http-headers=Content-Type=image/jpeg \ + --request=@image.jpeg POSITIONAL ARGUMENTS Endpoint resource - The endpoint to do online raw prediction. The diff --git a/gcloud/alpha/ai/endpoints/undeploy-model b/gcloud/alpha/ai/endpoints/undeploy-model index 73ee350c7..d4b91f53c 100644 --- a/gcloud/alpha/ai/endpoints/undeploy-model +++ b/gcloud/alpha/ai/endpoints/undeploy-model @@ -12,8 +12,7 @@ EXAMPLES region us-central1, run: $ gcloud alpha ai endpoints undeploy-model 123 --project=example \ - --region=us-central1 - --deployed-model-id=456 + --region=us-central1 --deployed-model-id=456 POSITIONAL ARGUMENTS Endpoint resource - The endpoint to undeploy a model from. The arguments diff --git a/gcloud/alpha/ai/endpoints/update b/gcloud/alpha/ai/endpoints/update index 7c01dc996..b5e2d8fba 100644 --- a/gcloud/alpha/ai/endpoints/update +++ b/gcloud/alpha/ai/endpoints/update @@ -13,8 +13,7 @@ EXAMPLES To update an endpoint 123 under project example in region us-central1, run: $ gcloud alpha ai endpoints update 123 --project=example \ - --region=us-central1 - --display-name=new_name + --region=us-central1 --display-name=new_name POSITIONAL ARGUMENTS Endpoint resource - The endpoint to update. The arguments in this group diff --git a/gcloud/alpha/ai/index-endpoints/create b/gcloud/alpha/ai/index-endpoints/create index 987da6d3a..7e01ec469 100644 --- a/gcloud/alpha/ai/index-endpoints/create +++ b/gcloud/alpha/ai/index-endpoints/create @@ -12,9 +12,9 @@ EXAMPLES projects/123/global/networks/test-network in region us-central1, run: $ gcloud alpha ai index-endpoints create \ - --display-name=index-endpoint --description=test - --network=projects/123/global/networks/test-network - --project=example --region=us-central1 + --display-name=index-endpoint --description=test \ + --network=projects/123/global/networks/test-network \ + --project=example --region=us-central1 REQUIRED FLAGS --display-name=DISPLAY_NAME diff --git a/gcloud/alpha/ai/index-endpoints/undeploy-index b/gcloud/alpha/ai/index-endpoints/undeploy-index index 93c8bc754..a86ed5ada 100644 --- a/gcloud/alpha/ai/index-endpoints/undeploy-index +++ b/gcloud/alpha/ai/index-endpoints/undeploy-index @@ -12,8 +12,8 @@ EXAMPLES 456 under project example in region us-central1, run: $ gcloud alpha ai index-endpoints undeploy-index 456 \ - --project=example --region=us-central1 - --deployed-index-id=deployed-index-345 + --project=example --region=us-central1 \ + --deployed-index-id=deployed-index-345 POSITIONAL ARGUMENTS Index endpoint resource - The index endpoint to undeploy an index. The diff --git a/gcloud/alpha/ai/indexes/create b/gcloud/alpha/ai/indexes/create index 5e8436d15..493d913ce 100644 --- a/gcloud/alpha/ai/indexes/create +++ b/gcloud/alpha/ai/indexes/create @@ -11,9 +11,8 @@ EXAMPLES To create an index under project example in region us-central1, run: $ gcloud alpha ai indexes create --display-name=index \ - --description=test - --metadata-file=path/to/your/metadata.json - --project=example --region=us-central1 + --description=test --metadata-file=path/to/your/metadata.json \ + --project=example --region=us-central1 REQUIRED FLAGS --display-name=DISPLAY_NAME diff --git a/gcloud/alpha/ai/indexes/update b/gcloud/alpha/ai/indexes/update index 3a9c22f22..1721d389a 100644 --- a/gcloud/alpha/ai/indexes/update +++ b/gcloud/alpha/ai/indexes/update @@ -10,9 +10,9 @@ SYNOPSIS EXAMPLES To update index 123 under project example in region us-central1, run: - $ gcloud alpha ai indexes update --display-name=new-name - --metadata-file=path/to/your/metadata.json --project=example - --region=us-central1 + $ gcloud alpha ai indexes update --display-name=new-name \ + --metadata-file=path/to/your/metadata.json --project=example \ + --region=us-central1 POSITIONAL ARGUMENTS Index resource - Index to update. The arguments in this group can be used diff --git a/gcloud/alpha/ai/models/upload b/gcloud/alpha/ai/models/upload index 38f3a039b..12bde610a 100644 --- a/gcloud/alpha/ai/models/upload +++ b/gcloud/alpha/ai/models/upload @@ -23,9 +23,10 @@ EXAMPLES To upload a model under project example in region us-central1, run: $ gcloud alpha ai models upload \ - --container-image-uri="gcr.io/example/my-image" - --description=example-model --display-name=my-model - --artifact-uri='gs://bucket/path' --project=example --region=us-central1 + --container-image-uri="gcr.io/example/my-image" \ + --description=example-model --display-name=my-model \ + --artifact-uri='gs://bucket/path' --project=example \ + --region=us-central1 REQUIRED FLAGS --container-image-uri=CONTAINER_IMAGE_URI diff --git a/gcloud/alpha/anthos/auth/login b/gcloud/alpha/anthos/auth/login index efd0d7de5..18d15031c 100644 --- a/gcloud/alpha/anthos/auth/login +++ b/gcloud/alpha/anthos/auth/login @@ -19,7 +19,7 @@ EXAMPLES To add credentials to custom kubeconfig file: - $ gcloud alpha anthos auth login --cluster=testcluster \ + $ gcloud alpha anthos auth login --cluster=testcluster \ --login-config=kubectl-anthos-config.yaml \ --kubeconfig=my.kubeconfig diff --git a/gcloud/alpha/api-gateway/apis/remove-iam-policy-binding b/gcloud/alpha/api-gateway/apis/remove-iam-policy-binding index d74cc31ad..6625acbaa 100644 --- a/gcloud/alpha/api-gateway/apis/remove-iam-policy-binding +++ b/gcloud/alpha/api-gateway/apis/remove-iam-policy-binding @@ -14,8 +14,7 @@ EXAMPLES 'test-user@gmail.com' on API 'my-api', run: $ gcloud alpha api-gateway apis remove-iam-policy-binding my-api \ - --member='user:test-user@gmail.com' - --role='roles/editor' + --member='user:test-user@gmail.com' --role='roles/editor' POSITIONAL ARGUMENTS Api resource - Name for API which IAM policy binding will be added to. diff --git a/gcloud/alpha/api-gateway/gateways/remove-iam-policy-binding b/gcloud/alpha/api-gateway/gateways/remove-iam-policy-binding index 9aeb55431..ed9a09f8d 100644 --- a/gcloud/alpha/api-gateway/gateways/remove-iam-policy-binding +++ b/gcloud/alpha/api-gateway/gateways/remove-iam-policy-binding @@ -15,9 +15,8 @@ EXAMPLES 'test-user@gmail.com' on Gateway 'my-gateway' in us-central1, run: $ gcloud alpha api-gateway gateways remove-iam-policy-binding \ - my-gateway --location='us-central1' - --member='user:test-user@gmail.com' - --role='roles/editor' + my-gateway --location='us-central1' \ + --member='user:test-user@gmail.com' --role='roles/editor' POSITIONAL ARGUMENTS Gateway resource - Name for gateway which will be IAM policy binding will diff --git a/gcloud/alpha/apigee/products/update b/gcloud/alpha/apigee/products/update index 3b18178c8..dca281096 100644 --- a/gcloud/alpha/apigee/products/update +++ b/gcloud/alpha/apigee/products/update @@ -70,7 +70,7 @@ EXAMPLES attribute baz if it exists, run: $ gcloud alpha apigee products update my-prod \ - --add-attribute="foo=bar" --remove-attribute=baz + --add-attribute="foo=bar" --remove-attribute=baz To update the list of API proxies included in the API product, run: diff --git a/gcloud/alpha/app/ssl-certificates/create b/gcloud/alpha/app/ssl-certificates/create index 9aa65161a..a22655f5a 100644 --- a/gcloud/alpha/app/ssl-certificates/create +++ b/gcloud/alpha/app/ssl-certificates/create @@ -15,8 +15,8 @@ EXAMPLES To add a new SSL certificate to App Engine, run: $ gcloud alpha app ssl-certificates create \ - --display-name='example cert' \ - --certificate='/home/user/me/my_cert.cer' \ + --display-name='example cert' \ + --certificate='/home/user/me/my_cert.cer' \ --private-key='/home/user/me/my_key.pfx' REQUIRED FLAGS diff --git a/gcloud/alpha/app/ssl-certificates/update b/gcloud/alpha/app/ssl-certificates/update index 45ca40254..f4c770add 100644 --- a/gcloud/alpha/app/ssl-certificates/update +++ b/gcloud/alpha/app/ssl-certificates/update @@ -13,8 +13,8 @@ EXAMPLES To update an App Engine SSL certificate, run: $ gcloud alpha app ssl-certificates update 1234 \ - --display-name='updated name' \ - --certificate='/home/user/me/new_cert.cer' \ + --display-name='updated name' \ + --certificate='/home/user/me/new_cert.cer' \ --private-key='/home/user/me/new_key.pfx' POSITIONAL ARGUMENTS diff --git a/gcloud/alpha/artifacts/repositories/help b/gcloud/alpha/artifacts/repositories/help index 28f256cc8..4e4b06dd9 100644 --- a/gcloud/alpha/artifacts/repositories/help +++ b/gcloud/alpha/artifacts/repositories/help @@ -33,15 +33,16 @@ EXAMPLES To add an IAM policy binding for the role of 'roles/editor' for the user 'test-user@gmail.com' on repository my-repo, run: - $ gcloud alpha artifacts repositories add-iam-policy-binding my-repo - --member='user:test-user@gmail.com' --role='roles/editor' + $ gcloud alpha artifacts repositories add-iam-policy-binding \ + my-repo --member='user:test-user@gmail.com' \ + --role='roles/editor' To remove an IAM policy binding for the role of 'roles/editor' for the user 'test-user@gmail.com' on repository my-repo, run: $ gcloud alpha artifacts repositories remove-iam-policy-binding \ - my-repo - --member='user:test-user@gmail.com' --role='roles/editor' + my-repo --member='user:test-user@gmail.com' \ + --role='roles/editor' GCLOUD WIDE FLAGS These flags are available to all commands: --help. diff --git a/gcloud/alpha/asset/feeds/create b/gcloud/alpha/asset/feeds/create index e7b740e1b..df2a80fb5 100644 --- a/gcloud/alpha/asset/feeds/create +++ b/gcloud/alpha/asset/feeds/create @@ -19,9 +19,10 @@ EXAMPLES To create a new feed 'feed1' in project 'p1' which alerts on compute disks and network resources types, run: - $ gcloud alpha asset feeds create feed1 --project=p1 - --asset-types=compute.googleapis.com/Network,compute.googleapis.com/Disk - --content-type=resource --pubsub-topic=projects/project1/topics/feed-topic + $ gcloud alpha asset feeds create feed1 --project=p1 \ + --asset-types=compute.googleapis.com/Network,\ + compute.googleapis.com/Disk --content-type=resource \ + --pubsub-topic=projects/project1/topics/feed-topic POSITIONAL ARGUMENTS FEED_ID diff --git a/gcloud/alpha/asset/feeds/update b/gcloud/alpha/asset/feeds/update index ee9d9ded7..052fb7379 100644 --- a/gcloud/alpha/asset/feeds/update +++ b/gcloud/alpha/asset/feeds/update @@ -27,8 +27,8 @@ DESCRIPTION EXAMPLES To add an asset-type to an existing feed, run: - $ gcloud alpha asset feeds update feed1 --project=p1 - --add-asset-types=pubsub.googleapis.com/Topic + $ gcloud alpha asset feeds update feed1 --project=p1 \ + --add-asset-types=pubsub.googleapis.com/Topic POSITIONAL ARGUMENTS FEED_ID diff --git a/gcloud/alpha/auth/activate-service-account b/gcloud/alpha/auth/activate-service-account index 746a32ff5..396de8a33 100644 --- a/gcloud/alpha/auth/activate-service-account +++ b/gcloud/alpha/auth/activate-service-account @@ -46,8 +46,8 @@ EXAMPLES account while also specifying a project, run: $ gcloud alpha auth activate-service-account \ - SERVICE_ACCOUNT@DOMAIN.COM \ - --key-file=/path/key.json --project=PROJECT_ID + SERVICE_ACCOUNT@DOMAIN.COM --key-file=/path/key.json \ + --project=PROJECT_ID POSITIONAL ARGUMENTS [ACCOUNT] diff --git a/gcloud/alpha/auth/configure-docker b/gcloud/alpha/auth/configure-docker index 74d4f9dfe..c0692fdb8 100644 --- a/gcloud/alpha/auth/configure-docker +++ b/gcloud/alpha/auth/configure-docker @@ -22,16 +22,32 @@ DESCRIPTION For more details on Docker registries, see https://docs.docker.com/registry/. + For more details on how to authenticate to Google Container Registry using + this command, see + https://cloud.google.com/container-registry/docs/advanced-authentication#gcloud-helper. + + For more details on Google Container Registry's standalone credential + helpers, see https://github.com/GoogleCloudPlatform/docker-credential-gcr. + For more details on Docker credential helpers, see https://docs.docker.com/engine/reference/commandline/login/#credential-helpers. - For more details on the Google Container Registry's Docker credential - helper, see https://github.com/GoogleCloudPlatform/docker-credential-gcr. +EXAMPLES + To configure docker authentication after logging into gcloud, run: + + $ gcloud alpha auth configure-docker + + To configure docker authentication with Container Registry, e.g., gcr.io, + run: + + $ gcloud alpha auth configure-docker gcr.io POSITIONAL ARGUMENTS [REGISTRIES] The comma-separated list of registries to configure the credential - helper for. + helper for. Container Registry is a service for storing private + container images. For available registries, see + https://cloud.google.com/container-registry/docs/pushing-and-pulling#add-registry. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/bigtable/backups/create b/gcloud/alpha/bigtable/backups/create index fe8574afa..d59330f0a 100644 --- a/gcloud/alpha/bigtable/backups/create +++ b/gcloud/alpha/bigtable/backups/create @@ -17,15 +17,16 @@ EXAMPLES which expires at '2019-03-30T10:49:41Z', run: $ gcloud alpha bigtable backups create BACKUP_NAME \ - --instance=INSTANCE_NAME --cluster=CLUSTER_NAME - --table=TABLE_NAME --expiration-date=2019-03-30T10:49:41Z --async + --instance=INSTANCE_NAME --cluster=CLUSTER_NAME \ + --table=TABLE_NAME --expiration-date=2019-03-30T10:49:41Z \ + --async To create a backup 'BACKUP_NAME' syncronously from table 'TABLE_NAME' which expires in 2 weeks from now, run: $ gcloud alpha bigtable backups create BACKUP_NAME \ - --instance=INSTANCE_NAME --cluster=CLUSTER_NAME - --table=TABLE_NAME --retention-period=2w + --instance=INSTANCE_NAME --cluster=CLUSTER_NAME \ + --table=TABLE_NAME --retention-period=2w POSITIONAL ARGUMENTS Backup resource - The Cloud Bigtable backup to create. The arguments in diff --git a/gcloud/alpha/bigtable/backups/update b/gcloud/alpha/bigtable/backups/update index 4a4e336d4..78975f46f 100644 --- a/gcloud/alpha/bigtable/backups/update +++ b/gcloud/alpha/bigtable/backups/update @@ -16,8 +16,8 @@ EXAMPLES To update the expire time of backup 'BACKUP_NAME' to 7 days from now, run: $ gcloud alpha bigtable backups update BACKUP_NAME \ - --instance=INSTANCE_NAME --cluster=CLUSTER_NAME - --retention-period=7d + --instance=INSTANCE_NAME --cluster=CLUSTER_NAME \ + --retention-period=7d POSITIONAL ARGUMENTS Backup resource - Cloud Bigtable backup to update. The arguments in this diff --git a/gcloud/alpha/bms/instances/update b/gcloud/alpha/bms/instances/update index 94de54be7..606e0b594 100644 --- a/gcloud/alpha/bms/instances/update +++ b/gcloud/alpha/bms/instances/update @@ -17,7 +17,7 @@ EXAMPLES To update an instance called my-instance in region us-central1 with a new label key1=value1, run: - $ gcloud alpha bms instances update my-instance \ + $ gcloud alpha bms instances update my-instance \ --region=us-central1 --update-labels=key1=value1 To clear all labels, run: diff --git a/gcloud/alpha/bms/networks/update b/gcloud/alpha/bms/networks/update index 139a5b90c..24b70be94 100644 --- a/gcloud/alpha/bms/networks/update +++ b/gcloud/alpha/bms/networks/update @@ -17,8 +17,8 @@ EXAMPLES To update an network called my-network in region us-central1 with a new label key1=value1, run: - $ gcloud alpha bms networks update my-network \ - --region=us-central1 --update-labels=key1=value1 + $ gcloud alpha bms networks update my-network --region=us-central1 \ + --update-labels=key1=value1 To clear all labels, run: diff --git a/gcloud/alpha/bms/nfs-shares/update b/gcloud/alpha/bms/nfs-shares/update index 71d27a6a6..0f05c747e 100644 --- a/gcloud/alpha/bms/nfs-shares/update +++ b/gcloud/alpha/bms/nfs-shares/update @@ -17,8 +17,8 @@ EXAMPLES To update an NFS share called my-share in region us-central1 with a new label key1=value1, run: - $ gcloud alpha bms nfs-shares update my-share \ - --region=us-central1 --update-labels=key1=value1 + $ gcloud alpha bms nfs-shares update my-share --region=us-central1 \ + --update-labels=key1=value1 To clear all labels, run: diff --git a/gcloud/alpha/bq/datasets/create b/gcloud/alpha/bq/datasets/create index 6fc689678..a13c31323 100644 --- a/gcloud/alpha/bq/datasets/create +++ b/gcloud/alpha/bq/datasets/create @@ -12,13 +12,13 @@ DESCRIPTION EXAMPLES The following command creates a dataset with ID my-dataset - $ gcloud alpha bq datasets create my-dataset \ + $ gcloud alpha bq datasets create my-dataset \ --description 'My New Dataset' The following command creates a dataset with ID my-other-dataset, overwritting destination if it exists: - $ gcloud alpha bq datasets create my-other-dataset \ + $ gcloud alpha bq datasets create my-other-dataset \ --description 'My Other Dataset' --if-exists 'overwrite' POSITIONAL ARGUMENTS diff --git a/gcloud/alpha/bq/datasets/delete b/gcloud/alpha/bq/datasets/delete index a1b956128..a2be5ecec 100644 --- a/gcloud/alpha/bq/datasets/delete +++ b/gcloud/alpha/bq/datasets/delete @@ -11,7 +11,7 @@ DESCRIPTION EXAMPLES The following command deletes a dataset with ID my-dataset - $ gcloud alpha bq datasets delete my-dataset + $ gcloud alpha bq datasets delete my-dataset POSITIONAL ARGUMENTS Dataset resource - The BigQuery dataset you want to delete. This diff --git a/gcloud/alpha/bq/datasets/describe b/gcloud/alpha/bq/datasets/describe index ffeb09266..51f6b0f1d 100644 --- a/gcloud/alpha/bq/datasets/describe +++ b/gcloud/alpha/bq/datasets/describe @@ -10,7 +10,7 @@ DESCRIPTION EXAMPLES The following command fetches details about a dataset with ID my-dataset - $ gcloud alpha bq datasets describe my-dataset + $ gcloud alpha bq datasets describe my-dataset POSITIONAL ARGUMENTS Dataset resource - The BigQuery dataset you want to describe. This diff --git a/gcloud/alpha/bq/datasets/list b/gcloud/alpha/bq/datasets/list index b9e6c8aec..ca23bd55d 100644 --- a/gcloud/alpha/bq/datasets/list +++ b/gcloud/alpha/bq/datasets/list @@ -12,7 +12,7 @@ EXAMPLES The following command list all datasets in current project (including hidden) - $ gcloud alpha bq datasets list --all + $ gcloud alpha bq datasets list --all FLAGS --all diff --git a/gcloud/alpha/bq/datasets/update b/gcloud/alpha/bq/datasets/update index 840c2c94a..47d5fcc95 100644 --- a/gcloud/alpha/bq/datasets/update +++ b/gcloud/alpha/bq/datasets/update @@ -12,7 +12,7 @@ EXAMPLES The following command updates the description on a dataset with ID my-dataset - $ gcloud alpha bq datasets update my-dataset \ + $ gcloud alpha bq datasets update my-dataset \ --description 'My New Dataset Description' POSITIONAL ARGUMENTS diff --git a/gcloud/alpha/bq/jobs/cancel b/gcloud/alpha/bq/jobs/cancel index 2e890d098..3f1cd3ec0 100644 --- a/gcloud/alpha/bq/jobs/cancel +++ b/gcloud/alpha/bq/jobs/cancel @@ -11,7 +11,7 @@ EXAMPLES The following command cancels a job named my-query-job and returns the final state of the job: - $ gcloud alpha bq jobs cancel my-query-job + $ gcloud alpha bq jobs cancel my-query-job POSITIONAL ARGUMENTS Job resource - The BigQuery job to cancel. This represents a Cloud diff --git a/gcloud/alpha/bq/jobs/describe b/gcloud/alpha/bq/jobs/describe index b9b4929ef..70d2f088a 100644 --- a/gcloud/alpha/bq/jobs/describe +++ b/gcloud/alpha/bq/jobs/describe @@ -10,7 +10,7 @@ DESCRIPTION EXAMPLES The following command displays details for job named my-query-job - $ gcloud alpha bq jobs describe my-query-job + $ gcloud alpha bq jobs describe my-query-job POSITIONAL ARGUMENTS Job resource - The BigQuery job to display details for. This represents a diff --git a/gcloud/alpha/bq/jobs/list b/gcloud/alpha/bq/jobs/list index 847f0ce5f..792eab52f 100644 --- a/gcloud/alpha/bq/jobs/list +++ b/gcloud/alpha/bq/jobs/list @@ -12,7 +12,7 @@ DESCRIPTION EXAMPLES The following command list all jobs in current project (for all users) - $ gcloud alpha bq jobs list --show-all-users + $ gcloud alpha bq jobs list --show-all-users FLAGS --show-all-users diff --git a/gcloud/alpha/bq/tables/create b/gcloud/alpha/bq/tables/create index 9abb3a58f..ddea37735 100644 --- a/gcloud/alpha/bq/tables/create +++ b/gcloud/alpha/bq/tables/create @@ -17,15 +17,17 @@ DESCRIPTION EXAMPLES The following command creates a table with ID my-table in my-dataset: - $ gcloud alpha bq tables create \ + $ gcloud alpha bq tables create \ /projects/myproject/datasets/my-dataset/tables/my-table \ --description 'My New Table' The following command creates a view with ID my-view in dataset my-other-dataset: - $ gcloud alpha bq tables create my-view --dataset my-other-dataset \ - --view 'SELECT field1, field3 FROM `my-project.my-other-dataset.my-table`' + $ gcloud alpha bq tables create my-view --dataset my-other-dataset \ + --view \ + 'SELECT field1, field3 FROM + `my-project.my-other-dataset.my-table`' POSITIONAL ARGUMENTS Table resource - The BigQuery table you want to create. The arguments in diff --git a/gcloud/alpha/bq/tables/delete b/gcloud/alpha/bq/tables/delete index 4344db3a8..c7b33cbec 100644 --- a/gcloud/alpha/bq/tables/delete +++ b/gcloud/alpha/bq/tables/delete @@ -11,7 +11,7 @@ DESCRIPTION EXAMPLES The following command deletes a table with ID my-table - $ gcloud alpha bq tables delete my-table + $ gcloud alpha bq tables delete my-table POSITIONAL ARGUMENTS Table resource - The BigQuery table you want to delete. The arguments in diff --git a/gcloud/alpha/bq/tables/describe b/gcloud/alpha/bq/tables/describe index 317a7a8ba..84e19a90d 100644 --- a/gcloud/alpha/bq/tables/describe +++ b/gcloud/alpha/bq/tables/describe @@ -11,7 +11,7 @@ DESCRIPTION EXAMPLES The following command fetches details about a table with ID my-table - $ gcloud alpha bq tables describe my-table + $ gcloud alpha bq tables describe my-table POSITIONAL ARGUMENTS Table resource - The BigQuery table you want to describe. The arguments in diff --git a/gcloud/alpha/bq/tables/list b/gcloud/alpha/bq/tables/list index 3661ce8ba..0456c0aeb 100644 --- a/gcloud/alpha/bq/tables/list +++ b/gcloud/alpha/bq/tables/list @@ -13,7 +13,7 @@ DESCRIPTION EXAMPLES The following command list all tables the specified dataset - $ gcloud alpha bq tables list --dataset my-dataset + $ gcloud alpha bq tables list --dataset my-dataset REQUIRED FLAGS Dataset resource - The BigQuery dataset you want to list datasets for. diff --git a/gcloud/alpha/bq/tables/show-rows b/gcloud/alpha/bq/tables/show-rows index f45500aed..1cc62303e 100644 --- a/gcloud/alpha/bq/tables/show-rows +++ b/gcloud/alpha/bq/tables/show-rows @@ -13,7 +13,7 @@ EXAMPLES The following command displays 150 rows of my-table in my-dataset starting from row 10: - $ gcloud alpha bq tables show-rows \ + $ gcloud alpha bq tables show-rows \ --table \ /projects/myproject/datasets/my-dataset/tables/my-table \ --limit 150 --start 10 diff --git a/gcloud/alpha/bq/tables/update b/gcloud/alpha/bq/tables/update index e6a929fec..f1834436f 100644 --- a/gcloud/alpha/bq/tables/update +++ b/gcloud/alpha/bq/tables/update @@ -16,7 +16,7 @@ EXAMPLES The following command updates the description on a table with ID my-table in my-dataset: - $ gcloud alpha bq tables update \ + $ gcloud alpha bq tables update \ /projects/myproject/datasets/my-dataset/tables/my-table \ --description 'My New Table' @@ -24,9 +24,8 @@ EXAMPLES the value and tags columns in a table with ID my-other-table in dataset my-other-dataset: - $ gcloud alpha bq tables update my-other-table \ - --dataset my-other-dataset \ - --relax-columns name,tags + $ gcloud alpha bq tables update my-other-table \ + --dataset my-other-dataset --relax-columns name,tags POSITIONAL ARGUMENTS Table resource - The BigQuery table you want to update. The arguments in diff --git a/gcloud/alpha/builds/submit b/gcloud/alpha/builds/submit index 58c181347..8ea9446f2 100644 --- a/gcloud/alpha/builds/submit +++ b/gcloud/alpha/builds/submit @@ -25,7 +25,7 @@ EXAMPLES To submit a build with source located at storage URL gs://bucket/object.zip: - $ gcloud alpha builds submit "gs://bucket/object.zip" \ + $ gcloud alpha builds submit "gs://bucket/object.zip" \ --tag=gcr.io/my-project/image To submit a build with source located at storage URL gs://bucket/object.zip diff --git a/gcloud/alpha/certificate-manager/certificates/create b/gcloud/alpha/certificate-manager/certificates/create index f429719f1..243b77bef 100644 --- a/gcloud/alpha/certificate-manager/certificates/create +++ b/gcloud/alpha/certificate-manager/certificates/create @@ -37,7 +37,7 @@ EXAMPLES $ gcloud alpha certificate-manager certificates create \ api-example-com --dns-authorizations=api-example-com \ - --domains="api.example.com" + --domains="api.example.com" POSITIONAL ARGUMENTS Certificate resource - The name of the certificate to create. The diff --git a/gcloud/alpha/certificate-manager/certificates/update b/gcloud/alpha/certificate-manager/certificates/update index aec29b4d0..f0547a713 100644 --- a/gcloud/alpha/certificate-manager/certificates/update +++ b/gcloud/alpha/certificate-manager/certificates/update @@ -16,7 +16,7 @@ EXAMPLES To update a certificate with name simple-cert, run: $ gcloud alpha certificate-manager certificates update simple-cert \ - --description="desc" --update-labels="key=value" + --description="desc" --update-labels="key=value" \ --certificate-file=cert.pem --private-key-file=key.pem POSITIONAL ARGUMENTS diff --git a/gcloud/alpha/certificate-manager/maps/entries/update b/gcloud/alpha/certificate-manager/maps/entries/update index 2967f1376..1a4abc921 100644 --- a/gcloud/alpha/certificate-manager/maps/entries/update +++ b/gcloud/alpha/certificate-manager/maps/entries/update @@ -16,8 +16,8 @@ EXAMPLES To update a certificate map entry with name simple-entry, run: $ gcloud alpha certificate-manager maps entries update \ - simple-entry --map="simple-map" --description="desc" - --update-labels="key=value" --certificates="simple-cert" + simple-entry --map="simple-map" --description="desc" \ + --update-labels="key=value" --certificates="simple-cert" POSITIONAL ARGUMENTS Certificate map entry resource - The certificate map entry to update. The diff --git a/gcloud/alpha/code/dev b/gcloud/alpha/code/dev index 655a0dfd7..e0b603306 100644 --- a/gcloud/alpha/code/dev +++ b/gcloud/alpha/code/dev @@ -37,8 +37,8 @@ EXAMPLES this command with the --application-default-credential flag. $ gcloud auth application-default login - $ gcloud alpha code dev --dockerfile= \ - --application-default-credential + $ gcloud alpha code dev --dockerfile= \ + --application-default-credential POSITIONAL ARGUMENTS [SERVICE_CONFIG] diff --git a/gcloud/alpha/compute/addresses/create b/gcloud/alpha/compute/addresses/create index 11a5313d5..0bbd3fdf5 100644 --- a/gcloud/alpha/compute/addresses/create +++ b/gcloud/alpha/compute/addresses/create @@ -42,28 +42,27 @@ EXAMPLES $ gcloud alpha compute addresses create SHARED-ADDRESS-1 \ --region=us-central1 --subnet=default \ - --purpose=SHARED_LOADBALANCER_VIP + --purpose=SHARED_LOADBALANCER_VIP To reserve an IP range '10.110.0.0/16' from the network 'default' for 'VPC_PEERING', run: $ gcloud alpha compute addresses create IP-RANGE-1 --global \ --addresses=10.110.0.0 --prefix-length=16 \ - --purpose=VPC_PEERING --network=default + --purpose=VPC_PEERING --network=default To reserve any IP range with prefix length '16' from the network 'default' for 'VPC_PEERING', run: $ gcloud alpha compute addresses create IP-RANGE-1 --global \ - --prefix-length=16 --purpose=VPC_PEERING \ - --network=default + --prefix-length=16 --purpose=VPC_PEERING --network=default To reserve an address from network 'default' for PRIVATE_SERVICE_CONNECT, run: $ gcloud alpha compute addresses create PSC-ADDRESS-1 --global \ - --addresses=10.110.0.10 \ - --purpose=PRIVATE_SERVICE_CONNECT --network=default + --addresses=10.110.0.10 --purpose=PRIVATE_SERVICE_CONNECT \ + --network=default POSITIONAL ARGUMENTS [NAME ...] diff --git a/gcloud/alpha/compute/addresses/update b/gcloud/alpha/compute/addresses/update index 6b7fd54d9..5c52244e4 100644 --- a/gcloud/alpha/compute/addresses/update +++ b/gcloud/alpha/compute/addresses/update @@ -16,8 +16,8 @@ EXAMPLES address 'example-address', run: $ gcloud alpha compute addresses update example-address \ - --region=us-central1 \ - --update-labels=k0=value1,k1=value2 --remove-labels=k3 + --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: diff --git a/gcloud/alpha/compute/backend-services/add-service-bindings b/gcloud/alpha/compute/backend-services/add-service-bindings index 016f0d8ae..5b886f762 100644 --- a/gcloud/alpha/compute/backend-services/add-service-bindings +++ b/gcloud/alpha/compute/backend-services/add-service-bindings @@ -13,8 +13,8 @@ DESCRIPTION EXAMPLES To add a service binding to a backend service, run: - $ gcloud alpha compute backend-services add-service-bindings NAME \ - --service-bindings=SERVICE_BINDING1 --global + $ gcloud alpha compute backend-services add-service-bindings NAME \ + --service-bindings=SERVICE_BINDING1 --global POSITIONAL ARGUMENTS BACKEND_SERVICE_NAME diff --git a/gcloud/alpha/compute/backend-services/remove-service-bindings b/gcloud/alpha/compute/backend-services/remove-service-bindings index d8b2d3a42..61e316218 100644 --- a/gcloud/alpha/compute/backend-services/remove-service-bindings +++ b/gcloud/alpha/compute/backend-services/remove-service-bindings @@ -14,7 +14,7 @@ EXAMPLES To remove a service binding from a backend service, run: $ gcloud alpha compute backend-services remove-service-bindings \ - NAME --service-bindings=SERVICE_BINDING1 --global + NAME --service-bindings=SERVICE_BINDING1 --global POSITIONAL ARGUMENTS BACKEND_SERVICE_NAME diff --git a/gcloud/alpha/compute/disks/create b/gcloud/alpha/compute/disks/create index 7ebf1ec32..41b645593 100644 --- a/gcloud/alpha/compute/disks/create +++ b/gcloud/alpha/compute/disks/create @@ -204,8 +204,8 @@ FLAGS needed. --primary-disk=PRIMARY_DISK - Primary disk from which data will replicate to the disk - asynchronously. + Primary disk for asynchronous replication. This flag is required when + creating a secondary disk. --source-disk=SOURCE_DISK Source disk used to create the disk(s). It is safe to delete a source @@ -271,14 +271,14 @@ FLAGS At most one of these can be specified: --primary-disk-region=PRIMARY_DISK_REGION - Region of the async primary disk, it cannot be the same as the region - of the secondary disk that's to be created. Overrides the default - compute/region property value for this command invocation. + Region of the primary disk for asynchronous replication. The primary + and secondary disks must not be in the same region. Overrides the + default compute/region property value for this command invocation. --primary-disk-zone=PRIMARY_DISK_ZONE - Zone of the async primary disk, it cannot be in the same region as - the secondary disk that's to be created. Overrides the default - compute/zone property value for this command invocation. + Zone of the primary disk for asynchronous replication. The primary + and secondary disks must not be in the same region. Overrides the + default compute/zone property value for this command invocation. At most one of these can be specified: @@ -326,14 +326,14 @@ FLAGS At most one of these can be specified: --source-disk-region=SOURCE_DISK_REGION - Region of the source disk, this argument is not required if target - disk is in same region of source disk. Overrides the default - compute/region property value for this command invocation. + Region of the source disk. This argument is not required if the + target disk is in the same region as the source disk. Overrides the + default compute/region property value for this command invocation. --source-disk-zone=SOURCE_DISK_ZONE - Zone of the source disk, this argument is not required if target disk - is in same zone of source disk. Overrides the default compute/zone - property value for this command invocation. + Zone of the source disk. This argument is not required if the target + disk is in the same zone as the source disk. 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, diff --git a/gcloud/alpha/compute/disks/stop-async-replication b/gcloud/alpha/compute/disks/stop-async-replication index 1dcdfbddd..245f7757b 100644 --- a/gcloud/alpha/compute/disks/stop-async-replication +++ b/gcloud/alpha/compute/disks/stop-async-replication @@ -35,9 +35,10 @@ POSITIONAL ARGUMENTS FLAGS --secondary-disk=SECONDARY_DISK - Secondary disk to stop asynchronous replication to. Supplied if and - only if the target disk is a primary disk in an asynchronously - replicated pair. + Secondary disk for asynchronous replication. This flag is required when + starting replication. It is also required when stopping replication on + the primary disk. It must not be used when stopping replication on the + secondary disk. At most one of these can be specified: @@ -85,12 +86,13 @@ FLAGS At most one of these can be specified: --secondary-disk-region=SECONDARY_DISK_REGION - Region of the async secondary disk. Overrides the default - compute/region property value for this command invocation. + Region of the secondary disk for asynchronous replication. Overrides + the default compute/region property value for this command + invocation. --secondary-disk-zone=SECONDARY_DISK_ZONE - Zone of the async secondary disk. Overrides the default compute/zone - property value for this command invocation. + Zone of the secondary disk for asynchronous replication. 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, diff --git a/gcloud/alpha/compute/external-vpn-gateways/update b/gcloud/alpha/compute/external-vpn-gateways/update index d98320e67..7454b3642 100644 --- a/gcloud/alpha/compute/external-vpn-gateways/update +++ b/gcloud/alpha/compute/external-vpn-gateways/update @@ -31,8 +31,7 @@ EXAMPLES To update labels for an external VPN gateway, run: $ gcloud alpha compute external-vpn-gateways update \ - my-external-gateway \ - --update-labels=k0=value1,k1=value2 + my-external-gateway --update-labels=k0=value1,k1=value2 POSITIONAL ARGUMENTS NAME diff --git a/gcloud/alpha/compute/firewall-policies/rules/create b/gcloud/alpha/compute/firewall-policies/rules/create index d663e0eca..67e4546bc 100644 --- a/gcloud/alpha/compute/firewall-policies/rules/create +++ b/gcloud/alpha/compute/firewall-policies/rules/create @@ -22,8 +22,8 @@ EXAMPLES with ID ``123456789", run: $ gcloud alpha compute firewall-policies rules create 10 \ - --firewall-policy=123456789 --action=allow - --description=example-rule + --firewall-policy=123456789 --action=allow \ + --description=example-rule POSITIONAL ARGUMENTS PRIORITY diff --git a/gcloud/alpha/compute/firewall-policies/rules/update b/gcloud/alpha/compute/firewall-policies/rules/update index 142ad4472..f437e9830 100644 --- a/gcloud/alpha/compute/firewall-policies/rules/update +++ b/gcloud/alpha/compute/firewall-policies/rules/update @@ -23,8 +23,8 @@ EXAMPLES ``new-example-rule", run: $ gcloud alpha compute firewall-policies rules update 10 \ - --firewall-policy=123456789 --action=allow - --description=new-example-rule + --firewall-policy=123456789 --action=allow \ + --description=new-example-rule POSITIONAL ARGUMENTS PRIORITY diff --git a/gcloud/alpha/compute/firewall-rules/create b/gcloud/alpha/compute/firewall-rules/create index f160c7890..dc0867911 100644 --- a/gcloud/alpha/compute/firewall-rules/create +++ b/gcloud/alpha/compute/firewall-rules/create @@ -25,16 +25,17 @@ EXAMPLES To create a firewall rule allowing incoming TCP traffic on port 8080, run: $ gcloud alpha compute firewall-rules create FooService \ - --allow=tcp:8080 - --description="Allow incoming traffic on TCP port 8080" --direction=INGRESS + --allow=tcp:8080 \ + --description="Allow incoming traffic on TCP port 8080" \ + --direction=INGRESS To create a firewall rule that allows TCP traffic through port 80 and determines a list of specific IP address blocks that are allowed to make inbound connections, run: $ gcloud alpha compute firewall-rules create "tcp-rule" \ - --allow=tcp:80 - --source-ranges="10.0.0.0/22,10.0.0.0/14" --description="Narrowing TCP traffic" + --allow=tcp:80 --source-ranges="10.0.0.0/22,10.0.0.0/14" \ + --description="Narrowing TCP traffic" To list existing firewall rules, run: diff --git a/gcloud/alpha/compute/forwarding-rules/update b/gcloud/alpha/compute/forwarding-rules/update index 160464584..ddb9c1260 100644 --- a/gcloud/alpha/compute/forwarding-rules/update +++ b/gcloud/alpha/compute/forwarding-rules/update @@ -23,8 +23,8 @@ EXAMPLES To add/update labels k0 and k1 and remove labels with key k3 , run: $ gcloud alpha compute forwarding-rules update example-fr \ - --region=us-central1 \ - --update-labels=k0=value1,k1=value2 --remove-labels=k3 + --region=us-central1 --update-labels=k0=value1,k1=value2 \ + --remove-labels=k3 Labels can be used to identify the forwarding rule and to filter them as in diff --git a/gcloud/alpha/compute/future-reservations/update b/gcloud/alpha/compute/future-reservations/update index 30a3b9a8d..1c6ff76c7 100644 --- a/gcloud/alpha/compute/future-reservations/update +++ b/gcloud/alpha/compute/future-reservations/update @@ -16,8 +16,8 @@ EXAMPLES $ gcloud alpha compute future-reservations update \ my-future-reservation --total-count=1000 \ - --start-time=2021-11-10T07:00:00Z - --end-time=2021-12-10T07:00:00Z --zone=us-central1-a + --start-time=2021-11-10T07:00:00Z \ + --end-time=2021-12-10T07:00:00Z --zone=us-central1-a POSITIONAL ARGUMENTS FUTURE_RESERVATION diff --git a/gcloud/alpha/compute/instance-groups/managed/create-instance b/gcloud/alpha/compute/instance-groups/managed/create-instance index 0bd77d532..d046a27b7 100644 --- a/gcloud/alpha/compute/instance-groups/managed/create-instance +++ b/gcloud/alpha/compute/instance-groups/managed/create-instance @@ -34,12 +34,15 @@ EXAMPLES IP on interface nic1, run: $ gcloud alpha compute instance-groups managed create-instance \ - my-group --region=europe-west4 \ - --instance=instance-1 \ - --stateful-disk='device-name=foo,source=https://compute.googleapis.com/compute/alpha/projects/my-project/zones/europe-west4/disks/disk-1,mode=rw,auto-delete=on-permanent-instance-deletion' \ - --stateful-metadata='my-key=my-value' \ - --stateful-internal-ip=address=192.168.0.10,auto-delete=on-permanent-instance-deletion \ - --stateful-external-ip=address=/projects/example-project/regions/europe-west4/addresses/my-address,interface-name=nic1 + my-group --region=europe-west4 --instance=instance-1 \ + --stateful-disk='device-name=foo,source=https://compute.googleap\ + is.com/compute/alpha/projects/my-project/zones/europe-west4/disks/di\ + sk-1,mode=rw,auto-delete=on-permanent-instance-deletion' \ + --stateful-metadata='my-key=my-value' \ + --stateful-internal-ip=address=192.168.0.10,\ + auto-delete=on-permanent-instance-deletion \ + --stateful-external-ip=address=/projects/example-project/\ + regions/europe-west4/addresses/my-address,interface-name=nic1 POSITIONAL ARGUMENTS NAME diff --git a/gcloud/alpha/compute/instance-groups/managed/describe-instance b/gcloud/alpha/compute/instance-groups/managed/describe-instance index 190a0e61c..73fb05b25 100644 --- a/gcloud/alpha/compute/instance-groups/managed/describe-instance +++ b/gcloud/alpha/compute/instance-groups/managed/describe-instance @@ -17,8 +17,7 @@ EXAMPLES run: $ gcloud alpha compute instance-groups managed describe-instance \ - my-group --instance=instance-1 \ - --region=europe-west4 + my-group --instance=instance-1 --region=europe-west4 POSITIONAL ARGUMENTS NAME diff --git a/gcloud/alpha/compute/instance-groups/managed/list-errors b/gcloud/alpha/compute/instance-groups/managed/list-errors index 33df24038..1cb430f7b 100644 --- a/gcloud/alpha/compute/instance-groups/managed/list-errors +++ b/gcloud/alpha/compute/instance-groups/managed/list-errors @@ -35,7 +35,7 @@ EXAMPLES To list errors on managed instance group 'my-group', run: $ gcloud alpha compute instance-groups managed list-errors \ - my-group --format=yaml + my-group --format=yaml POSITIONAL ARGUMENTS NAME diff --git a/gcloud/alpha/compute/instance-groups/managed/list-instances b/gcloud/alpha/compute/instance-groups/managed/list-instances index 37182a1ba..f48abc3e5 100644 --- a/gcloud/alpha/compute/instance-groups/managed/list-instances +++ b/gcloud/alpha/compute/instance-groups/managed/list-instances @@ -36,7 +36,7 @@ EXAMPLES my-group, including per-instance overrides, run: $ gcloud alpha compute instance-groups managed list-instances \ - my-group --format=yaml + my-group --format=yaml POSITIONAL ARGUMENTS NAME diff --git a/gcloud/alpha/compute/instance-groups/managed/update-instances b/gcloud/alpha/compute/instance-groups/managed/update-instances index a6143d37b..fbef8bc5c 100644 --- a/gcloud/alpha/compute/instance-groups/managed/update-instances +++ b/gcloud/alpha/compute/instance-groups/managed/update-instances @@ -35,9 +35,8 @@ EXAMPLES minimal-action=none and most-disruptive-allowed-action=restart, run: $ gcloud alpha compute instance-groups managed update-instances \ - my-group --instances=instance-1,instance2 \ - --minimal-action=none - --most-disruptive-allowed-action=restart + my-group --instances=instance-1,instance2 \ + --minimal-action=none --most-disruptive-allowed-action=restart POSITIONAL ARGUMENTS NAME diff --git a/gcloud/alpha/compute/instance-templates/create-with-container b/gcloud/alpha/compute/instance-templates/create-with-container index b5d3202f3..1f6c4bd50 100644 --- a/gcloud/alpha/compute/instance-templates/create-with-container +++ b/gcloud/alpha/compute/instance-templates/create-with-container @@ -68,16 +68,16 @@ EXAMPLES a command, run: $ gcloud alpha compute instance-templates create-with-container \ - instance-template-1 \ - --container-image=gcr.io/google-containers/busybox \ + instance-template-1 \ + --container-image=gcr.io/google-containers/busybox \ --container-command='echo "Hello world"' To create a template running gcr.io/google-containers/busybox in privileged mode, run: $ gcloud alpha compute instance-templates create-with-container \ - instance-template-1 \ - --container-image=gcr.io/google-containers/busybox \ + instance-template-1 \ + --container-image=gcr.io/google-containers/busybox \ --container-privileged POSITIONAL ARGUMENTS diff --git a/gcloud/alpha/compute/instances/create-with-container b/gcloud/alpha/compute/instances/create-with-container index e83132f58..4be330afb 100644 --- a/gcloud/alpha/compute/instances/create-with-container +++ b/gcloud/alpha/compute/instances/create-with-container @@ -77,15 +77,15 @@ EXAMPLES To run the gcr.io/google-containers/busybox image on an instance named 'instance-1' that executes 'echo "Hello world"' as a run command, run: - $ gcloud alpha compute instances create-with-container instance-1 \ - --container-image=gcr.io/google-containers/busybox \ - --container-command='echo "Hello world"' + $ gcloud alpha compute instances create-with-container instance-1 \ + --container-image=gcr.io/google-containers/busybox \ + --container-command='echo "Hello world"' To run the gcr.io/google-containers/busybox image in privileged mode, run: - $ gcloud alpha compute instances create-with-container instance-1 \ - --container-image=gcr.io/google-containers/busybox - --container-privileged + $ gcloud alpha compute instances create-with-container instance-1 \ + --container-image=gcr.io/google-containers/busybox \ + --container-privileged POSITIONAL ARGUMENTS INSTANCE_NAMES [INSTANCE_NAMES ...] diff --git a/gcloud/alpha/compute/instances/network-interfaces/get-effective-firewalls b/gcloud/alpha/compute/instances/network-interfaces/get-effective-firewalls index 94fdb7c3a..6fd9be121 100644 --- a/gcloud/alpha/compute/instances/network-interfaces/get-effective-firewalls +++ b/gcloud/alpha/compute/instances/network-interfaces/get-effective-firewalls @@ -20,7 +20,8 @@ EXAMPLES To get the effective firewalls of instance with name example-instance, run: $ gcloud alpha compute instances network-interfaces \ - get-effective-firewalls example-instance, + get-effective-firewalls example-instance + To show all fields of the firewall rules, please show in JSON format with option --format=json diff --git a/gcloud/alpha/compute/instances/os-inventory/list-instances b/gcloud/alpha/compute/instances/os-inventory/list-instances index 3b219db93..a54e6281a 100644 --- a/gcloud/alpha/compute/instances/os-inventory/list-instances +++ b/gcloud/alpha/compute/instances/os-inventory/list-instances @@ -37,43 +37,39 @@ EXAMPLES installed, run: $ gcloud alpha compute instances os-inventory list-instances \ - --package-name="google-cloud-sdk" \ - --package-version="235.0.0-0" + --package-name="google-cloud-sdk" --package-version="235.0.0-0" To list all instances with package name matching a regex ^google-cloud available for update through apt, run: $ gcloud alpha compute instances os-inventory list-instances \ - --inventory-filter="\ - PackageUpdates.apt[].Name~^google-cloud*" + --inventory-filter="PackageUpdates.apt[].Name~^google-cloud*" To list all instances with package update google-cloud-sdk of version greater than or equal to 235.0.0-0 available through apt, run: $ gcloud alpha compute instances os-inventory list-instances \ - --inventory-filter="\ - PackageUpdates.apt[].['google-cloud-sdk'].Version>=235.0.0-0" + --inventory-filter="PackageUpdates.apt[].['google-cloud-sdk'].Ve\ + rsion>=235.0.0-0" To list all instances missing the Stackdriver monitoring package stackdriver-agent, run: $ gcloud alpha compute instances os-inventory list-instances \ - --inventory-filter="\ - NOT(InstalledPackages:stackdriver-agent)" + --inventory-filter="NOT(InstalledPackages:stackdriver-agent)" To list all Windows instances with an installed qfe hotfix whose ID equals KB4462930, run: $ gcloud alpha compute instances os-inventory list-instances \ - --inventory-filter="\ - InstalledPackages.qfe[].HotFixID=KB4462930" + --inventory-filter="InstalledPackages.qfe[].HotFixID=KB4462930" To list all Windows instances with a wua update whose description contains the word Security, run: $ gcloud alpha compute instances os-inventory list-instances \ - --inventory-filter="\ - InstalledPackages.wua[].Description:Security" + --inventory-filter="InstalledPackages.wua[].Description:Security\ + " FLAGS --inventory-filter=INVENTORY_FILTER diff --git a/gcloud/alpha/compute/instances/set-iam-policy b/gcloud/alpha/compute/instances/set-iam-policy index 1c64e909f..6c7aa6ff5 100644 --- a/gcloud/alpha/compute/instances/set-iam-policy +++ b/gcloud/alpha/compute/instances/set-iam-policy @@ -11,8 +11,11 @@ DESCRIPTION EXAMPLES The following command reads an IAM policy defined in a JSON file - policy.json and sets it for the instance 'my-instance' and zone 'ZONE': $ gcloud alpha compute instances set-iam-policy my-instance \ + policy.json and sets it for the instance 'my-instance' and zone 'ZONE': + + $ gcloud alpha compute instances set-iam-policy my-instance \ --zone=ZONE policy.json + See https://cloud.google.com/iam/docs/managing-policies for details of policy role and member types. diff --git a/gcloud/alpha/compute/instances/set-scheduling b/gcloud/alpha/compute/instances/set-scheduling index 114296fe3..bb633ec1a 100644 --- a/gcloud/alpha/compute/instances/set-scheduling +++ b/gcloud/alpha/compute/instances/set-scheduling @@ -20,7 +20,7 @@ DESCRIPTION EXAMPLES To set instance to be terminated during maintenance, run: - $ gcloud alpha compute instances set-scheduling example-instance \ + $ gcloud alpha compute instances set-scheduling example-instance \ --maintenance-policy=TERMINATE --zone=us-central1-b POSITIONAL ARGUMENTS diff --git a/gcloud/alpha/compute/instances/update-access-config b/gcloud/alpha/compute/instances/update-access-config index f3fd93a33..4d8e916a1 100644 --- a/gcloud/alpha/compute/instances/update-access-config +++ b/gcloud/alpha/compute/instances/update-access-config @@ -21,7 +21,7 @@ EXAMPLES To update network interface of an instance to 'nic0', run: $ gcloud alpha compute instances update-access-config \ - example-instance --network-interface=nic0 --zone=us-central1-b + example-instance --network-interface=nic0 --zone=us-central1-b POSITIONAL ARGUMENTS INSTANCE_NAME diff --git a/gcloud/alpha/compute/instances/update-container b/gcloud/alpha/compute/instances/update-container index c438ee100..a14d050ca 100644 --- a/gcloud/alpha/compute/instances/update-container +++ b/gcloud/alpha/compute/instances/update-container @@ -40,14 +40,14 @@ EXAMPLES To run the gcr.io/google-containers/busybox image on an instance named 'instance-1' that executes 'echo "Hello world"' as a run command, run: - $ gcloud alpha compute instances update-container instance-1 \ - --container-image=gcr.io/google-containers/busybox \ + $ gcloud alpha compute instances update-container instance-1 \ + --container-image=gcr.io/google-containers/busybox \ --container-command='echo "Hello world"' To run the gcr.io/google-containers/busybox image in privileged mode, run: - $ gcloud alpha compute instances update-container instance-1 \ - --container-image=gcr.io/google-containers/busybox \ + $ gcloud alpha compute instances update-container instance-1 \ + --container-image=gcr.io/google-containers/busybox \ --container-privileged POSITIONAL ARGUMENTS diff --git a/gcloud/alpha/compute/network-edge-security-services/create b/gcloud/alpha/compute/network-edge-security-services/create index 19586ecba..f388a4dde 100644 --- a/gcloud/alpha/compute/network-edge-security-services/create +++ b/gcloud/alpha/compute/network-edge-security-services/create @@ -19,16 +19,13 @@ EXAMPLES region 'us-central1', run: $ gcloud alpha compute network-edge-security-services create \ - my-service \ - --region=us-central1 + my-service --region=us-central1 To create a network edge security service with the name 'my-service' with security policy 'my-policy' attached in region 'us-central1', run: $ gcloud alpha compute network-edge-security-services create \ - my-service \ - --security-policy=my-policy \ - --region=us-central1 + my-service --security-policy=my-policy --region=us-central1 POSITIONAL ARGUMENTS NAME diff --git a/gcloud/alpha/compute/network-edge-security-services/delete b/gcloud/alpha/compute/network-edge-security-services/delete index b33b3ce04..152ed853b 100644 --- a/gcloud/alpha/compute/network-edge-security-services/delete +++ b/gcloud/alpha/compute/network-edge-security-services/delete @@ -15,8 +15,7 @@ EXAMPLES region 'us-central1', run: $ gcloud alpha compute network-edge-security-services delete \ - my-service \ - --region=us-central1 + my-service --region=us-central1 POSITIONAL ARGUMENTS NAME diff --git a/gcloud/alpha/compute/network-edge-security-services/describe b/gcloud/alpha/compute/network-edge-security-services/describe index e5ccafe19..65f637404 100644 --- a/gcloud/alpha/compute/network-edge-security-services/describe +++ b/gcloud/alpha/compute/network-edge-security-services/describe @@ -16,8 +16,7 @@ EXAMPLES region 'us-central1', run: $ gcloud alpha compute network-edge-security-services describe \ - my-service \ - --region=us-central1 + my-service --region=us-central1 POSITIONAL ARGUMENTS NAME diff --git a/gcloud/alpha/compute/network-edge-security-services/update b/gcloud/alpha/compute/network-edge-security-services/update index f5d49c15f..16795dfc2 100644 --- a/gcloud/alpha/compute/network-edge-security-services/update +++ b/gcloud/alpha/compute/network-edge-security-services/update @@ -19,17 +19,13 @@ EXAMPLES service with the name 'my-service' in region 'us-central1', run: $ gcloud alpha compute network-edge-security-services update \ - my-service \ - --security-policy=my-policy \ - --region=us-central1 + my-service --security-policy=my-policy --region=us-central1 To remove the security policy attached to a network edge security service with the name 'my-service' in region 'us-central1', run: $ gcloud alpha compute network-edge-security-services update \ - my-service \ - --security-policy="" \ - --region=us-central1 + my-service --security-policy="" --region=us-central1 POSITIONAL ARGUMENTS NAME diff --git a/gcloud/alpha/compute/network-firewall-policies/associations/create b/gcloud/alpha/compute/network-firewall-policies/associations/create index cd6f9edf8..677fa0e8f 100644 --- a/gcloud/alpha/compute/network-firewall-policies/associations/create +++ b/gcloud/alpha/compute/network-firewall-policies/associations/create @@ -18,21 +18,17 @@ EXAMPLES To associate a global network firewall policy with name my-policy to network my-network with an association named my-association, run: - $ gcloud alpha compute network-firewall-policies associations create - --firewall-policy=my-policy - --network=my-network - --name=my-association - --global-firewall-policy + $ gcloud alpha compute network-firewall-policies associations \ + create --firewall-policy=my-policy --network=my-network \ + --name=my-association --global-firewall-policy To associate a network firewall policy with name my-region-policy in region region-a to network my-network with an association named my-association, run: - $ gcloud alpha compute network-firewall-policies associations create - --firewall-policy=my-policy - --network=my-network - --name=my-association - --firewall-policy-region=region-a + $ gcloud alpha compute network-firewall-policies associations \ + create --firewall-policy=my-policy --network=my-network \ + --name=my-association --firewall-policy-region=region-a REQUIRED FLAGS --firewall-policy=FIREWALL_POLICY diff --git a/gcloud/alpha/compute/network-firewall-policies/associations/delete b/gcloud/alpha/compute/network-firewall-policies/associations/delete index 5dc6c24a9..9c214375e 100644 --- a/gcloud/alpha/compute/network-firewall-policies/associations/delete +++ b/gcloud/alpha/compute/network-firewall-policies/associations/delete @@ -18,17 +18,15 @@ EXAMPLES To delete an association from a global network firewall policy with NAME my-policy and association name my-association, run: - $ gcloud alpha compute network-firewall-policies associations delete - --firewall-policy=my-policy - --name=my-association + $ gcloud alpha compute network-firewall-policies associations \ + delete --firewall-policy=my-policy --name=my-association \ --global-firewall-policy To delete an association from a regional network firewall policy with NAME my-policy in region region-a and association name my-association, run: - $ gcloud alpha compute network-firewall-policies associations delete - --firewall-policy=my-policy - --name=my-association + $ gcloud alpha compute network-firewall-policies associations \ + delete --firewall-policy=my-policy --name=my-association \ --firewall-policy-region=region-a REQUIRED FLAGS diff --git a/gcloud/alpha/compute/network-firewall-policies/clone-rules b/gcloud/alpha/compute/network-firewall-policies/clone-rules index 7c1819c83..c89ba7da8 100644 --- a/gcloud/alpha/compute/network-firewall-policies/clone-rules +++ b/gcloud/alpha/compute/network-firewall-policies/clone-rules @@ -25,8 +25,7 @@ EXAMPLES with NAME source-policy, run: $ gcloud alpha compute network-firewall-policies clone-rules \ - my-region-policy \ - --source-firewall-policy=source-policy \ + my-region-policy --source-firewall-policy=source-policy \ --region=region-a POSITIONAL ARGUMENTS diff --git a/gcloud/alpha/compute/network-firewall-policies/create b/gcloud/alpha/compute/network-firewall-policies/create index 8d06fd03e..0571ebe94 100644 --- a/gcloud/alpha/compute/network-firewall-policies/create +++ b/gcloud/alpha/compute/network-firewall-policies/create @@ -16,15 +16,14 @@ EXAMPLES To create a global network firewall policy named ``my-policy" under project with ID test-project, run: - $ gcloud alpha compute network-firewall-policies create my-policy \ - --project=test-project --global + $ gcloud alpha compute network-firewall-policies create my-policy \ + --project=test-project --global To create a regional network firewall policy named ``my-region-policy" under project with ID test-project, in region my-region, run: $ gcloud alpha compute network-firewall-policies create \ - my-region-policy --project=test-project \ - --region=my-region + my-region-policy --project=test-project --region=my-region POSITIONAL ARGUMENTS FIREWALL_POLICY diff --git a/gcloud/alpha/compute/network-firewall-policies/rules/delete b/gcloud/alpha/compute/network-firewall-policies/rules/delete index 690f2ccde..4c3362dea 100644 --- a/gcloud/alpha/compute/network-firewall-policies/rules/delete +++ b/gcloud/alpha/compute/network-firewall-policies/rules/delete @@ -23,8 +23,7 @@ EXAMPLES with name my-policy, in region region-a, run: $ gcloud alpha compute network-firewall-policies rules delete 10 \ - --firewall-policy=my-policy \ - --firewall-policy-region=region-a + --firewall-policy=my-policy --firewall-policy-region=region-a POSITIONAL ARGUMENTS PRIORITY diff --git a/gcloud/alpha/compute/network-firewall-policies/rules/describe b/gcloud/alpha/compute/network-firewall-policies/rules/describe index 984f47ece..0cbd6c27d 100644 --- a/gcloud/alpha/compute/network-firewall-policies/rules/describe +++ b/gcloud/alpha/compute/network-firewall-policies/rules/describe @@ -17,14 +17,13 @@ EXAMPLES with name my-policy, run: $ gcloud alpha compute network-firewall-policies rules describe 10 \ - --firewall-policy=my-policy --global-firewall-policy + --firewall-policy=my-policy --global-firewall-policy To describe a rule with priority 10 in a regional network firewall policy with name my-policy, in region region-a, run: $ gcloud alpha compute network-firewall-policies rules describe 10 \ - --firewall-policy=my-policy \ - --firewall-policy-region=region-a + --firewall-policy=my-policy --firewall-policy-region=region-a POSITIONAL ARGUMENTS PRIORITY diff --git a/gcloud/alpha/compute/network-firewall-policies/update b/gcloud/alpha/compute/network-firewall-policies/update index d32ca27be..7437c0d1c 100644 --- a/gcloud/alpha/compute/network-firewall-policies/update +++ b/gcloud/alpha/compute/network-firewall-policies/update @@ -16,15 +16,14 @@ EXAMPLES To update a global network firewall policy with name my-policy, to change the description to New description, run: - $ gcloud alpha compute network-firewall-policies update my-policy \ - --description='New description' --global + $ gcloud alpha compute network-firewall-policies update my-policy \ + --description='New description' --global To update a regional network firewall policy with name my-policy, in region my-region, to change the description to New description, run: - $ gcloud alpha compute network-firewall-policies update my-policy \ - --description='New description' \ - --region=my-region + $ gcloud alpha compute network-firewall-policies update my-policy \ + --description='New description' --region=my-region POSITIONAL ARGUMENTS FIREWALL_POLICY diff --git a/gcloud/alpha/compute/networks/get-effective-firewalls b/gcloud/alpha/compute/networks/get-effective-firewalls index ba35a7fad..fbe5c3122 100644 --- a/gcloud/alpha/compute/networks/get-effective-firewalls +++ b/gcloud/alpha/compute/networks/get-effective-firewalls @@ -16,7 +16,8 @@ EXAMPLES To get the effective firewalls of network with name example-network, run: $ gcloud alpha compute networks get-effective-firewalls \ - example-network, + example-network + To show all fields of the firewall rules, please show in JSON format with option --format=json diff --git a/gcloud/alpha/compute/networks/list-ip-addresses b/gcloud/alpha/compute/networks/list-ip-addresses index ebdc3ac6f..344c392f3 100644 --- a/gcloud/alpha/compute/networks/list-ip-addresses +++ b/gcloud/alpha/compute/networks/list-ip-addresses @@ -18,8 +18,8 @@ EXAMPLES List IP addresses only for given types: - $ gcloud alpha compute networks list-ip-addresses my-network \ - --types=SUBNETWORK,PEER_USED,REMOTE_USED + $ gcloud alpha compute networks list-ip-addresses my-network \ + --types=SUBNETWORK,PEER_USED,REMOTE_USED POSITIONAL ARGUMENTS NAME diff --git a/gcloud/alpha/compute/networks/list-ip-owners b/gcloud/alpha/compute/networks/list-ip-owners index 1b96e13ed..60bfd3896 100644 --- a/gcloud/alpha/compute/networks/list-ip-owners +++ b/gcloud/alpha/compute/networks/list-ip-owners @@ -20,23 +20,23 @@ EXAMPLES List IP owners only for given owner types: - $ gcloud alpha compute networks list-ip-owners my-network \ - --owner-types=instance,address,forwardingRule + $ gcloud alpha compute networks list-ip-owners my-network \ + --owner-types=instance,address,forwardingRule List IP owners only for given owner projects: - $ gcloud alpha compute networks list-ip-owners my-network \ - --owner-projects=p1,p2 + $ gcloud alpha compute networks list-ip-owners my-network \ + --owner-projects=p1,p2 List IP owners only for given subnet: - $ gcloud alpha compute networks list-ip-owners my-network \ - --subnet-name=subnet-1 --subnet-region=us-central1 + $ gcloud alpha compute networks list-ip-owners my-network \ + --subnet-name=subnet-1 --subnet-region=us-central1 List IP owners whose IP ranges overlap with the given IP CIDR range: - $ gcloud alpha compute networks list-ip-owners my-network \ - --ip-cidr-range=10.128.10.130/30 + $ gcloud alpha compute networks list-ip-owners my-network \ + --ip-cidr-range=10.128.10.130/30 POSITIONAL ARGUMENTS NAME diff --git a/gcloud/alpha/compute/networks/peerings/create b/gcloud/alpha/compute/networks/peerings/create index a6c08b866..e63606ef2 100644 --- a/gcloud/alpha/compute/networks/peerings/create +++ b/gcloud/alpha/compute/networks/peerings/create @@ -21,12 +21,10 @@ EXAMPLES imports custom routes and subnet routes with public IPs, run: $ gcloud alpha compute networks peerings create peering-name \ - --network=local-network \ - --peer-network=peer-network \ - --export-custom-routes \ - --import-custom-routes \ - --export-subnet-routes-with-public-ip \ - --import-subnet-routes-with-public-ip + --network=local-network --peer-network=peer-network \ + --export-custom-routes --import-custom-routes \ + --export-subnet-routes-with-public-ip \ + --import-subnet-routes-with-public-ip POSITIONAL ARGUMENTS NAME diff --git a/gcloud/alpha/compute/networks/peerings/delete b/gcloud/alpha/compute/networks/peerings/delete index 88f2a0ae6..3f9fae380 100644 --- a/gcloud/alpha/compute/networks/peerings/delete +++ b/gcloud/alpha/compute/networks/peerings/delete @@ -15,7 +15,7 @@ EXAMPLES 'local-network', run: $ gcloud alpha compute networks peerings delete peering-name \ - --network=local-network + --network=local-network POSITIONAL ARGUMENTS NAME diff --git a/gcloud/alpha/compute/networks/peerings/list-routes b/gcloud/alpha/compute/networks/peerings/list-routes index 6850c9156..ae0da4f18 100644 --- a/gcloud/alpha/compute/networks/peerings/list-routes +++ b/gcloud/alpha/compute/networks/peerings/list-routes @@ -16,9 +16,8 @@ DESCRIPTION EXAMPLES List received routes for VPC network peering in us-central1: - $ gcloud alpha compute networks peerings list-routes peering-name \ - --network=network-name --region=us-central1 \ - --direction=INCOMING + $ gcloud alpha compute networks peerings list-routes peering-name \ + --network=network-name --region=us-central1 --direction=INCOMING POSITIONAL ARGUMENTS NAME diff --git a/gcloud/alpha/compute/networks/peerings/update b/gcloud/alpha/compute/networks/peerings/update index fe7271974..d83740785 100644 --- a/gcloud/alpha/compute/networks/peerings/update +++ b/gcloud/alpha/compute/networks/peerings/update @@ -13,15 +13,14 @@ EXAMPLES routes, run: $ gcloud alpha compute networks peerings update peering-name \ - --export-custom-routes \ - --import-custom-routes + --export-custom-routes --import-custom-routes To update the peering named peering-name to both export and import subnet routes with public ip, run: $ gcloud alpha compute networks peerings update peering-name \ - --export-subnet-routes-with-public-ip \ - --import-subnet-routes-with-public-ip + --export-subnet-routes-with-public-ip \ + --import-subnet-routes-with-public-ip POSITIONAL ARGUMENTS NAME diff --git a/gcloud/alpha/compute/org-security-policies/rules/create b/gcloud/alpha/compute/org-security-policies/rules/create index 051a0877a..b74dcbee1 100644 --- a/gcloud/alpha/compute/org-security-policies/rules/create +++ b/gcloud/alpha/compute/org-security-policies/rules/create @@ -22,8 +22,8 @@ EXAMPLES with ID ``123456789", run: $ gcloud alpha compute org-security-policies rules create create \ - 10 --security-policy=123456789 --action=allow - --description=example-rule + 10 --security-policy=123456789 --action=allow \ + --description=example-rule POSITIONAL ARGUMENTS PRIORITY diff --git a/gcloud/alpha/compute/org-security-policies/rules/update b/gcloud/alpha/compute/org-security-policies/rules/update index acc06acb3..58a49b03e 100644 --- a/gcloud/alpha/compute/org-security-policies/rules/update +++ b/gcloud/alpha/compute/org-security-policies/rules/update @@ -24,8 +24,8 @@ EXAMPLES ``new-example-rule", run: $ gcloud alpha compute org-security-policies rules update create \ - 10 --security-policy=123456789 --action=allow - --description=new-example-rule + 10 --security-policy=123456789 --action=allow \ + --description=new-example-rule POSITIONAL ARGUMENTS PRIORITY diff --git a/gcloud/alpha/compute/os-config/guest-policies/create b/gcloud/alpha/compute/os-config/guest-policies/create index 1b004f145..ca069cf4f 100644 --- a/gcloud/alpha/compute/os-config/guest-policies/create +++ b/gcloud/alpha/compute/os-config/guest-policies/create @@ -16,8 +16,7 @@ EXAMPLES To create a guest policy policy1 in the organization 12345, run: $ gcloud alpha compute os-config guest-policies create policy1 \ - --file=path_to_config_file \ - --organization=12345 + --file=path_to_config_file --organization=12345 POSITIONAL ARGUMENTS POLICY_ID diff --git a/gcloud/alpha/compute/os-config/os-policy-assignment-reports/describe b/gcloud/alpha/compute/os-config/os-policy-assignment-reports/describe index f64318a1c..bafc651de 100644 --- a/gcloud/alpha/compute/os-config/os-policy-assignment-reports/describe +++ b/gcloud/alpha/compute/os-config/os-policy-assignment-reports/describe @@ -27,7 +27,7 @@ EXAMPLES my-instance/osPolicyAssignments/my-assignment/report $ gcloud alpha compute os-config os-policy-assignment-reports \ - describe \ + describe \ https://osconfig.googleapis.com/v1alpha/projects/my-project/\ locations/us-central1-a/instances/instance-name/\ osPolicyAssignments/assignment-id/report diff --git a/gcloud/alpha/compute/packet-mirrorings/create b/gcloud/alpha/compute/packet-mirrorings/create index f5c2806ce..ee420ef23 100644 --- a/gcloud/alpha/compute/packet-mirrorings/create +++ b/gcloud/alpha/compute/packet-mirrorings/create @@ -19,19 +19,18 @@ EXAMPLES us-central1, and send the mirrored traffic to the collector-fr Forwarding Rule. - $ gcloud alpha compute packet-mirrorings create my-pm - --network my-network --region us-central1 - --mirrored-subnets my-subnet --collector-ilb collector-fr - --filter-protocols tcp + $ gcloud alpha compute packet-mirrorings create my-pm \ + --network my-network --region us-central1 \ + --mirrored-subnets my-subnet --collector-ilb collector-fr \ + --filter-protocols tcp Mirror all traffic between instances with tag t1 and external server with IP 11.22.33.44 in us-central1, and send the mirrored traffic to the collector-fr Forwarding Rule. - $ gcloud alpha compute packet-mirrorings create my-pm - --network my-network --region us-central1 - --mirrored-tags t1 --collector-ilb collector-fr - --filter-cidr-ranges 11.22.33.44/32 + $ gcloud alpha compute packet-mirrorings create my-pm \ + --network my-network --region us-central1 --mirrored-tags t1 \ + --collector-ilb collector-fr --filter-cidr-ranges 11.22.33.44/32 POSITIONAL ARGUMENTS NAME diff --git a/gcloud/alpha/compute/packet-mirrorings/delete b/gcloud/alpha/compute/packet-mirrorings/delete index cd8d76382..db97ffdd4 100644 --- a/gcloud/alpha/compute/packet-mirrorings/delete +++ b/gcloud/alpha/compute/packet-mirrorings/delete @@ -12,8 +12,8 @@ DESCRIPTION EXAMPLES Delete the Packet Mirroring policy pm-1 in region us-central1. - $ gcloud alpha compute packet-mirrorings delete pm-1 - --region us-central1 + $ gcloud alpha compute packet-mirrorings delete pm-1 \ + --region us-central1 POSITIONAL ARGUMENTS NAME [NAME ...] diff --git a/gcloud/alpha/compute/packet-mirrorings/describe b/gcloud/alpha/compute/packet-mirrorings/describe index bac0da158..d637cf216 100644 --- a/gcloud/alpha/compute/packet-mirrorings/describe +++ b/gcloud/alpha/compute/packet-mirrorings/describe @@ -12,8 +12,8 @@ DESCRIPTION EXAMPLES Describe the Packet Mirroring policy pm-1 in region us-central1. - $ gcloud alpha compute packet-mirrorings describe pm-1 - --region us-central1 + $ gcloud alpha compute packet-mirrorings describe pm-1 \ + --region us-central1 POSITIONAL ARGUMENTS NAME diff --git a/gcloud/alpha/compute/packet-mirrorings/update b/gcloud/alpha/compute/packet-mirrorings/update index d0d64d80d..02e71bd0b 100644 --- a/gcloud/alpha/compute/packet-mirrorings/update +++ b/gcloud/alpha/compute/packet-mirrorings/update @@ -28,23 +28,23 @@ DESCRIPTION EXAMPLES Stop mirroring by tags, add subnet-1 as a mirrored subnet. - $ gcloud alpha compute packet-mirrorings update my-pm - --region us-central1 --clear-mirrored-tags + $ gcloud alpha compute packet-mirrorings update my-pm \ + --region us-central1 --clear-mirrored-tags \ --add-mirrored-subnets subnet-1 Change the load-balancer to send mirrored traffic to. - $ gcloud alpha compute packet-mirrorings update my-pm + $ gcloud alpha compute packet-mirrorings update my-pm \ --region us-central1 --collector-ilb new-forwarding-rule Disable a Packet Mirroring policy. - $ gcloud alpha compute packet-mirrorings update my-pm + $ gcloud alpha compute packet-mirrorings update my-pm \ --region us-central1 --no-enable Re-enable a disabled Packet Mirroring policy. - $ gcloud alpha compute packet-mirrorings update my-pm + $ gcloud alpha compute packet-mirrorings update my-pm \ --region us-central1 --enable POSITIONAL ARGUMENTS diff --git a/gcloud/alpha/compute/public-advertised-prefixes/create b/gcloud/alpha/compute/public-advertised-prefixes/create index dec130071..8bccd06cb 100644 --- a/gcloud/alpha/compute/public-advertised-prefixes/create +++ b/gcloud/alpha/compute/public-advertised-prefixes/create @@ -12,7 +12,7 @@ EXAMPLES $ gcloud alpha compute public-advertised-prefixes create \ my-public-advertised-prefix --range=120.120.10.0/24 \ - --dns-verification-ip=120.120.10.15 + --dns-verification-ip=120.120.10.15 POSITIONAL ARGUMENTS NAME diff --git a/gcloud/alpha/compute/public-delegated-prefixes/create b/gcloud/alpha/compute/public-delegated-prefixes/create index 8528db339..81e809757 100644 --- a/gcloud/alpha/compute/public-delegated-prefixes/create +++ b/gcloud/alpha/compute/public-delegated-prefixes/create @@ -13,7 +13,7 @@ EXAMPLES $ gcloud alpha compute public-delegated-prefixes create \ my-public-delegated-prefix --public-advertised-prefix=my-pap \ - --range=120.120.10.128/27 --global + --range=120.120.10.128/27 --global POSITIONAL ARGUMENTS NAME diff --git a/gcloud/alpha/compute/routers/nats/create b/gcloud/alpha/compute/routers/nats/create index 28af7c1d2..a8d7d279b 100644 --- a/gcloud/alpha/compute/routers/nats/create +++ b/gcloud/alpha/compute/routers/nats/create @@ -27,14 +27,14 @@ DESCRIPTION EXAMPLES Auto-allocate NAT for all IP addresses of all subnets in the region: - $ gcloud alpha compute routers nats create nat1 --router=my-router - --auto-allocate-nat-external-ips --nat-all-subnet-ip-ranges + $ gcloud alpha compute routers nats create nat1 --router=my-router \ + --auto-allocate-nat-external-ips --nat-all-subnet-ip-ranges Specify IP addresses for NAT: Each IP address is the name of a reserved static IP address resource in the same region. - $ gcloud alpha compute routers nats create nat1 --router=my-router - --nat-external-ip-pool=ip-address1,ip-address2 + $ gcloud alpha compute routers nats create nat1 --router=my-router \ + --nat-external-ip-pool=ip-address1,ip-address2 Specify subnet ranges for NAT: @@ -42,9 +42,10 @@ EXAMPLES subnets in the region for the given VPC network. You can restrict which subnet primary and secondary ranges can use NAT. - $ gcloud alpha compute routers nats create nat1 --router=my-router - --auto-allocate-nat-external-ips - --nat-custom-subnet-ip-ranges=subnet-1,subnet-3:secondary-range-1 + $ gcloud alpha compute routers nats create nat1 --router=my-router \ + --auto-allocate-nat-external-ips \ + --nat-custom-subnet-ip-ranges=subnet-1,\ + subnet-3:secondary-range-1 POSITIONAL ARGUMENTS NAME diff --git a/gcloud/alpha/compute/routers/nats/rules/create b/gcloud/alpha/compute/routers/nats/rules/create index e309dcf32..0e05b0706 100644 --- a/gcloud/alpha/compute/routers/nats/rules/create +++ b/gcloud/alpha/compute/routers/nats/rules/create @@ -18,9 +18,9 @@ EXAMPLES the CIDR Range "203.0.113.0/24". $ gcloud alpha compute routers nats rules create 1 --nat=my-nat \ - --router=my-router --region=us-central1 - --match='inIpRange(destination.ip, "203.0.113.0/24")' - --source-nat-active-ips=a1 + --router=my-router --region=us-central1 \ + --match='inIpRange(destination.ip, "203.0.113.0/24")' \ + --source-nat-active-ips=a1 POSITIONAL ARGUMENTS RULE_NUMBER diff --git a/gcloud/alpha/compute/routers/nats/rules/update b/gcloud/alpha/compute/routers/nats/rules/update index 3f5a4c397..798a8d9cb 100644 --- a/gcloud/alpha/compute/routers/nats/rules/update +++ b/gcloud/alpha/compute/routers/nats/rules/update @@ -22,9 +22,9 @@ EXAMPLES new connections matching Rule 1 in NAT nat-1, run: $ gcloud alpha compute routers nats rules update 1 --nat=nat1 \ - --router=my-router --region=us-central1 - --source-nat-drain-ips=address-1 - --source-nat-active-ips=address-2 + --router=my-router --region=us-central1 \ + --source-nat-drain-ips=address-1 \ + --source-nat-active-ips=address-2 POSITIONAL ARGUMENTS RULE_NUMBER diff --git a/gcloud/alpha/compute/routers/nats/update b/gcloud/alpha/compute/routers/nats/update index 536f69a1d..cef9734c5 100644 --- a/gcloud/alpha/compute/routers/nats/update +++ b/gcloud/alpha/compute/routers/nats/update @@ -32,9 +32,10 @@ DESCRIPTION EXAMPLES Change subnetworks and IP address resources associated with NAT: - $ gcloud alpha compute routers nats update nat1 --router=my-router - --nat-external-ip-pool=ip-address2,ip-address3 - --nat-custom-subnet-ip-ranges=subnet-2,subnet-3:secondary-range-2 + $ gcloud alpha compute routers nats update nat1 --router=my-router \ + --nat-external-ip-pool=ip-address2,ip-address3 \ + --nat-custom-subnet-ip-ranges=subnet-2,\ + subnet-3:secondary-range-2 Change minimum default ports allocated per VM associated with NAT: @@ -43,18 +44,18 @@ EXAMPLES Change connection timeouts associated with NAT: - $ gcloud alpha compute routers nats update nat1 --router=my-router - --udp-mapping-idle-timeout=60s - --icmp-mapping-idle-timeout=60s - --tcp-established-connection-idle-timeout=60s - --tcp-transitory-connection-idle-timeout=60s + $ gcloud alpha compute routers nats update nat1 --router=my-router \ + --udp-mapping-idle-timeout=60s --icmp-mapping-idle-timeout=60s \ + --tcp-established-connection-idle-timeout=60s \ + --tcp-transitory-connection-idle-timeout=60s Reset connection timeouts associated NAT to default values: - $ gcloud alpha compute routers nats update nat1 --router=my-router - --clear-udp-mapping-idle-timeout --clear-icmp-mapping-idle-timeout - --clear-tcp-established-connection-idle-timeout - --clear-tcp-transitory-connection-idle-timeout + $ gcloud alpha compute routers nats update nat1 --router=my-router \ + --clear-udp-mapping-idle-timeout \ + --clear-icmp-mapping-idle-timeout \ + --clear-tcp-established-connection-idle-timeout \ + --clear-tcp-transitory-connection-idle-timeout POSITIONAL ARGUMENTS NAME diff --git a/gcloud/alpha/compute/routes/create b/gcloud/alpha/compute/routes/create index 044d354e7..a0b9a04cc 100644 --- a/gcloud/alpha/compute/routes/create +++ b/gcloud/alpha/compute/routes/create @@ -42,8 +42,8 @@ EXAMPLES '0.0.0.0/0' and with next hop gateway 'default-internet-gateway', run: $ gcloud alpha compute routes create route-name \ - --destination-range=0.0.0.0/0 \ - --next-hop-gateway=default-internet-gateway + --destination-range=0.0.0.0/0 \ + --next-hop-gateway=default-internet-gateway POSITIONAL ARGUMENTS NAME diff --git a/gcloud/alpha/compute/shared-vpc/organizations/list-host-projects b/gcloud/alpha/compute/shared-vpc/organizations/list-host-projects index d488011ae..227849d53 100644 --- a/gcloud/alpha/compute/shared-vpc/organizations/list-host-projects +++ b/gcloud/alpha/compute/shared-vpc/organizations/list-host-projects @@ -17,6 +17,7 @@ EXAMPLES $ gcloud alpha compute shared-vpc organizations list-host-projects \ 12345 + NAME CREATION_TIMESTAMP XPN_PROJECT_STATUS xpn-host1 2000-01-01T12:00:00.00-00:00 HOST xpn-host2 2000-01-02T12:00:00.00-00:00 HOST diff --git a/gcloud/alpha/compute/tpus/create b/gcloud/alpha/compute/tpus/create index 91338ee74..25403dd21 100644 --- a/gcloud/alpha/compute/tpus/create +++ b/gcloud/alpha/compute/tpus/create @@ -22,12 +22,9 @@ EXAMPLES The following command creates a TPU with ID my-tpu with explicit values for all required and optional parameters: - $ gcloud alpha compute tpus create my-tpu \ - --zone=us-central1-a \ - --range='10.240.0.0/29' \ - --accelerator-type='v2-8' \ - --network=my-tf-network \ - --description='My TF Node' \ + $ gcloud alpha compute tpus create my-tpu --zone=us-central1-a \ + --range='10.240.0.0/29' --accelerator-type='v2-8' \ + --network=my-tf-network --description='My TF Node' \ --version='1.1' POSITIONAL ARGUMENTS diff --git a/gcloud/alpha/compute/tpus/execution-groups/create b/gcloud/alpha/compute/tpus/execution-groups/create index 288050f68..f34bb0030 100644 --- a/gcloud/alpha/compute/tpus/execution-groups/create +++ b/gcloud/alpha/compute/tpus/execution-groups/create @@ -17,28 +17,31 @@ EXAMPLES To create both TPU and VM, run: $ gcloud alpha compute tpus execution-groups create \ - --name=test-execution-group --zone=test-zone - --project=test-project --accelerator-type=v2-8 --tf-version=2.4.1 + --name=test-execution-group --zone=test-zone \ + --project=test-project --accelerator-type=v2-8 \ + --tf-version=2.4.1 To create both TPU and VM with additional flags, run: $ gcloud alpha compute tpus execution-groups create \ --name=test-execution-group --zone=test-zone \ - --project=test-project --accelerator-type=v2-8 --tf-version=2.4.1 \ - --network=default --preemptible-vm --disk-size=100 \ - --machine-type=n1-standard-2 --use-dl-images + --project=test-project --accelerator-type=v2-8 \ + --tf-version=2.4.1 --network=default --preemptible-vm \ + --disk-size=100 --machine-type=n1-standard-2 --use-dl-images To create a VM only before creating the TPU, run: $ gcloud alpha compute tpus execution-groups create \ --name=test-execution-group-tpu-only --zone=test-zone \ - --project=test-project --accelerator-type=v2-8 --tf-version=2.4.1 --tpu-only + --project=test-project --accelerator-type=v2-8 \ + --tf-version=2.4.1 --tpu-only To create the TPU only after the VM has been created, run: $ gcloud alpha compute tpus execution-groups create \ --name=test-execution-group-tpu-only --zone=test-zone \ - --project=test-project --accelerator-type=v2-8 --tf-version=2.4.1 --vm-only + --project=test-project --accelerator-type=v2-8 \ + --tf-version=2.4.1 --vm-only FLAGS --accelerator-type=ACCELERATOR_TYPE; default="v2-8" diff --git a/gcloud/alpha/compute/tpus/execution-groups/delete b/gcloud/alpha/compute/tpus/execution-groups/delete index c117c5e96..878ba00c5 100644 --- a/gcloud/alpha/compute/tpus/execution-groups/delete +++ b/gcloud/alpha/compute/tpus/execution-groups/delete @@ -16,7 +16,7 @@ EXAMPLES $ gcloud alpha compute tpus execution-groups delete \ test-execution-group --zone=test-zone --project=test-project \ - --tpu-only + --tpu-only POSITIONAL ARGUMENTS EXECUTION_GROUP_NAME diff --git a/gcloud/alpha/compute/tpus/execution-groups/resume b/gcloud/alpha/compute/tpus/execution-groups/resume index c21b48db4..2951a555d 100644 --- a/gcloud/alpha/compute/tpus/execution-groups/resume +++ b/gcloud/alpha/compute/tpus/execution-groups/resume @@ -14,7 +14,7 @@ EXAMPLES $ gcloud alpha compute tpus execution-groups resume \ test-execution-group --zone=test-zone --project=test-project \ - --accelerator-type=v2-8 --tf-version=2.4.1 + --accelerator-type=v2-8 --tf-version=2.4.1 POSITIONAL ARGUMENTS EXECUTION_GROUP_NAME diff --git a/gcloud/alpha/compute/vpn-gateways/update b/gcloud/alpha/compute/vpn-gateways/update index 99d07b474..e85e8a03e 100644 --- a/gcloud/alpha/compute/vpn-gateways/update +++ b/gcloud/alpha/compute/vpn-gateways/update @@ -32,8 +32,7 @@ EXAMPLES To update labels for a VPN gateway, run: $ gcloud alpha compute vpn-gateways update my-gateway \ - --region=us-central1 \ - --update-labels=k0=value1,k1=value2 + --region=us-central1 --update-labels=k0=value1,k1=value2 POSITIONAL ARGUMENTS NAME diff --git a/gcloud/alpha/container/backup-restore/backups/create b/gcloud/alpha/container/backup-restore/backups/create index 082dd7417..1df39e2b1 100644 --- a/gcloud/alpha/container/backup-restore/backups/create +++ b/gcloud/alpha/container/backup-restore/backups/create @@ -16,23 +16,23 @@ EXAMPLES under backup plan my-backup-plan, run: $ gcloud alpha container backup-restore backups create my-backup \ - --project=my-project --location=us-central1 - --backup-plan=my-backup-plan + --project=my-project --location=us-central1 \ + --backup-plan=my-backup-plan To create a backup my-backup in project my-project in location us-central1 under backup plan my-backup-plan and not wait for the resulting operation to finish, run: $ gcloud alpha container backup-restore backups create my-backup \ - --project=my-project --location=us-central1 - --backup-plan=my-backup-plan --async + --project=my-project --location=us-central1 \ + --backup-plan=my-backup-plan --async To create a backup my-backup in project my-project in location us-central1 under backup plan my-backup-plan and wait for the Backup to complete, run: $ gcloud alpha container backup-restore backups create my-backup \ - --project=my-project --location=us-central1 - --backup-plan=my-backup-plan --wait-for-completion + --project=my-project --location=us-central1 \ + --backup-plan=my-backup-plan --wait-for-completion POSITIONAL ARGUMENTS Backup resource - Name of the backup to create. Once the backup is diff --git a/gcloud/alpha/container/backup-restore/restores/create b/gcloud/alpha/container/backup-restore/restores/create index 34810c44c..81fce1c50 100644 --- a/gcloud/alpha/container/backup-restore/restores/create +++ b/gcloud/alpha/container/backup-restore/restores/create @@ -15,8 +15,8 @@ EXAMPLES my-restore-plan, run: $ gcloud alpha container backup-restore restores create my-restore \ - --project=my-project --location=us-central1 - --restore-plan=my-restore-plan + --project=my-project --location=us-central1 \ + --restore-plan=my-restore-plan POSITIONAL ARGUMENTS Restore resource - Name of the restore to create. Once the restore is diff --git a/gcloud/alpha/container/binauthz/attestations/create b/gcloud/alpha/container/binauthz/attestations/create index b1d04c30e..07f2a4098 100644 --- a/gcloud/alpha/container/binauthz/attestations/create +++ b/gcloud/alpha/container/binauthz/attestations/create @@ -20,9 +20,9 @@ EXAMPLES resource path "projects/foo/attestors/bar", run: $ gcloud alpha container binauthz attestations create \ - --project=my_proj \ - --artifact-url='gcr.io/example-project/example-image@sha256:abcd' \ - --attestor=projects/foo/attestors/bar \ + --project=my_proj \ + --artifact-url='gcr.io/example-project/example-image@sha256:abcd\ + ' --attestor=projects/foo/attestors/bar \ --signature-file=signed_artifact_attestation.pgp.sig \ --public-key-id=AAAA0000000000000000FFFFFFFFFFFFFFFFFFFF diff --git a/gcloud/alpha/container/binauthz/attestations/list b/gcloud/alpha/container/binauthz/attestations/list index 221e625bc..0dff82a0c 100644 --- a/gcloud/alpha/container/binauthz/attestations/list +++ b/gcloud/alpha/container/binauthz/attestations/list @@ -20,14 +20,14 @@ EXAMPLES attestor: $ gcloud alpha container binauthz attestations list \ - --attestor=projects/foo/attestor/bar + --attestor=projects/foo/attestor/bar List the Occurrence messages for all attestations for the passed artifact-url bound to the passed attestor: $ gcloud alpha container binauthz attestations list \ - --attestor=projects/foo/attestors/bar \ - --artifact-url='gcr.io/foo/example-image@sha256:abcd' + --attestor=projects/foo/attestors/bar \ + --artifact-url='gcr.io/foo/example-image@sha256:abcd' REQUIRED FLAGS Attestor resource - The Attestor whose Container Analysis Note will be diff --git a/gcloud/alpha/container/binauthz/attestations/sign-and-create b/gcloud/alpha/container/binauthz/attestations/sign-and-create index 79123557d..09cbea5d8 100644 --- a/gcloud/alpha/container/binauthz/attestations/sign-and-create +++ b/gcloud/alpha/container/binauthz/attestations/sign-and-create @@ -26,14 +26,11 @@ EXAMPLES run: $ gcloud alpha container binauthz attestations sign-and-create \ - --project=my_proj \ - --artifact-url='gcr.io/example-project/example-image@sha256:abcd' \ - --attestor=projects/foo/attestors/bar \ - --keyversion-project=foo \ - --keyversion-location=us-west1 \ - --keyversion-keyring=aring \ - --keyversion-key=akey \ - --keyversion=1 + --project=my_proj \ + --artifact-url='gcr.io/example-project/example-image@sha256:abcd\ + ' --attestor=projects/foo/attestors/bar --keyversion-project=foo \ + --keyversion-location=us-west1 --keyversion-keyring=aring \ + --keyversion-key=akey --keyversion=1 REQUIRED FLAGS --artifact-url=ARTIFACT_URL diff --git a/gcloud/alpha/container/binauthz/attestors/create b/gcloud/alpha/container/binauthz/attestors/create index ff8651767..461c1b997 100644 --- a/gcloud/alpha/container/binauthz/attestors/create +++ b/gcloud/alpha/container/binauthz/attestors/create @@ -10,8 +10,7 @@ SYNOPSIS EXAMPLES To create an Attestor with an existing Note projects/my_proj/notes/my_note: - $ gcloud alpha container binauthz attestors create \ - my_new_attestor + $ gcloud alpha container binauthz attestors create my_new_attestor \ --attestation-authority-note=my_note \ --attestation-authority-note-project=my_proj \ diff --git a/gcloud/alpha/container/binauthz/attestors/public-keys/add b/gcloud/alpha/container/binauthz/attestors/public-keys/add index 32c5cd7b7..c34cc4ac3 100644 --- a/gcloud/alpha/container/binauthz/attestors/public-keys/add +++ b/gcloud/alpha/container/binauthz/attestors/public-keys/add @@ -19,18 +19,14 @@ EXAMPLES To add a new KMS public key to an existing Attestor my_attestor: $ gcloud alpha container binauthz attestors public-keys add \ - --attestor=my_attestor \ - --keyversion-project=foo \ - --keyversion-location=us-west1 \ - --keyversion-keyring=aring \ - --keyversion-key=akey \ - --keyversion=1 + --attestor=my_attestor --keyversion-project=foo \ + --keyversion-location=us-west1 --keyversion-keyring=aring \ + --keyversion-key=akey --keyversion=1 To add a new PGP public key to an existing Attestor my_attestor: $ gcloud alpha container binauthz attestors public-keys add \ - --attestor=my_attestor \ - --pgp-public-key-file=my_key.pub + --attestor=my_attestor --pgp-public-key-file=my_key.pub REQUIRED FLAGS Attestor resource - The attestor to which the public key should be added. diff --git a/gcloud/alpha/container/binauthz/attestors/public-keys/remove b/gcloud/alpha/container/binauthz/attestors/public-keys/remove index 6267b7c28..946b88f51 100644 --- a/gcloud/alpha/container/binauthz/attestors/public-keys/remove +++ b/gcloud/alpha/container/binauthz/attestors/public-keys/remove @@ -10,8 +10,7 @@ EXAMPLES To remove a public key from the Attestor my_attestor: $ gcloud alpha container binauthz attestors public-keys remove \ - 0638AADD940361EA2D7F14C58C124F0E663DA097 \ - --attestor=my_attestor + 0638AADD940361EA2D7F14C58C124F0E663DA097 --attestor=my_attestor POSITIONAL ARGUMENTS PUBLIC_KEY_ID diff --git a/gcloud/alpha/container/binauthz/continuous-validation/describe b/gcloud/alpha/container/binauthz/continuous-validation/describe index 553c005e9..c92efd5d3 100644 --- a/gcloud/alpha/container/binauthz/continuous-validation/describe +++ b/gcloud/alpha/container/binauthz/continuous-validation/describe @@ -12,10 +12,10 @@ DESCRIPTION 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 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, diff --git a/gcloud/alpha/container/binauthz/create-signature-payload b/gcloud/alpha/container/binauthz/create-signature-payload index 0e844df1c..c42f165df 100644 --- a/gcloud/alpha/container/binauthz/create-signature-payload +++ b/gcloud/alpha/container/binauthz/create-signature-payload @@ -15,7 +15,8 @@ EXAMPLES To output serialized JSON to sign, run: $ gcloud alpha container binauthz create-signature-payload \ - --artifact-url="gcr.io/example-project/example-image@sha256:abcd" + --artifact-url="gcr.io/example-project/example-image@sha256:abcd\ + " REQUIRED FLAGS --artifact-url=ARTIFACT_URL diff --git a/gcloud/alpha/container/clusters/create b/gcloud/alpha/container/clusters/create index fd099a10a..d54f57d74 100644 --- a/gcloud/alpha/container/clusters/create +++ b/gcloud/alpha/container/clusters/create @@ -700,7 +700,7 @@ FLAGS --monitoring=[COMPONENT,...] Set the components that have monitoring enabled. Valid component values - are: SYSTEM, NONE + are: SYSTEM, WORKLOAD (Deprecated), NONE For more information, look at https://cloud.google.com/stackdriver/docs/solutions/gke/installing#available-metrics diff --git a/gcloud/alpha/container/clusters/update b/gcloud/alpha/container/clusters/update index 4fed62a9f..5ec24b366 100644 --- a/gcloud/alpha/container/clusters/update +++ b/gcloud/alpha/container/clusters/update @@ -964,7 +964,7 @@ REQUIRED FLAGS --monitoring=[COMPONENT,...] Set the components that have monitoring enabled. Valid component - values are: SYSTEM, NONE + values are: SYSTEM, WORKLOAD (Deprecated), NONE For more information, look at https://cloud.google.com/stackdriver/docs/solutions/gke/installing#available-metrics diff --git a/gcloud/alpha/container/hub/cloudrun/apply b/gcloud/alpha/container/hub/cloudrun/apply index 7c7517283..778049b3c 100644 --- a/gcloud/alpha/container/hub/cloudrun/apply +++ b/gcloud/alpha/container/hub/cloudrun/apply @@ -16,7 +16,7 @@ EXAMPLES To apply the CloudRun YAML file, run: $ gcloud alpha container hub cloudrun apply \ - --kubeconfig=/path/to/kubeconfig \ + --kubeconfig=/path/to/kubeconfig \ --config=/path/to/cloud-run-cr.yaml REQUIRED FLAGS diff --git a/gcloud/alpha/container/hub/config-management/disable b/gcloud/alpha/container/hub/config-management/disable index 1ba47d974..c68cb91ef 100644 --- a/gcloud/alpha/container/hub/config-management/disable +++ b/gcloud/alpha/container/hub/config-management/disable @@ -7,7 +7,7 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Disable the Config Management Feature in Hub. + (ALPHA) Disable the Config Management Feature in a fleet. EXAMPLES To disable the Config Management Feature, run: diff --git a/gcloud/alpha/container/hub/config-management/enable b/gcloud/alpha/container/hub/config-management/enable index 04837b6a7..18a86903e 100644 --- a/gcloud/alpha/container/hub/config-management/enable +++ b/gcloud/alpha/container/hub/config-management/enable @@ -6,7 +6,7 @@ SYNOPSIS gcloud alpha container hub config-management enable [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Enables the Config Management Feature in Hub. + (ALPHA) Enables the Config Management Feature in a fleet. EXAMPLES To enable the Config Management Feature, run: diff --git a/gcloud/alpha/container/hub/identity-service/describe b/gcloud/alpha/container/hub/identity-service/describe index 2f24f9920..1f4c28a84 100644 --- a/gcloud/alpha/container/hub/identity-service/describe +++ b/gcloud/alpha/container/hub/identity-service/describe @@ -8,7 +8,8 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Prints the status of the Identity Service Feature resource in Hub. + (ALPHA) Prints the status of the Identity Service Feature resource in a + fleet. EXAMPLES To describe the status of the Identity Service configuration, run: diff --git a/gcloud/alpha/container/hub/identity-service/disable b/gcloud/alpha/container/hub/identity-service/disable index c2000485d..1a2233c97 100644 --- a/gcloud/alpha/container/hub/identity-service/disable +++ b/gcloud/alpha/container/hub/identity-service/disable @@ -7,7 +7,7 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) This command disables the Identity Service Feature in Hub. + (ALPHA) This command disables the Identity Service Feature in a fleet. EXAMPLES To disable the Identity Service Feature, run: diff --git a/gcloud/alpha/container/hub/identity-service/enable b/gcloud/alpha/container/hub/identity-service/enable index f993f3c52..53085008a 100644 --- a/gcloud/alpha/container/hub/identity-service/enable +++ b/gcloud/alpha/container/hub/identity-service/enable @@ -6,7 +6,7 @@ SYNOPSIS gcloud alpha container hub identity-service enable [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) This command enables the Identity Service Feature in Hub. + (ALPHA) This command enables the Identity Service Feature in a fleet. EXAMPLES To enable the Identity Service Feature, run: diff --git a/gcloud/alpha/container/hub/ingress/describe b/gcloud/alpha/container/hub/ingress/describe index 52a183354..4db7522f8 100644 --- a/gcloud/alpha/container/hub/ingress/describe +++ b/gcloud/alpha/container/hub/ingress/describe @@ -7,7 +7,7 @@ SYNOPSIS DESCRIPTION (ALPHA) This command describes the status of Multi-cluster Ingress Feature - resource in Hub. + resource in fleet. EXAMPLES To describe the Ingress Feature, run: diff --git a/gcloud/alpha/container/hub/ingress/disable b/gcloud/alpha/container/hub/ingress/disable index e2bc6841a..e9f418805 100644 --- a/gcloud/alpha/container/hub/ingress/disable +++ b/gcloud/alpha/container/hub/ingress/disable @@ -6,7 +6,7 @@ SYNOPSIS gcloud alpha container hub ingress disable [--force] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) This command disables Multi-cluster Ingress Feature in Hub. + (ALPHA) This command disables Multi-cluster Ingress Feature in a fleet. EXAMPLES To disable the Ingress Feature, run: diff --git a/gcloud/alpha/container/hub/ingress/enable b/gcloud/alpha/container/hub/ingress/enable index f827a2e51..68ff4d7f6 100644 --- a/gcloud/alpha/container/hub/ingress/enable +++ b/gcloud/alpha/container/hub/ingress/enable @@ -7,7 +7,7 @@ SYNOPSIS [--config-membership=CONFIG_MEMBERSHIP] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) This command enables Multi-cluster Ingress Feature in Hub. + (ALPHA) This command enables Multi-cluster Ingress Feature in a fleet. EXAMPLES To enable the Ingress Feature, run: diff --git a/gcloud/alpha/container/hub/ingress/update b/gcloud/alpha/container/hub/ingress/update index d79b96d1f..911fbe290 100644 --- a/gcloud/alpha/container/hub/ingress/update +++ b/gcloud/alpha/container/hub/ingress/update @@ -7,7 +7,7 @@ SYNOPSIS [--config-membership=CONFIG_MEMBERSHIP] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) This command updates Multi-cluster Ingress Feature in Hub. + (ALPHA) This command updates Multi-cluster Ingress Feature in a fleet. EXAMPLES To update the Ingress Feature, run: diff --git a/gcloud/alpha/container/hub/memberships/generate-gateway-rbac b/gcloud/alpha/container/hub/memberships/generate-gateway-rbac index 37bd439f1..65c160440 100644 --- a/gcloud/alpha/container/hub/memberships/generate-gateway-rbac +++ b/gcloud/alpha/container/hub/memberships/generate-gateway-rbac @@ -27,16 +27,18 @@ EXAMPLES directory: $ gcloud alpha container hub memberships generate-gateway-rbac \ - --membership=my-cluster - --users=foo@example.com,test-acct@test-project.iam.gserviceaccount.com - --role=clusterrole/cluster-reader --rbac-output-file=./rbac.yaml + --membership=my-cluster \ + --users=foo@example.com,\ + test-acct@test-project.iam.gserviceaccount.com \ + --role=clusterrole/cluster-admin --rbac-output-file=./rbac.yaml Dry run mode to generate the RBAC policy, and print on screen: $ gcloud alpha container hub memberships generate-gateway-rbac \ - --membership=my-cluster - --users=foo@example.com,test-acct@test-project.iam.gserviceaccount.com - --role=clusterrole/cluster-reader + --membership=my-cluster \ + --users=foo@example.com,\ + test-acct@test-project.iam.gserviceaccount.com \ + --role=clusterrole/cluster-admin Anthos support mode, generate the RBAC policy file with read-only permission for TSE/Eng to debug customers' clusters: @@ -47,18 +49,20 @@ EXAMPLES Apply mode, generate the RBAC policy and apply it to the specified cluster: $ gcloud alpha container hub memberships generate-gateway-rbac \ - --membership=my-cluster - --users=foo@example.com,test-acct@test-project.iam.gserviceaccount.com - --role=clusterrole/cluster-reader --context=my-cluster-contex - --kubeconfig=/home/user/custom_kubeconfig --apply + --membership=my-cluster \ + --users=foo@example.com,\ + test-acct@test-project.iam.gserviceaccount.com \ + --role=clusterrole/cluster-admin --context=my-cluster-contex \ + --kubeconfig=/home/user/custom_kubeconfig --apply Revoke mode, revoke the RBAC policy for the specified users: $ gcloud alpha container hub memberships generate-gateway-rbac \ - --membership=my-cluster - --users=foo@example.com,test-acct@test-project.iam.gserviceaccount.com - --role=clusterrole/cluster-reader --context=my-cluster-contex - --kubeconfig=/home/user/custom_kubeconfig --apply + --membership=my-cluster \ + --users=foo@example.com,\ + test-acct@test-project.iam.gserviceaccount.com \ + --role=clusterrole/cluster-admin --context=my-cluster-contex \ + --kubeconfig=/home/user/custom_kubeconfig --apply FLAGS --anthos-support diff --git a/gcloud/alpha/container/hub/memberships/register b/gcloud/alpha/container/hub/memberships/register index 9f7b07d0f..50dc2b4f9 100644 --- a/gcloud/alpha/container/hub/memberships/register +++ b/gcloud/alpha/container/hub/memberships/register @@ -49,72 +49,72 @@ EXAMPLES kubeconfig file, and install the Connect Agent: $ gcloud alpha container hub memberships register my-cluster \ - --context=my-cluster-context \ - --kubeconfig=/home/user/custom_kubeconfig \ - --service-account-key-file=/tmp/keyfile.json + --context=my-cluster-context \ + --kubeconfig=/home/user/custom_kubeconfig \ + --service-account-key-file=/tmp/keyfile.json Register a non-GKE or GKE On-Prem cluster referenced from the default kubeconfig file, and install the Connect Agent: $ gcloud alpha container hub memberships register my-cluster \ - --context=my-cluster-context \ - --service-account-key-file=/tmp/keyfile.json + --context=my-cluster-context \ + --service-account-key-file=/tmp/keyfile.json Register a non-GKE or GKE On-Prem cluster, and install a specific version of the Connect Agent: $ gcloud alpha container hub memberships register my-cluster \ - --context=my-cluster-context \ - --version=gkeconnect_20190802_02_00 \ - --service-account-key-file=/tmp/keyfile.json + --context=my-cluster-context \ + --version=gkeconnect_20190802_02_00 \ + --service-account-key-file=/tmp/keyfile.json Register a non-GKE or GKE On-Prem cluster and output a manifest that can be used to install the Connect Agent: $ gcloud alpha container hub memberships register my-cluster \ - --context=my-cluster-context \ - --manifest-output-file=/tmp/manifest.yaml \ - --service-account-key-file=/tmp/keyfile.json + --context=my-cluster-context \ + --manifest-output-file=/tmp/manifest.yaml \ + --service-account-key-file=/tmp/keyfile.json Register a GKE cluster referenced from a GKE URI, and install the Connect Agent: $ gcloud alpha container hub memberships register my-cluster \ - --gke-uri=my-cluster-gke-uri \ - --service-account-key-file=/tmp/keyfile.json + --gke-uri=my-cluster-gke-uri \ + --service-account-key-file=/tmp/keyfile.json Register a GKE cluster referenced from a GKE Cluster location and name, and install the Connect Agent: $ gcloud alpha container hub memberships register my-cluster \ - --gke-cluster=my-cluster-region-or-zone/my-cluster \ - --service-account-key-file=/tmp/keyfile.json + --gke-cluster=my-cluster-region-or-zone/my-cluster \ + --service-account-key-file=/tmp/keyfile.json Register a GKE cluster, and install a specific version of the Connect Agent: $ gcloud alpha container hub memberships register my-cluster \ - --gke-uri=my-cluster-gke-uri \ - --version=gkeconnect_20190802_02_00 \ - --service-account-key-file=/tmp/keyfile.json + --gke-uri=my-cluster-gke-uri \ + --version=gkeconnect_20190802_02_00 \ + --service-account-key-file=/tmp/keyfile.json $ gcloud alpha container hub memberships register my-cluster \ - --gke-cluster=my-cluster-region-or-zone/my-cluster \ - --version=gkeconnect_20190802_02_00 \ - --service-account-key-file=/tmp/keyfile.json + --gke-cluster=my-cluster-region-or-zone/my-cluster \ + --version=gkeconnect_20190802_02_00 \ + --service-account-key-file=/tmp/keyfile.json Register a GKE cluster and output a manifest that can be used to install the Connect Agent: $ gcloud alpha container hub memberships register my-cluster \ - --gke-uri=my-cluster-gke-uri \ - --manifest-output-file=/tmp/manifest.yaml \ - --service-account-key-file=/tmp/keyfile.json + --gke-uri=my-cluster-gke-uri \ + --manifest-output-file=/tmp/manifest.yaml \ + --service-account-key-file=/tmp/keyfile.json $ gcloud alpha container hub memberships register my-cluster \ - --gke-cluster=my-cluster-region-or-zone/my-cluster \ - --manifest-output-file=/tmp/manifest.yaml \ - --service-account-key-file=/tmp/keyfile.json + --gke-cluster=my-cluster-region-or-zone/my-cluster \ + --manifest-output-file=/tmp/manifest.yaml \ + --service-account-key-file=/tmp/keyfile.json POSITIONAL ARGUMENTS CLUSTER_NAME diff --git a/gcloud/alpha/container/hub/memberships/unregister b/gcloud/alpha/container/hub/memberships/unregister index f47505916..113dec2c1 100644 --- a/gcloud/alpha/container/hub/memberships/unregister +++ b/gcloud/alpha/container/hub/memberships/unregister @@ -39,8 +39,8 @@ EXAMPLES Unregister a non-GKE cluster referenced from a specific kubeconfig file: $ gcloud alpha container hub memberships unregister my-membership \ - --context=my-cluster-context \ - --kubeconfig=/home/user/custom_kubeconfig + --context=my-cluster-context \ + --kubeconfig=/home/user/custom_kubeconfig Unregister a non-GKE cluster referenced from the default kubeconfig file: @@ -50,12 +50,12 @@ EXAMPLES Unregister a GKE cluster referenced from a GKE URI: $ gcloud alpha container hub memberships unregister my-membership \ - --gke-uri=my-cluster-gke-uri + --gke-uri=my-cluster-gke-uri Unregister a GKE cluster referenced from a GKE Cluster location and name: $ gcloud alpha container hub memberships unregister my-membership \ - --gke-cluster=my-cluster-region-or-zone/my-cluster + --gke-cluster=my-cluster-region-or-zone/my-cluster POSITIONAL ARGUMENTS CLUSTER_NAME diff --git a/gcloud/alpha/container/hub/mesh/describe b/gcloud/alpha/container/hub/mesh/describe index aaa290b64..4463c889e 100644 --- a/gcloud/alpha/container/hub/mesh/describe +++ b/gcloud/alpha/container/hub/mesh/describe @@ -6,7 +6,7 @@ SYNOPSIS gcloud alpha container hub mesh describe [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Describe the status of Service Mesh Feature resource in Hub. + (ALPHA) Describe the status of Service Mesh Feature resource in a fleet. EXAMPLES To describe the Service Mesh Feature, run: diff --git a/gcloud/alpha/container/hub/mesh/disable b/gcloud/alpha/container/hub/mesh/disable index 0330fae94..280ce74f7 100644 --- a/gcloud/alpha/container/hub/mesh/disable +++ b/gcloud/alpha/container/hub/mesh/disable @@ -5,7 +5,7 @@ SYNOPSIS gcloud alpha container hub mesh disable [--force] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Disable the Service Mesh Feature in Hub. + (ALPHA) Disable the Service Mesh Feature in a fleet. EXAMPLES To disable the Service Mesh Feature, run: diff --git a/gcloud/alpha/container/hub/mesh/enable b/gcloud/alpha/container/hub/mesh/enable index d8cc5013f..ab7f440ed 100644 --- a/gcloud/alpha/container/hub/mesh/enable +++ b/gcloud/alpha/container/hub/mesh/enable @@ -5,7 +5,7 @@ SYNOPSIS gcloud alpha container hub mesh enable [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Enable the Service Mesh Feature in Hub. + (ALPHA) Enable the Service Mesh Feature in a fleet. EXAMPLES To enable the Service Mesh Feature, run: diff --git a/gcloud/alpha/container/hub/mesh/update b/gcloud/alpha/container/hub/mesh/update index 7eefdde2d..fc58434b0 100644 --- a/gcloud/alpha/container/hub/mesh/update +++ b/gcloud/alpha/container/hub/mesh/update @@ -13,8 +13,8 @@ EXAMPLES To update the control plane management of a Membership named MEMBERSHIP, run: - $ gcloud alpha container hub mesh update --membership=MEMBERSHIP - --control-plane=CONTROL_PLANE + $ gcloud alpha container hub mesh update --membership=MEMBERSHIP \ + --control-plane=CONTROL_PLANE REQUIRED FLAGS --control-plane=CONTROL_PLANE diff --git a/gcloud/alpha/container/hub/multi-cluster-services/describe b/gcloud/alpha/container/hub/multi-cluster-services/describe index 0c752e4ef..60393fe3a 100644 --- a/gcloud/alpha/container/hub/multi-cluster-services/describe +++ b/gcloud/alpha/container/hub/multi-cluster-services/describe @@ -8,7 +8,7 @@ SYNOPSIS DESCRIPTION (ALPHA) This command gets the detailed status of the Multi-cluster Services - Feature in Hub. + Feature in a fleet. EXAMPLES To describe the Multi-cluster Services Feature, run: diff --git a/gcloud/alpha/container/hub/multi-cluster-services/disable b/gcloud/alpha/container/hub/multi-cluster-services/disable index d98e49839..a9cc00fcf 100644 --- a/gcloud/alpha/container/hub/multi-cluster-services/disable +++ b/gcloud/alpha/container/hub/multi-cluster-services/disable @@ -7,7 +7,8 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) This command disables the Multi-cluster Services Feature in Hub. + (ALPHA) This command disables the Multi-cluster Services Feature in a + fleet. EXAMPLES To disable the Multi-cluster Services Feature, run: diff --git a/gcloud/alpha/container/hub/multi-cluster-services/enable b/gcloud/alpha/container/hub/multi-cluster-services/enable index 424039b9d..aeb568533 100644 --- a/gcloud/alpha/container/hub/multi-cluster-services/enable +++ b/gcloud/alpha/container/hub/multi-cluster-services/enable @@ -7,7 +7,7 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) This command enables the Multi-cluster Services Feature in Hub. + (ALPHA) This command enables the Multi-cluster Services Feature in a fleet. EXAMPLES To enable the Multi-cluster Services Feature, run: diff --git a/gcloud/alpha/container/hub/service-directory/describe b/gcloud/alpha/container/hub/service-directory/describe index b6f869ec6..9ec89325a 100644 --- a/gcloud/alpha/container/hub/service-directory/describe +++ b/gcloud/alpha/container/hub/service-directory/describe @@ -8,7 +8,7 @@ SYNOPSIS DESCRIPTION (ALPHA) This command gets the detailed status of the Service Directory - Feature resource in Hub. + Feature resource in a fleet. EXAMPLES To describe the Service Directory Feature, run: diff --git a/gcloud/alpha/container/hub/service-directory/disable b/gcloud/alpha/container/hub/service-directory/disable index c746f5e3e..3856c5127 100644 --- a/gcloud/alpha/container/hub/service-directory/disable +++ b/gcloud/alpha/container/hub/service-directory/disable @@ -7,7 +7,7 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Disables the Service Directory Feature in Hub. + (ALPHA) Disables the Service Directory Feature in a fleet. EXAMPLES To disable the Service Directory Feature, run: diff --git a/gcloud/alpha/container/hub/service-directory/enable b/gcloud/alpha/container/hub/service-directory/enable index e06d2ac65..95e022978 100644 --- a/gcloud/alpha/container/hub/service-directory/enable +++ b/gcloud/alpha/container/hub/service-directory/enable @@ -6,7 +6,7 @@ SYNOPSIS gcloud alpha container hub service-directory enable [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Enables the Service Directory Feature in Hub. + (ALPHA) Enables the Service Directory Feature in a fleet. EXAMPLES To enable the Service Directory Feature, run: diff --git a/gcloud/alpha/container/images/add-tag b/gcloud/alpha/container/images/add-tag index db8be5b88..0081775de 100644 --- a/gcloud/alpha/container/images/add-tag +++ b/gcloud/alpha/container/images/add-tag @@ -15,25 +15,23 @@ EXAMPLES Add a tag to another tag: $ gcloud alpha container images add-tag \ - gcr.io/myproject/myimage:mytag1 - gcr.io/myproject/myimage:mytag2 + gcr.io/myproject/myimage:mytag1 gcr.io/myproject/myimage:mytag2 Add a tag to a digest $ gcloud alpha container images add-tag \ - gcr.io/myproject/myimage@sha256:digest - gcr.io/myproject/myimage:mytag2 + gcr.io/myproject/myimage@sha256:digest \ + gcr.io/myproject/myimage:mytag2 Add a tag to latest - $ gcloud alpha container images add-tag gcr.io/myproject/myimage - gcr.io/myproject/myimage:mytag2 + $ gcloud alpha container images add-tag gcr.io/myproject/myimage \ + gcr.io/myproject/myimage:mytag2 Promote a tag to latest $ gcloud alpha container images add-tag \ - gcr.io/myproject/myimage:mytag1 - gcr.io/myproject/myimage:latest + gcr.io/myproject/myimage:mytag1 gcr.io/myproject/myimage:latest POSITIONAL ARGUMENTS SRC_IMAGE diff --git a/gcloud/alpha/container/images/delete b/gcloud/alpha/container/images/delete index 3828e7ed2..593662bcc 100644 --- a/gcloud/alpha/container/images/delete +++ b/gcloud/alpha/container/images/delete @@ -30,8 +30,8 @@ EXAMPLES digests that lack tags: $ gcloud container images list-tags \ - [HOSTNAME]/[PROJECT-ID]/[IMAGE] \ - --filter='-tags:*' --format="get(digest)" --limit=$BIG_NUMBER + [HOSTNAME]/[PROJECT-ID]/[IMAGE] --filter='-tags:*' \ + --format="get(digest)" --limit=$BIG_NUMBER Then, delete these tagless images without prompting by running: diff --git a/gcloud/alpha/container/images/describe b/gcloud/alpha/container/images/describe index 3dc719aa8..0671b2059 100644 --- a/gcloud/alpha/container/images/describe +++ b/gcloud/alpha/container/images/describe @@ -16,18 +16,22 @@ EXAMPLES $ gcloud alpha container images describe \ gcr.io/myproject/myimage@digest - OR + + Or: + $ gcloud alpha container images describe gcr.io/myproject/myimage:tag Find the digest for a tag: $ gcloud alpha container images describe \ gcr.io/myproject/myimage:tag \ - --format="value(image_summary.digest)" - OR + --format="value(image_summary.digest)" + + Or: + $ gcloud alpha container images describe \ gcr.io/myproject/myimage:tag \ - --format="value(image_summary.fully_qualified_digest)" + --format="value(image_summary.fully_qualified_digest)" See package vulnerabilities found by the Container Analysis API for the specified image: diff --git a/gcloud/alpha/container/node-pools/create b/gcloud/alpha/container/node-pools/create index 8b73b05c7..022f92420 100644 --- a/gcloud/alpha/container/node-pools/create +++ b/gcloud/alpha/container/node-pools/create @@ -8,8 +8,9 @@ SYNOPSIS [--boot-disk-kms-key=BOOT_DISK_KMS_KEY] [--cluster=CLUSTER] [--disk-size=DISK_SIZE] [--disk-type=DISK_TYPE] [--enable-autoprovisioning] [--enable-autorepair] - [--no-enable-autoupgrade] [--enable-gvnic] [--enable-image-streaming] - [--image-type=IMAGE_TYPE] [--linux-sysctls=KEY=VALUE,[KEY=VALUE,...]] + [--no-enable-autoupgrade] [--enable-confidential-nodes] + [--enable-gvnic] [--enable-image-streaming] [--image-type=IMAGE_TYPE] + [--linux-sysctls=KEY=VALUE,[KEY=VALUE,...]] [--machine-type=MACHINE_TYPE, -m MACHINE_TYPE] [--max-pods-per-node=MAX_PODS_PER_NODE] [--max-surge-upgrade=MAX_SURGE_UPGRADE; default=1] @@ -126,6 +127,11 @@ FLAGS Enabled by default, use --no-enable-autoupgrade to disable. + --enable-confidential-nodes + Enable confidential nodes for the node pool. Enabling Confidential + Nodes will create nodes using Confidential VM + https://cloud.google.com/compute/confidential-vm/docs/about-cvm. + --enable-gvnic Enable the use of GVNIC for this cluster. Requires re-creation of nodes using either a node-pool upgrade or node-pool creation. @@ -309,6 +315,7 @@ FLAGS Multiple locations can be specified, separated by commas. For example: $ gcloud alpha container node-pools create node-pool-1 \ + --cluster=sample-cluster \ --node-locations=us-central1-a,us-central1-b --node-taints=[NODE_TAINT,...] diff --git a/gcloud/alpha/container/node-pools/update b/gcloud/alpha/container/node-pools/update index f94e6631e..0bb8b6a30 100644 --- a/gcloud/alpha/container/node-pools/update +++ b/gcloud/alpha/container/node-pools/update @@ -4,9 +4,9 @@ NAME SYNOPSIS gcloud alpha container node-pools update NAME - (--enable-gvnic | --enable-image-streaming - | --node-labels=[NODE_LABEL,...] | --node-locations=ZONE,[ZONE,...] - | --node-taints=[NODE_TAINT,...] + (--enable-confidential-nodes | --enable-gvnic + | --enable-image-streaming | --node-labels=[NODE_LABEL,...] + | --node-locations=ZONE,[ZONE,...] | --node-taints=[NODE_TAINT,...] | --system-config-from-file=SYSTEM_CONFIG_FROM_FILE | --tags=[TAG,...] | --workload-metadata=WORKLOAD_METADATA | --enable-autoprovisioning @@ -35,6 +35,10 @@ POSITIONAL ARGUMENTS REQUIRED FLAGS Exactly one of these must be specified: + --enable-confidential-nodes + Recreate all the nodes in the node pool to be confidential VM + https://cloud.google.com/compute/confidential-vm/docs/about-cvm. + --enable-gvnic Enable the use of GVNIC for this cluster. Requires re-creation of nodes using either a node-pool upgrade or node-pool creation. @@ -72,6 +76,7 @@ REQUIRED FLAGS example: $ gcloud alpha container node-pools update node-pool-1 \ + --cluster=sample-cluster \ --node-locations=us-central1-a,us-central1-b --node-taints=[NODE_TAINT,...] diff --git a/gcloud/alpha/container/subnets/list-usable b/gcloud/alpha/container/subnets/list-usable index 61cc6fefe..c3897b0ba 100644 --- a/gcloud/alpha/container/subnets/list-usable +++ b/gcloud/alpha/container/subnets/list-usable @@ -21,15 +21,14 @@ DESCRIPTION EXAMPLES List all subnetworks usable for cluster creation in project my-project. - $ gcloud alpha container subnets list-usable \ - --project=my-project + $ gcloud alpha container subnets list-usable --project=my-project List all subnetworks existing in project my-shared-host-project usable for cluster creation in project my-service-project. $ gcloud alpha container subnets list-usable \ - --project=my-service-project \ - --network-project=my-shared-host-project + --project=my-service-project \ + --network-project=my-shared-host-project FLAGS --network-project=NETWORK_PROJECT diff --git a/gcloud/alpha/data-catalog/crawlers/create b/gcloud/alpha/data-catalog/crawlers/create index 23fa5849e..8bc318821 100644 --- a/gcloud/alpha/data-catalog/crawlers/create +++ b/gcloud/alpha/data-catalog/crawlers/create @@ -16,7 +16,8 @@ EXAMPLES Create a project-scoped crawler: $ gcloud alpha data-catalog crawlers create crawler1 \ - --run-option=MANUAL --display-name=my-crawler --crawl-scope=PROJECT + --run-option=MANUAL --display-name=my-crawler \ + --crawl-scope=PROJECT Create a bucket-scoped crawler that runs weekly: diff --git a/gcloud/alpha/data-catalog/entries/create b/gcloud/alpha/data-catalog/entries/create index dcecd2edb..d890dcad7 100644 --- a/gcloud/alpha/data-catalog/entries/create +++ b/gcloud/alpha/data-catalog/entries/create @@ -25,7 +25,8 @@ EXAMPLES $ gcloud alpha data-catalog entries create entry1 \ --location=us-central1 --entry-group=group1 \ - --gcs-file-patterns="gs://bucket1/*" --display-name="sales data" \ + --gcs-file-patterns="gs://bucket1/*" \ + --display-name="sales data" \ --schema="qtr=STRING,sales=FLOAT,year=STRING" To create an entry for a Google Cloud Storage fileset with a schema from a @@ -33,8 +34,8 @@ EXAMPLES $ gcloud alpha data-catalog entries create entry1 \ --location=us-central1 --entry-group=group1 \ - --gcs-file-patterns="gs://bucket1/*" --display-name="sales data" \ - --schema-from-file=/tmp/schema.json + --gcs-file-patterns="gs://bucket1/*" \ + --display-name="sales data" --schema-from-file=/tmp/schema.json POSITIONAL ARGUMENTS Entry resource - Entry to create. The arguments in this group can be used diff --git a/gcloud/alpha/data-catalog/entry-groups/create b/gcloud/alpha/data-catalog/entry-groups/create index 5b499033d..cf63ecaf3 100644 --- a/gcloud/alpha/data-catalog/entry-groups/create +++ b/gcloud/alpha/data-catalog/entry-groups/create @@ -14,8 +14,9 @@ EXAMPLES To create an entry group for some data, run: $ gcloud alpha data-catalog entry-groups create group1 \ - --location=us-central1 --display-name="analytics data - jan 2011" \ - --description="Entries related to January 2011 analytics data." + --location=us-central1 \ + --display-name="analytics data - jan 2011" \ + --description="Entries related to January 2011 analytics data." POSITIONAL ARGUMENTS Entry group resource - Entry group to create. The arguments in this group diff --git a/gcloud/alpha/data-catalog/tag-templates/create b/gcloud/alpha/data-catalog/tag-templates/create index ee51363ce..62d22e744 100644 --- a/gcloud/alpha/data-catalog/tag-templates/create +++ b/gcloud/alpha/data-catalog/tag-templates/create @@ -29,7 +29,8 @@ EXAMPLES $ gcloud alpha data-catalog tag-templates create TEMPLATE \ --field=id=ID1,display-name=DISPLAY1,type=string \ - --field=id=ID2,display-name=DISPLAY2,type='enum(A|B)',required=TRUE + --field=id=ID2,display-name=DISPLAY2,type='enum(A|B)',\ + required=TRUE POSITIONAL ARGUMENTS Tag template resource - Tag template to create. The arguments in this diff --git a/gcloud/alpha/database-migration/migration-jobs/create b/gcloud/alpha/database-migration/migration-jobs/create index d75aa6d4f..8fa736cca 100644 --- a/gcloud/alpha/database-migration/migration-jobs/create +++ b/gcloud/alpha/database-migration/migration-jobs/create @@ -18,7 +18,7 @@ EXAMPLES To create a migration job with vpc peering connectivity: $ gcloud alpha database-migration migration-jobs create \ - MIGRATION_JOB --region=us-central1 --display-name=my-job \ + MIGRATION_JOB --region=us-central1 --display-name=my-job \ --source=cp1 --destination=cp2 --peer-vpc=network1 POSITIONAL ARGUMENTS diff --git a/gcloud/alpha/database-migration/migration-jobs/update b/gcloud/alpha/database-migration/migration-jobs/update index 3aa9f69b9..e5c9dc03d 100644 --- a/gcloud/alpha/database-migration/migration-jobs/update +++ b/gcloud/alpha/database-migration/migration-jobs/update @@ -20,7 +20,7 @@ EXAMPLES destination connection profiles: $ gcloud alpha database-migration migration-jobs update \ - MIGRATION_JOB --region=us-central1 --display-name=new-name \ + MIGRATION_JOB --region=us-central1 --display-name=new-name \ --source=new-src --destination=new-dest POSITIONAL ARGUMENTS diff --git a/gcloud/alpha/dataplex/tasks/add-iam-policy-binding b/gcloud/alpha/dataplex/tasks/add-iam-policy-binding index ee7f45c1e..c250e64d3 100644 --- a/gcloud/alpha/dataplex/tasks/add-iam-policy-binding +++ b/gcloud/alpha/dataplex/tasks/add-iam-policy-binding @@ -16,7 +16,7 @@ EXAMPLES location us-central, run: $ gcloud alpha dataplex tasks add-iam-policy-binding test-task \ - --location=us-central1 --lake=test-lake \ + --location=us-central1 --lake=test-lake \ --role=roles/dataplex.viewer --member=user:testuser@gmail.com See https://cloud.google.com/dataplex/docs/iam-roles for details of policy diff --git a/gcloud/alpha/dataplex/tasks/create b/gcloud/alpha/dataplex/tasks/create index 6ed0a87c7..a57f3786a 100644 --- a/gcloud/alpha/dataplex/tasks/create +++ b/gcloud/alpha/dataplex/tasks/create @@ -47,7 +47,8 @@ EXAMPLES $ gcloud alpha dataplex tasks create test-task \ --location=us-central1 --lake=test-lake \ - --execution-service-account=dataplex-demo-test@test-project.iam.gserviceaccount.com \ + --execution-service-account=dataplex-demo-test@test-project.iam.\ + gserviceaccount.com \ --spark-python-script-file=gs://test-bucket/test-file.py \ --trigger-type=ON_DEMAND @@ -59,9 +60,10 @@ EXAMPLES $ gcloud alpha dataplex tasks create test-task \ --location=us-central1 --lake=test-lake \ - --execution-service-account=dataplex-demo-test@test-project.iam.gserviceaccount.com \ - --spark-python-script-file=gs://test-bucket/test-file.py \ - --trigger-type=RECURRING --trigger-schedule="0 * * * *" + --execution-service-account=dataplex-demo-test@test-project.iam.\ + gserviceaccount.com \ + --spark-python-script-file=gs://test-bucket/test-file.py \ + --trigger-type=RECURRING --trigger-schedule="0 * * * *" POSITIONAL ARGUMENTS Task resource - Arguments and flags that specify the Dataplex Task you diff --git a/gcloud/alpha/dataplex/tasks/remove-iam-policy-binding b/gcloud/alpha/dataplex/tasks/remove-iam-policy-binding index be02337c7..6d4b6b65f 100644 --- a/gcloud/alpha/dataplex/tasks/remove-iam-policy-binding +++ b/gcloud/alpha/dataplex/tasks/remove-iam-policy-binding @@ -16,7 +16,7 @@ EXAMPLES location us-central1, run: $ gcloud alpha dataplex tasks remove-iam-policy-binding test-task \ - --location=us-central1 --lake=test-lake \ + --location=us-central1 --lake=test-lake \ --role=roles/dataplex.viewer --member=user:testuser@gmail.com See https://cloud.google.com/dataplex/docs/iam-roles for details of policy diff --git a/gcloud/alpha/dataplex/tasks/update b/gcloud/alpha/dataplex/tasks/update index f36ceefa9..155e54302 100644 --- a/gcloud/alpha/dataplex/tasks/update +++ b/gcloud/alpha/dataplex/tasks/update @@ -37,8 +37,7 @@ EXAMPLES $ gcloud alpha dataplex tasks update \ projects/test-project/locations/us-central1/lakes/test-lake/\ - tasks/test-task \ - --description='Updated Description' + tasks/test-task --description='Updated Description' POSITIONAL ARGUMENTS Task resource - Arguments and flags that specify the Dataplex Task you diff --git a/gcloud/alpha/dataproc/autoscaling-policies/set-iam-policy b/gcloud/alpha/dataproc/autoscaling-policies/set-iam-policy index 7f37fff79..2385bf256 100644 --- a/gcloud/alpha/dataproc/autoscaling-policies/set-iam-policy +++ b/gcloud/alpha/dataproc/autoscaling-policies/set-iam-policy @@ -17,8 +17,8 @@ EXAMPLES 'example-autoscaling-policy' $ gcloud alpha dataproc autoscaling-policies set-iam-policy \ - autoscaling-policies set-iam-policy \ - example-autoscaling-policy policy.json + autoscaling-policies set-iam-policy example-autoscaling-policy \ + policy.json See https://cloud.google.com/iam/docs/managing-policies for details of the policy file format and contents. diff --git a/gcloud/alpha/dataproc/jobs/submit/hadoop b/gcloud/alpha/dataproc/jobs/submit/hadoop index 6d38856c5..80cb48b76 100644 --- a/gcloud/alpha/dataproc/jobs/submit/hadoop +++ b/gcloud/alpha/dataproc/jobs/submit/hadoop @@ -25,8 +25,8 @@ EXAMPLES To submit a Hadoop job that runs a specific class of a jar, run: $ gcloud alpha dataproc jobs submit hadoop --cluster=my_cluster \ - --class=org.my.main.Class \ - --jars=my_jar1.jar,my_jar2.jar -- arg1 arg2 + --class=org.my.main.Class --jars=my_jar1.jar,my_jar2.jar \ + -- arg1 arg2 To submit a Hadoop job that runs a jar that is already on the cluster, run: diff --git a/gcloud/alpha/dataproc/jobs/submit/hive b/gcloud/alpha/dataproc/jobs/submit/hive index dc0afda7f..0e3367321 100644 --- a/gcloud/alpha/dataproc/jobs/submit/hive +++ b/gcloud/alpha/dataproc/jobs/submit/hive @@ -23,9 +23,9 @@ EXAMPLES To submit a Hive job with inline queries, run: - $ gcloud alpha dataproc jobs submit hive --cluster=my_cluster - -e="CREATE EXTERNAL TABLE foo(bar int) LOCATION 'gs://my_bucket/'" - -e="SELECT * FROM foo WHERE bar > 2" + $ gcloud alpha dataproc jobs submit hive --cluster=my_cluster \ + -e="CREATE EXTERNAL TABLE foo(bar int) LOCATION \ + 'gs://my_bucket/'" -e="SELECT * FROM foo WHERE bar > 2" REQUIRED FLAGS Exactly one of these must be specified: diff --git a/gcloud/alpha/dataproc/jobs/submit/pig b/gcloud/alpha/dataproc/jobs/submit/pig index bdd075b81..8194edaa9 100644 --- a/gcloud/alpha/dataproc/jobs/submit/pig +++ b/gcloud/alpha/dataproc/jobs/submit/pig @@ -24,11 +24,11 @@ EXAMPLES To submit a Pig job with inline queries, run: - $ gcloud alpha dataproc jobs submit pig --cluster=my_cluster - -e="LNS = LOAD 'gs://my_bucket/my_file.txt' AS (line)" - -e="WORDS = FOREACH LNS GENERATE FLATTEN(TOKENIZE(line)) AS word" - -e="GROUPS = GROUP WORDS BY word" - -e="WORD_COUNTS = FOREACH GROUPS GENERATE group, COUNT(WORDS)" + $ gcloud alpha dataproc jobs submit pig --cluster=my_cluster \ + -e="LNS = LOAD 'gs://my_bucket/my_file.txt' AS (line)" \ + -e="WORDS = FOREACH LNS GENERATE FLATTEN(TOKENIZE(line)) AS \ + word" -e="GROUPS = GROUP WORDS BY word" \ + -e="WORD_COUNTS = FOREACH GROUPS GENERATE group, COUNT(WORDS)" \ -e="DUMP WORD_COUNTS" REQUIRED FLAGS diff --git a/gcloud/alpha/dataproc/jobs/submit/spark b/gcloud/alpha/dataproc/jobs/submit/spark index a26376754..be322af9a 100644 --- a/gcloud/alpha/dataproc/jobs/submit/spark +++ b/gcloud/alpha/dataproc/jobs/submit/spark @@ -31,8 +31,7 @@ EXAMPLES To submit a Spark job that runs a jar that is already on the cluster, run: $ gcloud alpha dataproc jobs submit spark --cluster=my_cluster \ - --region=us-central1 \ - --class=org.apache.spark.examples.SparkPi \ + --region=us-central1 --class=org.apache.spark.examples.SparkPi \ --jars=file:///usr/lib/spark/examples/jars/spark-examples.jar \ -- 1000 diff --git a/gcloud/alpha/dataproc/jobs/submit/spark-r b/gcloud/alpha/dataproc/jobs/submit/spark-r index b44f98efc..ac3e41972 100644 --- a/gcloud/alpha/dataproc/jobs/submit/spark-r +++ b/gcloud/alpha/dataproc/jobs/submit/spark-r @@ -25,8 +25,7 @@ EXAMPLES To submit a Spark job that runs a script already on the cluster, run: $ gcloud alpha dataproc jobs submit spark-r --cluster=my_cluster \ - file:///.../my_script.R \ - -- gs://my_bucket/data.csv + file:///.../my_script.R -- gs://my_bucket/data.csv POSITIONAL ARGUMENTS R_FILE diff --git a/gcloud/alpha/dataproc/jobs/submit/spark-sql b/gcloud/alpha/dataproc/jobs/submit/spark-sql index 022466ae7..b0d20b5c4 100644 --- a/gcloud/alpha/dataproc/jobs/submit/spark-sql +++ b/gcloud/alpha/dataproc/jobs/submit/spark-sql @@ -24,9 +24,9 @@ EXAMPLES To submit a Spark SQL job with inline queries, run: - $ gcloud alpha dataproc jobs submit spark-sql --cluster=my_cluster - -e="CREATE EXTERNAL TABLE foo(bar int) LOCATION 'gs://my_bucket/'" - -e="SELECT * FROM foo WHERE bar > 2" + $ gcloud alpha dataproc jobs submit spark-sql --cluster=my_cluster \ + -e="CREATE EXTERNAL TABLE foo(bar int) LOCATION \ + 'gs://my_bucket/'" -e="SELECT * FROM foo WHERE bar > 2" REQUIRED FLAGS Exactly one of these must be specified: diff --git a/gcloud/alpha/dataproc/jobs/wait b/gcloud/alpha/dataproc/jobs/wait index 0afbb368e..fdb6da107 100644 --- a/gcloud/alpha/dataproc/jobs/wait +++ b/gcloud/alpha/dataproc/jobs/wait @@ -18,7 +18,7 @@ EXAMPLES run: $ gcloud dataproc jobs list --format "table(reference.jobId)" \ - --limit 1 --log-http + --limit 1 --log-http To view the output of a job as it runs, run: diff --git a/gcloud/alpha/dataproc/workflow-templates/add-job/help b/gcloud/alpha/dataproc/workflow-templates/add-job/help index 93fcaf496..602a0b8f5 100644 --- a/gcloud/alpha/dataproc/workflow-templates/add-job/help +++ b/gcloud/alpha/dataproc/workflow-templates/add-job/help @@ -10,20 +10,17 @@ EXAMPLES To add a Hadoop MapReduce job, run: $ gcloud alpha dataproc workflow-templates add-job hadoop \ - --workflow-template my_template --jar my_jar.jar \ - -- arg1 arg2 + --workflow-template my_template --jar my_jar.jar -- arg1 arg2 To add a Spark Scala or Java job, run: $ gcloud alpha dataproc workflow-templates add-job spark \ - --workflow-template my_template --jar my_jar.jar \ - -- arg1 arg2 + --workflow-template my_template --jar my_jar.jar -- arg1 arg2 To add a PySpark job, run: $ gcloud alpha dataproc workflow-templates add-job pyspark \ - --workflow-template my_template my_script.py \ - -- arg1 arg2 + --workflow-template my_template my_script.py -- arg1 arg2 To add a Spark SQL job, run: diff --git a/gcloud/alpha/dataproc/workflow-templates/help b/gcloud/alpha/dataproc/workflow-templates/help index 81053d68b..4d150b5ec 100644 --- a/gcloud/alpha/dataproc/workflow-templates/help +++ b/gcloud/alpha/dataproc/workflow-templates/help @@ -48,8 +48,7 @@ EXAMPLES To update cluster selector in a workflow template, run: $ gcloud alpha dataproc workflow-templates set-cluster-selector \ - my_template \ - --cluster-labels environment=prod + my_template --cluster-labels environment=prod GCLOUD WIDE FLAGS These flags are available to all commands: --help. diff --git a/gcloud/alpha/deploy/delivery-pipelines/add-iam-policy-binding b/gcloud/alpha/deploy/delivery-pipelines/add-iam-policy-binding index 548e1f652..bc2f740b3 100644 --- a/gcloud/alpha/deploy/delivery-pipelines/add-iam-policy-binding +++ b/gcloud/alpha/deploy/delivery-pipelines/add-iam-policy-binding @@ -21,10 +21,9 @@ EXAMPLES 'us-central1', run: $ gcloud alpha deploy delivery-pipelines add-iam-policy-binding \ - my-pipeline \ - --region='us-central1' \ - --member='user:test-user@gmail.com' \ - --role='roles/clouddeploy.operator' + my-pipeline --region='us-central1' \ + --member='user:test-user@gmail.com' \ + --role='roles/clouddeploy.operator' POSITIONAL ARGUMENTS Delivery pipeline resource - The delivery pipeline for which to add the diff --git a/gcloud/alpha/deploy/delivery-pipelines/remove-iam-policy-binding b/gcloud/alpha/deploy/delivery-pipelines/remove-iam-policy-binding index 56a355885..dc53e3300 100644 --- a/gcloud/alpha/deploy/delivery-pipelines/remove-iam-policy-binding +++ b/gcloud/alpha/deploy/delivery-pipelines/remove-iam-policy-binding @@ -21,10 +21,9 @@ EXAMPLES 'my-pipeline' with the region 'us-central1', run: $ gcloud alpha deploy delivery-pipelines remove-iam-policy-binding \ - my-pipeline \ - --region='us-central1' \ - --member='user:test-user@gmail.com' \ - --role='roles/clouddeploy.operator' + my-pipeline --region='us-central1' \ + --member='user:test-user@gmail.com' \ + --role='roles/clouddeploy.operator' POSITIONAL ARGUMENTS Delivery pipeline resource - The delivery pipeline for which to remove the diff --git a/gcloud/alpha/deploy/targets/add-iam-policy-binding b/gcloud/alpha/deploy/targets/add-iam-policy-binding index 4d159778d..bc040b48d 100644 --- a/gcloud/alpha/deploy/targets/add-iam-policy-binding +++ b/gcloud/alpha/deploy/targets/add-iam-policy-binding @@ -21,9 +21,8 @@ EXAMPLES 'us-central1', run: $ gcloud alpha deploy targets add-iam-policy-binding my-target \ - --region='us-central1' \ - --member='user:test-user@gmail.com' \ - --role='roles/clouddeploy.operator' + --region='us-central1' --member='user:test-user@gmail.com' \ + --role='roles/clouddeploy.operator' POSITIONAL ARGUMENTS Target resource - The target for which to add the IAM policy binding. The diff --git a/gcloud/alpha/deploy/targets/remove-iam-policy-binding b/gcloud/alpha/deploy/targets/remove-iam-policy-binding index be7a8d892..1155304b5 100644 --- a/gcloud/alpha/deploy/targets/remove-iam-policy-binding +++ b/gcloud/alpha/deploy/targets/remove-iam-policy-binding @@ -21,9 +21,8 @@ EXAMPLES 'my-target' with the region 'us-central1', run: $ gcloud alpha deploy targets remove-iam-policy-binding my-target \ - --region='us-central1' \ - --member='user:test-user@gmail.com' \ - --role='roles/clouddeploy.operator' + --region='us-central1' --member='user:test-user@gmail.com' \ + --role='roles/clouddeploy.operator' POSITIONAL ARGUMENTS Target resource - The target for which to remove the IAM policy binding. diff --git a/gcloud/alpha/deployment-manager/deployments/create b/gcloud/alpha/deployment-manager/deployments/create index 8b9fd0764..dcf2d6f75 100644 --- a/gcloud/alpha/deployment-manager/deployments/create +++ b/gcloud/alpha/deployment-manager/deployments/create @@ -22,14 +22,14 @@ EXAMPLES To create a new deployment from a top-level template file, run: - $ gcloud deployment-manager deployments create my-deployment \ - --template=template.{jinja|py} \ + $ gcloud deployment-manager deployments create my-deployment \ + --template=template.{jinja|py} \ --properties="string-key:'string-value',integer-key:12345" To create a new deployment directly from a composite type, run: - $ gcloud deployment-manager deployments create my-deployment \ - --composite-type=/composite: \ + $ gcloud deployment-manager deployments create my-deployment \ + --composite-type=/composite: \ --properties="string-key:'string-value',integer-key:12345" To preview a deployment without actually creating resources, run: diff --git a/gcloud/alpha/dialogflow/intents/create b/gcloud/alpha/dialogflow/intents/create index afb6f98b4..da2d310fd 100644 --- a/gcloud/alpha/dialogflow/intents/create +++ b/gcloud/alpha/dialogflow/intents/create @@ -17,8 +17,8 @@ EXAMPLES $ gcloud alpha dialogflow intents create \ --display-name="test-intent" --priority=1 \ - --training-phrases="example query" - --responses="example response" + --training-phrases="example query" \ + --responses="example response" REQUIRED FLAGS --display-name=DISPLAY_NAME diff --git a/gcloud/alpha/dlp/datasources/bigquery/analyze b/gcloud/alpha/dlp/datasources/bigquery/analyze index 77889c7b7..57cc29e15 100644 --- a/gcloud/alpha/dlp/datasources/bigquery/analyze +++ b/gcloud/alpha/dlp/datasources/bigquery/analyze @@ -20,7 +20,7 @@ EXAMPLES To create a job my-bq-analysis to analyze records in a BigQuery table myproject.myds.mytable, run: - $ gcloud alpha dlp datasources bigquery analyze \ + $ gcloud alpha dlp datasources bigquery analyze \ `myproject.myds.mytable` --job-id my-ds-job \ --output-topics my-topic --numerical-stat-field col2 diff --git a/gcloud/alpha/dlp/datasources/bigquery/inspect b/gcloud/alpha/dlp/datasources/bigquery/inspect index bfab9539c..8383f2f94 100644 --- a/gcloud/alpha/dlp/datasources/bigquery/inspect +++ b/gcloud/alpha/dlp/datasources/bigquery/inspect @@ -24,7 +24,7 @@ EXAMPLES The following command creates a job my-bq-job to scan records in BigQuery table myproject.myds.mytable: - $ gcloud alpha dlp datasources bigquery inspect \ + $ gcloud alpha dlp datasources bigquery inspect \ `myproject.myds.mytable` --job-id my-ds-job \ --min-time '2018-01-01T12:00:00Z' \ --max-time '2018-01-31T12:00:00Z' --output-topics my-topic \ diff --git a/gcloud/alpha/dlp/datasources/datastore/inspect b/gcloud/alpha/dlp/datasources/datastore/inspect index 52d14c178..544ba5387 100644 --- a/gcloud/alpha/dlp/datasources/datastore/inspect +++ b/gcloud/alpha/dlp/datasources/datastore/inspect @@ -23,7 +23,7 @@ EXAMPLES The following command creates a job my-ds-job to scan records in Cloud Datastore table myds:mykind: - $ gcloud alpha dlp datasources datastore inspect `myds:mykind` \ + $ gcloud alpha dlp datasources datastore inspect `myds:mykind` \ --job-id my-ds-job --min-time '2018-01-01T12:00:00Z' \ --max-time '2018-01-31T12:00:00Z' --output-topics my-topic \ --max-findings-per-item 3 --max-findings 1000 \ diff --git a/gcloud/alpha/dlp/datasources/gcs/inspect b/gcloud/alpha/dlp/datasources/gcs/inspect index 070d3ea6d..c3cae9b1d 100644 --- a/gcloud/alpha/dlp/datasources/gcs/inspect +++ b/gcloud/alpha/dlp/datasources/gcs/inspect @@ -24,7 +24,7 @@ EXAMPLES The following command creates a job my-gcs-job to scan files in the Google Cloud Storage path gs://testproject/dlp/*: - $ gcloud alpha dlp datasources gcs inspect \ + $ gcloud alpha dlp datasources gcs inspect \ `gs://testproject/dlp/*` --job-id my-gcs-job \ --file-size-limit 10000 --min-time '2018-01-01T12:00:00Z' \ --max-time '2018-01-31T12:00:00Z' --output-topics my-topic \ diff --git a/gcloud/alpha/dlp/images/redact b/gcloud/alpha/dlp/images/redact index 86926011f..bb0367623 100644 --- a/gcloud/alpha/dlp/images/redact +++ b/gcloud/alpha/dlp/images/redact @@ -17,8 +17,7 @@ EXAMPLES redacted image to my-redacted-image.jpg, run: $ gcloud alpha dlp images redact my-image.jpg \ - --info-types PHONE_NUMBER \ - --output-file my-redacted-image.jpg + --info-types PHONE_NUMBER --output-file my-redacted-image.jpg POSITIONAL ARGUMENTS IMAGE diff --git a/gcloud/alpha/dlp/text/redact b/gcloud/alpha/dlp/text/redact index cf523f02f..61151c3cd 100644 --- a/gcloud/alpha/dlp/text/redact +++ b/gcloud/alpha/dlp/text/redact @@ -18,8 +18,8 @@ EXAMPLES redacted contents to my-redacted-data.csv, run: $ gcloud alpha dlp text redact --info-types EMAIL_ADDRESS \ - --replace-with-info-type \ - --content-file my-data.csv --output-file my-redacted-data.csv + --replace-with-info-type --content-file my-data.csv \ + --output-file my-redacted-data.csv REQUIRED FLAGS --info-types=[INFOTYPE,...] diff --git a/gcloud/alpha/dns/dns-keys/list b/gcloud/alpha/dns/dns-keys/list index bf87f65e1..5477f2aa0 100644 --- a/gcloud/alpha/dns/dns-keys/list +++ b/gcloud/alpha/dns/dns-keys/list @@ -16,8 +16,7 @@ EXAMPLES To see the DS records for every key-signing DnsKey in a managed zone, run: $ gcloud alpha dns dns-keys list --zone=my_zone 3 \ - --format='value(ds_record())' \ - --filter='type=keySigning' + --format='value(ds_record())' --filter='type=keySigning' REQUIRED FLAGS --zone=ZONE, -z ZONE diff --git a/gcloud/alpha/dns/managed-zones/create b/gcloud/alpha/dns/managed-zones/create index 929bb9061..f64a3d5ed 100644 --- a/gcloud/alpha/dns/managed-zones/create +++ b/gcloud/alpha/dns/managed-zones/create @@ -28,17 +28,14 @@ EXAMPLES To create a managed-zone with DNSSEC, run: $ gcloud alpha dns managed-zones create my-zone-2 \ - --description="Signed Zone" \ - --dns-name=myzone.example \ + --description="Signed Zone" --dns-name=myzone.example \ --dnssec-state=on To create a zonal managed-zone scoped to a GKE Cluster in us-east1-a, run: $ gcloud alpha dns managed-zones create my-zonal-zone \ - --description="Signed Zone" \ - --dns-name=cluster.local - --visibiilty=private - --gkeclusters=cluster1 + --description="Signed Zone" --dns-name=cluster.local \ + --visibiilty=private --gkeclusters=cluster1 \ --location=us-east1-a POSITIONAL ARGUMENTS diff --git a/gcloud/alpha/dns/policies/create b/gcloud/alpha/dns/policies/create index e3ce01305..acc52eb00 100644 --- a/gcloud/alpha/dns/policies/create +++ b/gcloud/alpha/dns/policies/create @@ -16,18 +16,16 @@ EXAMPLES To create a new policy with minimal arguments, run: $ gcloud alpha dns policies create mypolicy \ - --description='My new policy test policy 5' \ - --networks='' + --description='My new policy test policy 5' --networks='' To create a new policy with all optional arguments, run: $ gcloud alpha dns policies create mypolicy \ - --description='My new policy test policy 5' \ - --networks=network1,network2 \ - --alternative-name-servers=192.168.1.1,192.168.1.2 \ - --private-alternative-name-servers=100.64.0.1 \ - --enable-inbound-forwarding \ - --enable-logging + --description='My new policy test policy 5' \ + --networks=network1,network2 \ + --alternative-name-servers=192.168.1.1,192.168.1.2 \ + --private-alternative-name-servers=100.64.0.1 \ + --enable-inbound-forwarding --enable-logging POSITIONAL ARGUMENTS Policy resource - The policy to create. This represents a Cloud resource. diff --git a/gcloud/alpha/dns/record-sets/create b/gcloud/alpha/dns/record-sets/create index f60028ff1..b3c78e63c 100644 --- a/gcloud/alpha/dns/record-sets/create +++ b/gcloud/alpha/dns/record-sets/create @@ -18,15 +18,14 @@ EXAMPLES [1.2.3.4, 9.8.7.6] and ttl 60 in my_zone run this: $ gcloud alpha dns record-sets create foo.bar.com. \ - --rrdatas=1.2.3.4,9.8.7.6 --type=A --ttl=60 - --zone=my_zone + --rrdatas=1.2.3.4,9.8.7.6 --type=A --ttl=60 --zone=my_zone To create a record-set with dnsName foo.bar.com., record type A, rrdata [1.2.3.4, 9.8.7.6] and ttl 60 in my_zone in us-east1-a run this: $ gcloud alpha dns record-sets create us-east1-a.bar.com. \ - --rrdatas=1.2.3.4,9.8.7.6 --type=A --ttl=60 - --zone=my_zone --location=us-east1-a + --rrdatas=1.2.3.4,9.8.7.6 --type=A --ttl=60 --zone=my_zone \ + --location=us-east1-a POSITIONAL ARGUMENTS DNS_NAME diff --git a/gcloud/alpha/dns/record-sets/export b/gcloud/alpha/dns/record-sets/export index a5347bde8..b9eb5c064 100644 --- a/gcloud/alpha/dns/record-sets/export +++ b/gcloud/alpha/dns/record-sets/export @@ -24,7 +24,7 @@ EXAMPLES Similarly, to import record-sets into a BIND zone formatted zone file, run: $ gcloud dns record-sets import pathto.zonefile --zone-file-format \ - --zone=examplezonename + --zone=examplezonename POSITIONAL ARGUMENTS RECORDS_FILE diff --git a/gcloud/alpha/dns/record-sets/transaction/add b/gcloud/alpha/dns/record-sets/transaction/add index 0b0eb9e70..9e7afd400 100644 --- a/gcloud/alpha/dns/record-sets/transaction/add +++ b/gcloud/alpha/dns/record-sets/transaction/add @@ -19,16 +19,14 @@ EXAMPLES "my.domain.", and a managed zone "MANAGED_ZONE", run: $ gcloud alpha dns record-sets transaction add "1.2.3.4" \ - --name=my.domain. --ttl=1234 \ - --type=A --zone=MANAGED_ZONE + --name=my.domain. --ttl=1234 --type=A --zone=MANAGED_ZONE To add a TXT record with multiple data values while specifying time to live as 14400 seconds, run: $ gcloud alpha dns record-sets transaction add "Hello world" \ - "Bye world" \ - --name=my.domain. --ttl=14400 \ - --type=TXT --zone=MANAGED_ZONE + "Bye world" --name=my.domain. --ttl=14400 --type=TXT \ + --zone=MANAGED_ZONE POSITIONAL ARGUMENTS RRDATAS [RRDATAS ...] diff --git a/gcloud/alpha/dns/record-sets/transaction/remove b/gcloud/alpha/dns/record-sets/transaction/remove index 4d02e5641..f80c24416 100644 --- a/gcloud/alpha/dns/record-sets/transaction/remove +++ b/gcloud/alpha/dns/record-sets/transaction/remove @@ -15,14 +15,14 @@ EXAMPLES To remove an A record, run: $ gcloud alpha dns record-sets transaction remove \ - --zone=MANAGED_ZONE --name=my.domain. --ttl=1234 \ - --type=A "1.2.3.4" + --zone=MANAGED_ZONE --name=my.domain. --ttl=1234 --type=A \ + "1.2.3.4" To remove a TXT record with multiple data values, run: $ gcloud alpha dns record-sets transaction remove \ - --zone=MANAGED_ZONE --name=my.domain. --ttl=2345 \ - --type=TXT "Hello world" "Bye world" + --zone=MANAGED_ZONE --name=my.domain. --ttl=2345 --type=TXT \ + "Hello world" "Bye world" POSITIONAL ARGUMENTS RRDATAS [RRDATAS ...] diff --git a/gcloud/alpha/dns/record-sets/update b/gcloud/alpha/dns/record-sets/update index c7268fcf3..13f563416 100644 --- a/gcloud/alpha/dns/record-sets/update +++ b/gcloud/alpha/dns/record-sets/update @@ -18,16 +18,15 @@ EXAMPLES rrdata [1.2.3.4, 9.8.7.6] and ttl 60 in my_zone, run: $ gcloud alpha dns record-sets update foo.bar.com. \ - --rrdatas=1.2.3.4,9.8.7.6 --type=A --ttl=60 - --zone=my_zone + --rrdatas=1.2.3.4,9.8.7.6 --type=A --ttl=60 --zone=my_zone To update a record-set with dnsName foo.bar.com., record type A to have rrdata [1.2.3.4, 9.8.7.6] and ttl 60 in my_zone that locates in us-east1-a, run: $ gcloud alpha dns record-sets update foo.bar.com. \ - --rrdatas=1.2.3.4,9.8.7.6 --type=A --ttl=60 - --zone=my_zone --location=us-east1-a + --rrdatas=1.2.3.4,9.8.7.6 --type=A --ttl=60 --zone=my_zone \ + --location=us-east1-a POSITIONAL ARGUMENTS DNS_NAME diff --git a/gcloud/alpha/dns/response-policies/create b/gcloud/alpha/dns/response-policies/create index d5b40edf0..b4f3d445a 100644 --- a/gcloud/alpha/dns/response-policies/create +++ b/gcloud/alpha/dns/response-policies/create @@ -15,21 +15,19 @@ EXAMPLES To create a new response policy with minimal arguments, run: $ gcloud alpha dns response-policies create myresponsepolicy \ - --description='My new response policy.' - --networks='' + --description='My new response policy.' --networks='' To create a new response policy with all optional arguments, run: $ gcloud alpha dns response-policies create myresponsepolicy \ - --description='My new response policy.' - --networks=network1,network2 + --description='My new response policy.' \ + --networks=network1,network2 To create a new zonal response policy scoped to a GKE cluster in us-central1-a, run (alpha/beta): $ gcloud alpha dns response-policies create beta myresponsepolicy \ --description='My new response - policy.' - --gkeclusters=cluster1 --location=us-central1-a + policy.' --gkeclusters=cluster1 --location=us-central1-a POSITIONAL ARGUMENTS Response policy resource - The response policy to create. This represents diff --git a/gcloud/alpha/dns/response-policies/rules/create b/gcloud/alpha/dns/response-policies/rules/create index d68255062..b3b8a11dc 100644 --- a/gcloud/alpha/dns/response-policies/rules/create +++ b/gcloud/alpha/dns/response-policies/rules/create @@ -13,23 +13,24 @@ EXAMPLES To create a new response policy rule with local data rrsets, run: $ gcloud alpha dns response-policies rules create \ - myresponsepolicyrule --response-policy="myresponsepolicy" - --dns-name="www.zone.com." - --local-data=name=www.zone.com.,type=CNAME,ttl=21600,rrdatas=zone.com. + myresponsepolicyrule --response-policy="myresponsepolicy" \ + --dns-name="www.zone.com." \ + --local-data=name=www.zone.com.,type=CNAME,ttl=21600,\ + rrdatas=zone.com. To create a new response policy rule with behavior, run: $ gcloud alpha dns response-policies rules create \ - myresponsepolicyrule --response-policy="myresponsepolicy" - --dns-name="www.zone.com." --behavior=bypassResponsePolicy + myresponsepolicyrule --response-policy="myresponsepolicy" \ + --dns-name="www.zone.com." --behavior=bypassResponsePolicy To create a new response policy rule with behavior in a zonal response policy in us-east1-a, run: $ gcloud alpha dns response-policies rules create \ - myresponsepolicyrule --response-policy="myresponsepolicy" - --dns-name="www.zone.com." --behavior=bypassResponsePolicy - --location=us-east1-a + myresponsepolicyrule --response-policy="myresponsepolicy" \ + --dns-name="www.zone.com." --behavior=bypassResponsePolicy \ + --location=us-east1-a POSITIONAL ARGUMENTS Response policy rule resource - The response policy rule to create. The diff --git a/gcloud/alpha/dns/response-policies/rules/help b/gcloud/alpha/dns/response-policies/rules/help index 1f4647ff8..f1a45ea54 100644 --- a/gcloud/alpha/dns/response-policies/rules/help +++ b/gcloud/alpha/dns/response-policies/rules/help @@ -9,27 +9,28 @@ EXAMPLES To create a new response policy rule with local data rrsets, run: $ gcloud alpha dns response-policies rules myresponsepolicyrule \ - --response-policy="myresponsepolicy" - --dns-name="www.zone.com." - --local-data=name=www.zone.com.,type=CNAME,ttl=21600,rrdatas=zone.com. + --response-policy="myresponsepolicy" \ + --dns-name="www.zone.com." \ + --local-data=name=www.zone.com.,type=CNAME,ttl=21600,\ + rrdatas=zone.com. To create a new response policy rule with behavior, run: $ gcloud alpha dns response-policies rules myresponsepolicyrule \ - --response-policy="myresponsepolicy" - --dns-name="www.zone.com." --behavior=bypassResponsePolicy + --response-policy="myresponsepolicy" \ + --dns-name="www.zone.com." --behavior=bypassResponsePolicy To update a new response policy rule with local data rrsets, run: $ gcloud alpha dns response-policies rules myresponsepolicyrule \ - --response-policy="myresponsepolicy" - --local-data=name=www.zone.com.,type=A,ttl=21600,rrdatas=1.2.3.4 + --response-policy="myresponsepolicy" \ + --local-data=name=www.zone.com.,type=A,ttl=21600,rrdatas=1.2.3.4 To update a new response policy rule with behavior, run: $ gcloud alpha dns response-policies rules myresponsepolicyrule \ - --response-policy="myresponsepolicy" - --behavior=bypassResponsePolicy + --response-policy="myresponsepolicy" \ + --behavior=bypassResponsePolicy GCLOUD WIDE FLAGS These flags are available to all commands: --help. diff --git a/gcloud/alpha/dns/response-policies/rules/update b/gcloud/alpha/dns/response-policies/rules/update index 90045a76b..d0b08ae4c 100644 --- a/gcloud/alpha/dns/response-policies/rules/update +++ b/gcloud/alpha/dns/response-policies/rules/update @@ -16,20 +16,20 @@ EXAMPLES To update a new response policy rule with DNS name, run: $ gcloud alpha dns response-policies rules update \ - myresponsepolicyrule --response-policy="myresponsepolicy" - --dns-name="www.newzone.com." # pylint: disable=line-too-long + myresponsepolicyrule --response-policy="myresponsepolicy" \ + --dns-name="www.newzone.com." # pylint: disable=line-too-long To update a new response policy rule with local data rrsets, run: $ gcloud alpha dns response-policies rules update \ - myresponsepolicyrule --response-policy="myresponsepolicy" - --local-data=name=www.zone.com.,type=A,ttl=21600,rrdatas=1.2.3.4 + myresponsepolicyrule --response-policy="myresponsepolicy" \ + --local-data=name=www.zone.com.,type=A,ttl=21600,rrdatas=1.2.3.4 To update a new response policy rule with behavior, run: $ gcloud alpha dns response-policies rules update \ - myresponsepolicyrule --response-policy="myresponsepolicy" - --behavior=bypassResponsePolicy + myresponsepolicyrule --response-policy="myresponsepolicy" \ + --behavior=bypassResponsePolicy POSITIONAL ARGUMENTS Response policy rule resource - The response policy rule to update. The diff --git a/gcloud/alpha/dns/response-policies/update b/gcloud/alpha/dns/response-policies/update index da14f8a2e..56a45b2b6 100644 --- a/gcloud/alpha/dns/response-policies/update +++ b/gcloud/alpha/dns/response-policies/update @@ -15,21 +15,20 @@ EXAMPLES To update a response policy with minimal arguments, run: $ gcloud alpha dns response-policies update myresponsepolicy \ - --description='My updated response policy.' - --networks='' + --description='My updated response policy.' --networks='' To update a response policy with all optional arguments, run: $ gcloud alpha dns response-policies update myresponsepolicy \ - --description='My updated response policy.' - --networks=network1,network2 + --description='My updated response policy.' \ + --networks=network1,network2 To update a new zonal response policy scoped to a GKE cluster in us-central1-a, run: $ gcloud alpha dns response-policies update myresponsepolicy \ - --description='My new response policy.' - --gkeclusters=cluster1 --location=us-central1-a + --description='My new response policy.' --gkeclusters=cluster1 \ + --location=us-central1-a POSITIONAL ARGUMENTS Response policy resource - The response policy to update. This represents diff --git a/gcloud/alpha/endpoints/quota/create b/gcloud/alpha/endpoints/quota/create index 4c9906b95..ac5b38733 100644 --- a/gcloud/alpha/endpoints/quota/create +++ b/gcloud/alpha/endpoints/quota/create @@ -15,31 +15,31 @@ EXAMPLES To create a quota override for a project with project number, run: $ gcloud alpha endpoints quota create \ - --service=example.googleapis.com --consumer=projects/12321 - --metric=example.googleapis.com/default_requests - --unit=1/min/{project} --value=360 + --service=example.googleapis.com --consumer=projects/12321 \ + --metric=example.googleapis.com/default_requests \ + --unit=1/min/{project} --value=360 To create a quota override for a project with project ID, run: $ gcloud alpha endpoints quota create \ - --service=example.googleapis.com --consumer=projects/hello - --metric=example.googleapis.com/default_requests - --unit=1/min/{project} --value=360 + --service=example.googleapis.com --consumer=projects/hello \ + --metric=example.googleapis.com/default_requests \ + --unit=1/min/{project} --value=360 To create a quota override for an organization, run: $ gcloud alpha endpoints quota create \ - --service=example.googleapis.com --consumer=organizations/555 - --metric=example.googleapis.com/default_requests - --unit=1/min/{project} --value=360 + --service=example.googleapis.com --consumer=organizations/555 \ + --metric=example.googleapis.com/default_requests \ + --unit=1/min/{project} --value=360 To force the creation of a quota override with dimensions, run: $ gcloud alpha endpoints quota create \ - --service=example.googleapis.com --consumer=projects/12321 - metric=example.googleapis.com/default_requests - --unit=1/min/{project} --dimensions=regions=us-central1 - --dimensions=zones=us-central1-c --value=360 --force + --service=example.googleapis.com --consumer=projects/12321 \ + metric=example.googleapis.com/default_requests \ + --unit=1/min/{project} --dimensions=regions=us-central1 \ + --dimensions=zones=us-central1-c --value=360 --force REQUIRED FLAGS --consumer=CONSUMER diff --git a/gcloud/alpha/endpoints/quota/delete b/gcloud/alpha/endpoints/quota/delete index 423cf753c..ee0b4c38b 100644 --- a/gcloud/alpha/endpoints/quota/delete +++ b/gcloud/alpha/endpoints/quota/delete @@ -16,30 +16,30 @@ EXAMPLES To delete a quota override for a project with project number, run: $ gcloud alpha endpoints quota delete \ - --service=example.googleapis.com --consumer=projects/12321 - --metric=example.googleapis.com/default_requests - --unit=1/min/{project} + --service=example.googleapis.com --consumer=projects/12321 \ + --metric=example.googleapis.com/default_requests \ + --unit=1/min/{project} To delete a quota override for a project with project ID, run: $ gcloud alpha endpoints quota delete \ - --service=example.googleapis.com --consumer=projects/hello - --metric=example.googleapis.com/default_requests - --unit=1/min/{project} + --service=example.googleapis.com --consumer=projects/hello \ + --metric=example.googleapis.com/default_requests \ + --unit=1/min/{project} To delete a quota override for an organization, run: $ gcloud alpha endpoints quota delete \ - --service=example.googleapis.com --consumer=organizations/555 - --metric=example.googleapis.com/default_requests - --unit=1/min/{project} + --service=example.googleapis.com --consumer=organizations/555 \ + --metric=example.googleapis.com/default_requests \ + --unit=1/min/{project} To force the deletion of a quota override, run: $ gcloud alpha endpoints quota delete \ - --service=example.googleapis.com --consumer=projects/12321 - --metric=example.googleapis.com/default_requests - --unit=1/min/{project} --force + --service=example.googleapis.com --consumer=projects/12321 \ + --metric=example.googleapis.com/default_requests \ + --unit=1/min/{project} --force REQUIRED FLAGS --consumer=CONSUMER diff --git a/gcloud/alpha/endpoints/quota/update b/gcloud/alpha/endpoints/quota/update index c792c6213..71d8a4c60 100644 --- a/gcloud/alpha/endpoints/quota/update +++ b/gcloud/alpha/endpoints/quota/update @@ -16,32 +16,32 @@ EXAMPLES To update a quota override for project with project number, run: $ gcloud alpha endpoints quota update \ - --service=example.googleapis.com --consumer=projects/12321 - --metric=example.googleapis.com/default_requests - --unit=1/min/{project} --override-id=hello123 --value=360 + --service=example.googleapis.com --consumer=projects/12321 \ + --metric=example.googleapis.com/default_requests \ + --unit=1/min/{project} --override-id=hello123 --value=360 To update a quota override for project with project ID, run: $ gcloud alpha endpoints quota update \ - --service=example.googleapis.com --consumer=projects/hello - --metric=example.googleapis.com/default_requests - --unit=1/min/{project} --override-id=hello123 --value=360 + --service=example.googleapis.com --consumer=projects/hello \ + --metric=example.googleapis.com/default_requests \ + --unit=1/min/{project} --override-id=hello123 --value=360 To update a quota override for an organization, run: $ gcloud alpha endpoints quota update \ - --service=example.googleapis.com --consumer=organizations/555 - --metric=example.googleapis.com/default_requests - --unit=1/min/{project} --override-id=hello123 --value=360 + --service=example.googleapis.com --consumer=organizations/555 \ + --metric=example.googleapis.com/default_requests \ + --unit=1/min/{project} --override-id=hello123 --value=360 To force the update of a quota override, run: $ gcloud alpha endpoints quota update \ - --service=example.googleapis.com --consumer=projects/12321 - --metric=example.googleapis.com/default_requests - --unit=1/min/{project} --override-id=hello123 - --dimensions=regions=us-central1 - --dimensions=zones=us-central1-c --value=360 --force + --service=example.googleapis.com --consumer=projects/12321 \ + --metric=example.googleapis.com/default_requests \ + --unit=1/min/{project} --override-id=hello123 \ + --dimensions=regions=us-central1 \ + --dimensions=zones=us-central1-c --value=360 --force REQUIRED FLAGS --consumer=CONSUMER diff --git a/gcloud/alpha/endpoints/services/add-iam-policy-binding b/gcloud/alpha/endpoints/services/add-iam-policy-binding index 7ef794aa1..f9b45bde0 100644 --- a/gcloud/alpha/endpoints/services/add-iam-policy-binding +++ b/gcloud/alpha/endpoints/services/add-iam-policy-binding @@ -29,9 +29,10 @@ EXAMPLES 'my-iam-account@my-project.iam.gserviceaccount.com' on the service 'my-service', run: - $ gcloud alpha endpoints services add-iam-policy-binding my-service \ - --member='serviceAccount:my-iam-account@my-project.iam.gserviceaccount.com' \ - --role='roles/servicemanagement.serviceConsumer' + $ gcloud alpha endpoints services add-iam-policy-binding \ + my-service \ + --member='serviceAccount:my-iam-account@my-project.iam.gservicea\ + ccount.com' --role='roles/servicemanagement.serviceConsumer' To add an IAM policy binding which expires at the end of the year 2018 for the role of 'roles/servicemanagement.quotaAdmin' and the user diff --git a/gcloud/alpha/essential-contacts/compute b/gcloud/alpha/essential-contacts/compute index e0504867a..915b3afb8 100644 --- a/gcloud/alpha/essential-contacts/compute +++ b/gcloud/alpha/essential-contacts/compute @@ -26,8 +26,7 @@ EXAMPLES for the folder with id 123, run: $ gcloud alpha essential-contacts compute \ - --notification-categories=product-updates,billing - --folder=123 + --notification-categories=product-updates,billing --folder=123 To compute contacts subscribed to the legal category for the organization with id 456, run: diff --git a/gcloud/alpha/essential-contacts/create b/gcloud/alpha/essential-contacts/create index 17b4d4b3b..3f301ce19 100644 --- a/gcloud/alpha/essential-contacts/create +++ b/gcloud/alpha/essential-contacts/create @@ -11,22 +11,23 @@ EXAMPLES To create a contact in the current project, run: $ gcloud alpha essential-contacts create \ - --email=contact-email@example.com - --notification-categories=technical,product-updates --language=en-US + --email=contact-email@example.com \ + --notification-categories=technical,product-updates \ + --language=en-US To create a contact in the folder with id 456, run: $ gcloud alpha essential-contacts create \ - --email=contact-email@example.com - --notification-categories=technical,product-updates --language=en-US - --folder=456 + --email=contact-email@example.com \ + --notification-categories=technical,product-updates \ + --language=en-US --folder=456 To create a contact in the organization with id 456, run: $ gcloud alpha essential-contacts create \ - --email=contact-email@example.com - --notification-categories=technical,product-updates --language=en-US - --organization=456 + --email=contact-email@example.com \ + --notification-categories=technical,product-updates \ + --language=en-US --organization=456 REQUIRED FLAGS --email=EMAIL diff --git a/gcloud/alpha/essential-contacts/update b/gcloud/alpha/essential-contacts/update index 4cadbdf12..96ea136a5 100644 --- a/gcloud/alpha/essential-contacts/update +++ b/gcloud/alpha/essential-contacts/update @@ -24,7 +24,7 @@ EXAMPLES for the contact with id 123 in the organization with id 456, run: $ gcloud alpha essential-contacts update 123 \ - --notification-categories=legal --language=en-US + --notification-categories=legal --language=en-US \ --organization=456 POSITIONAL ARGUMENTS diff --git a/gcloud/alpha/filestore/instances/create b/gcloud/alpha/filestore/instances/create index 34b9bca79..e31a2323f 100644 --- a/gcloud/alpha/filestore/instances/create +++ b/gcloud/alpha/filestore/instances/create @@ -21,12 +21,12 @@ EXAMPLES The following command creates a Filestore instance named NAME with a single volume. - $ gcloud alpha filestore instances create NAME \ - --description=DESCRIPTION --tier=TIER \ - --file-share=name=VOLUME_NAME,capacity=CAPACITY \ + $ gcloud alpha filestore instances create NAME \ + --description=DESCRIPTION --tier=TIER \ + --file-share=name=VOLUME_NAME,capacity=CAPACITY \ --network=name=NETWORK_NAME,\ - reserved-ip-range=RESERVED_IP_RANGE,connect-mode=CONNECT_MODE \ - --zone=ZONE --flags-file=FLAGS_FILE + reserved-ip-range=RESERVED_IP_RANGE,connect-mode=CONNECT_MODE \ + --zone=ZONE --flags-file=FLAGS_FILE Example json configuration file: { "--file-share": { "capacity": "61440", diff --git a/gcloud/alpha/filestore/instances/restore b/gcloud/alpha/filestore/instances/restore index c4bb7605e..2b629be74 100644 --- a/gcloud/alpha/filestore/instances/restore +++ b/gcloud/alpha/filestore/instances/restore @@ -21,10 +21,8 @@ EXAMPLES 'my-backup' in the region europe-west3. $ gcloud alpha filestore instances restore my-instance \ - --zone=europe-west3-a \ - --file-share=vol1 \ - --source-backup=my-backup \ - --source-backup-region=europe-west3 + --zone=europe-west3-a --file-share=vol1 \ + --source-backup=my-backup --source-backup-region=europe-west3 POSITIONAL ARGUMENTS Instance resource - Arguments and flags that specify the Filestore diff --git a/gcloud/alpha/filestore/instances/update b/gcloud/alpha/filestore/instances/update index 8bde12df1..bd356e767 100644 --- a/gcloud/alpha/filestore/instances/update +++ b/gcloud/alpha/filestore/instances/update @@ -55,7 +55,7 @@ EXAMPLES capacity to CAPACITY. $ gcloud alpha filestore instances update NAME \ - --project=PROJECT_ID --zone=ZONE \ + --project=PROJECT_ID --zone=ZONE \ --file-share=name=VOLUME_NAME,capacity=CAPACITY POSITIONAL ARGUMENTS diff --git a/gcloud/alpha/filestore/snapshots/create b/gcloud/alpha/filestore/snapshots/create index 280c5efb8..24b2c7de2 100644 --- a/gcloud/alpha/filestore/snapshots/create +++ b/gcloud/alpha/filestore/snapshots/create @@ -19,7 +19,7 @@ EXAMPLES run: $ gcloud alpha filestore snapshots create my-snapshot \ - --instance=my-instance --file-share=my-fs + --instance=my-instance --file-share=my-fs \ --instance-zone=us-central1-c To create a snapshot with the name 'my-snapshot' in a particular region @@ -27,7 +27,7 @@ EXAMPLES and the source file share called 'my-fs', run: $ gcloud alpha filestore snapshots create my-snapshot \ - --instance=my-instance --file-share=my-fs + --instance=my-instance --file-share=my-fs \ --instance-zone=us-central1-c --region=us-central1 POSITIONAL ARGUMENTS diff --git a/gcloud/alpha/firestore/indexes/fields/list b/gcloud/alpha/firestore/indexes/fields/list index e064a46d0..712f13cca 100644 --- a/gcloud/alpha/firestore/indexes/fields/list +++ b/gcloud/alpha/firestore/indexes/fields/list @@ -27,9 +27,10 @@ EXAMPLES The following command lists the indexes of all fields with custom index settings: - $ gcloud alpha firestore indexes fields list --format="table[box](\ - name,indexConfig.indexes:format='table[title=INDEXES,box](\ - fields.order.flatten(),fields.arrayConfig.flatten(),queryScope,state)')" + $ gcloud alpha firestore indexes fields list \ + --format="table[box](name,indexConfig.indexes:format='table[titl\ + e=INDEXES,box](fields.order.flatten(),fields.arrayConfig.flatten(),q\ + ueryScope,state)')" FLAGS Collection group resource - Collection group of the index. diff --git a/gcloud/alpha/firestore/indexes/fields/update b/gcloud/alpha/firestore/indexes/fields/update index f036e764f..025566b84 100644 --- a/gcloud/alpha/firestore/indexes/fields/update +++ b/gcloud/alpha/firestore/indexes/fields/update @@ -20,16 +20,14 @@ EXAMPLES Events collection group, in which all indexes are disabled: $ gcloud alpha firestore indexes fields update timestamp \ - --collection-group=Events - --disable-indexes + --collection-group=Events --disable-indexes The following command creates an exemption for the timestamp field in the Events collection group, in which the list of indexes is explicitly set to [ASCENDING, DESCENDING]: $ gcloud alpha firestore indexes fields update timestamp \ - --collection-group=Events \ - --index=order=ASCENDING \ + --collection-group=Events --index=order=ASCENDING \ --index=order=DESCENDING The following command clears the exemption on the timestamp field in the diff --git a/gcloud/alpha/functions/deploy b/gcloud/alpha/functions/deploy index cd40a54a7..f9d2b31e0 100644 --- a/gcloud/alpha/functions/deploy +++ b/gcloud/alpha/functions/deploy @@ -497,28 +497,27 @@ FLAGS We recommend referencing the latest version when using secret volumes so that the secret's value changes are reflected immediately. - Only `--update-secrets` and `--remove-secrets` can be used together. If - both are specified, then `--remove-secrets` will be applied first. + Only --update-secrets and --remove-secrets can be used together. If both + are specified, then --remove-secrets will be applied first. - --remove-secrets=[SECRET_ENV_VAR,/secret_path,/mount_path:/secret_file_path,...] - List of secret environment variable names and secret paths to - remove. + --remove-secrets=[SECRET_ENV_VAR,/secret_path,/mount_path:/secret_file_path,...] + List of secret environment variable names and secret paths to + remove. - Existing secrets configuration of secret environment variable - names and secret paths not specified in this list will be - preserved. + Existing secrets configuration of secret environment variable names + and secret paths not specified in this list will be preserved. - To remove a secret environment variable, use the name of the - environment variable SECRET_ENV_VAR. + To remove a secret environment variable, use the name of the + environment variable SECRET_ENV_VAR. - To remove a file within a secret volume or the volume itself, use - the secret path as the key (either /secret_path or - /mount_path:/secret_file_path). + To remove a file within a secret volume or the volume itself, use + the secret path as the key (either /secret_path or + /mount_path:/secret_file_path). - --update-secrets=[SECRET_ENV_VAR=SECRET_VALUE_REF,/secret_path=SECRET_VALUE_REF,/mount_path:/secret_file_path=SECRET_VALUE_REF,...] - List of secret environment variables and secret volumes to - update. Existing secrets configuration not specified in this list - will be preserved. + --update-secrets=[SECRET_ENV_VAR=SECRET_VALUE_REF,/secret_path=SECRET_VALUE_REF,/mount_path:/secret_file_path=SECRET_VALUE_REF,...] + List of secret environment variables and secret volumes to update. + Existing secrets configuration not specified in this list will be + preserved. At most one of these can be specified: diff --git a/gcloud/alpha/game/servers/clusters/create b/gcloud/alpha/game/servers/clusters/create index babe3fdce..a165ea66a 100644 --- a/gcloud/alpha/game/servers/clusters/create +++ b/gcloud/alpha/game/servers/clusters/create @@ -17,16 +17,18 @@ EXAMPLES $ gcloud alpha game servers clusters create my-cluster \ --project=my-project --realm=my-realm --location=my-location \ - --gke-cluster=projects/my-project/locations/my-location/clusters/my-gke-cluster \ - --namespace=default --labels=a=x,b=y --no-dry-run + --gke-cluster=projects/my-project/locations/my-location/\ + clusters/my-gke-cluster --namespace=default --labels=a=x,b=y \ + --no-dry-run To preview Game Server Cluster creation for 'my-cluster' in project 'my-project', realm 'my-realm', and location in 'my-location' run: $ gcloud alpha game servers clusters create my-cluster \ --project=my-project --realm=my-realm --location=my-location \ - --gke-cluster=projects/my-project/locations/my-location/clusters/my-gke-cluster \ - --namespace=default --labels=a=x,b=y --dry-run + --gke-cluster=projects/my-project/locations/my-location/\ + clusters/my-gke-cluster --namespace=default --labels=a=x,b=y \ + --dry-run POSITIONAL ARGUMENTS Game server cluster resource - Cloud Game Server Cluster to create. The diff --git a/gcloud/alpha/game/servers/clusters/update b/gcloud/alpha/game/servers/clusters/update index 65b5afbfd..5f60cf4c5 100644 --- a/gcloud/alpha/game/servers/clusters/update +++ b/gcloud/alpha/game/servers/clusters/update @@ -17,14 +17,14 @@ EXAMPLES $ gcloud alpha game servers clusters update my-cluster \ --project=my-project --realm=my-realm --location=my-location \ - --update-labels="key1=val1" --no-dry-run + --update-labels="key1=val1" --no-dry-run To preview Game Server Cluster label update for 'my-cluster' in project 'my-project', realm 'my-realm', and location in 'my-location' run: $ gcloud alpha game servers clusters update my-cluster \ --project=my-project --realm=my-realm --location=my-location \ - --update-labels="key1=val1" --dry-run + --update-labels="key1=val1" --dry-run POSITIONAL ARGUMENTS Game server cluster resource - Cloud Game Server Cluster to update. The diff --git a/gcloud/alpha/game/servers/configs/create b/gcloud/alpha/game/servers/configs/create index 44fe55c89..5752d079d 100644 --- a/gcloud/alpha/game/servers/configs/create +++ b/gcloud/alpha/game/servers/configs/create @@ -18,8 +18,8 @@ EXAMPLES $ gcloud alpha game servers configs create my-config \ --project=my-project --deployment=my-deployment \ - --location=global \ - --deployment=my-deployment --description=description --labels=a=x,b=y \ + --location=global --deployment=my-deployment \ + --description=description --labels=a=x,b=y \ --fleet-configs-file=fleet_configs.json POSITIONAL ARGUMENTS diff --git a/gcloud/alpha/game/servers/deployments/create b/gcloud/alpha/game/servers/deployments/create index f5e1ef180..a3ffd3c73 100644 --- a/gcloud/alpha/game/servers/deployments/create +++ b/gcloud/alpha/game/servers/deployments/create @@ -17,8 +17,7 @@ EXAMPLES $ gcloud alpha game servers deployments create my-deployment \ --project=my-project --location=global \ - --description=description \ - --labels=a=x,b=y + --description=description --labels=a=x,b=y POSITIONAL ARGUMENTS Deployment resource - Cloud Game Server Deployment to create. The diff --git a/gcloud/alpha/iam/list-grantable-roles b/gcloud/alpha/iam/list-grantable-roles index c6cff37f3..664947461 100644 --- a/gcloud/alpha/iam/list-grantable-roles +++ b/gcloud/alpha/iam/list-grantable-roles @@ -26,7 +26,8 @@ EXAMPLES List grantable roles for a resource identified via URI: $ gcloud alpha iam list-grantable-roles \ - https://www.googleapis.com/compute/v1/projects/example-project/zones/us-central1-f/instances/example-instance + https://www.googleapis.com/compute/v1/projects/example-project/\ + zones/us-central1-f/instances/example-instance POSITIONAL ARGUMENTS RESOURCE diff --git a/gcloud/alpha/iam/policies/create b/gcloud/alpha/iam/policies/create new file mode 100644 index 000000000..31cb25b57 --- /dev/null +++ b/gcloud/alpha/iam/policies/create @@ -0,0 +1,51 @@ +NAME + gcloud alpha iam policies create - create a policy on the given attachment + point with the given name + +SYNOPSIS + gcloud alpha iam policies create POLICY_ID + --attachment-point=ATTACHMENT_POINT --kind=KIND + --policy-file=POLICY_FILE [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Create a policy on the given attachment point with the given name. + +EXAMPLES + The following command creates the IAM policy defined at the resource + project 123 of kind denypolicies and id my-deny-policy from the file + policy.json: + + $ gcloud alpha iam policies create my-deny-policy \ + --attachment-point=cloudresourcemanager.googleapis.com/\ + projects/123 --kind=denypolicies --policy-file=policy.json + +POSITIONAL ARGUMENTS + POLICY_ID + Id of the policy. + +REQUIRED FLAGS + --attachment-point=ATTACHMENT_POINT + Resource to which the policy is attached. + + --kind=KIND + Kind of the policy. + + --policy-file=POLICY_FILE + Contents 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. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails 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 iam policies create + diff --git a/gcloud/alpha/iam/policies/delete b/gcloud/alpha/iam/policies/delete new file mode 100644 index 000000000..8aff974b6 --- /dev/null +++ b/gcloud/alpha/iam/policies/delete @@ -0,0 +1,54 @@ +NAME + gcloud alpha iam policies delete - delete a policy on the given attachment + point with the given name + +SYNOPSIS + gcloud alpha iam policies delete POLICY_ID + --attachment-point=ATTACHMENT_POINT --kind=KIND [--etag=ETAG] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Delete a policy on the given attachment point with the given name. + +EXAMPLES + The following command deletes the IAM policy defined at the resource + project 123 of kind denypolicies and id my-deny-policy, with etag abc: + + $ gcloud alpha iam policies delete my-deny-policy \ + --attachment-point=cloudresourcemanager.googleapis.com/\ + projects/123 --kind=denypolicies --etag=abc + + If etag isn't provided, the command will try to get the etag using the + calling user permissions. + +POSITIONAL ARGUMENTS + POLICY_ID + Id of the policy. + +REQUIRED FLAGS + --attachment-point=ATTACHMENT_POINT + Resource to which the policy is attached. + + --kind=KIND + Kind of the policy. + +OPTIONAL FLAGS + --etag=ETAG + Etag of the existing 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. This variant is also available: + + $ gcloud beta iam policies delete + diff --git a/gcloud/alpha/iam/policies/get b/gcloud/alpha/iam/policies/get new file mode 100644 index 000000000..c9666fcf2 --- /dev/null +++ b/gcloud/alpha/iam/policies/get @@ -0,0 +1,46 @@ +NAME + gcloud alpha iam policies get - get a policy on the given attachment point + with the given name + +SYNOPSIS + gcloud alpha iam policies get POLICY_ID --attachment-point=ATTACHMENT_POINT + --kind=KIND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Get a policy on the given attachment point with the given name. + +EXAMPLES + The following command gets the IAM policy defined at the resource project + 123 of kind denypolicies and id my-deny-policy: + + $ gcloud alpha iam policies get my-deny-policy \ + --attachment-point=cloudresourcemanager.googleapis.com/\ + projects/123 --kind=denypolicies + +POSITIONAL ARGUMENTS + POLICY_ID + Id of the policy. + +REQUIRED FLAGS + --attachment-point=ATTACHMENT_POINT + Resource to which the policy is attached. + + --kind=KIND + Kind 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. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails 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 iam policies get + diff --git a/gcloud/alpha/iam/policies/help b/gcloud/alpha/iam/policies/help index 84507d0f9..2135db8ed 100644 --- a/gcloud/alpha/iam/policies/help +++ b/gcloud/alpha/iam/policies/help @@ -15,9 +15,27 @@ GCLOUD WIDE FLAGS COMMANDS COMMAND is one of the following: + create + (ALPHA) Create a policy on the given attachment point with the given + name. + + delete + (ALPHA) Delete a policy on the given attachment point with the given + name. + + get + (ALPHA) Get a policy on the given attachment point with the given name. + lint-condition (ALPHA) Lint an IAM condition. + list + (ALPHA) List the policies on the given attachment point. + + update + (ALPHA) Update the policy on the given attachment point with the given + name. + 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/iam/policies/list b/gcloud/alpha/iam/policies/list new file mode 100644 index 000000000..409c873db --- /dev/null +++ b/gcloud/alpha/iam/policies/list @@ -0,0 +1,74 @@ +NAME + gcloud alpha iam policies list - list the policies on the given attachment + point + +SYNOPSIS + gcloud alpha iam policies list --attachment-point=ATTACHMENT_POINT + --kind=KIND [--page_token=PAGE_TOKEN] [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) List the policies on the given attachment point. + +EXAMPLES + The following command lists the IAM policy defined at the resource project + 123 of kind denypolicies: + + $ gcloud alpha iam policies list \ + --attachment-point=cloudresourcemanager.googleapis.com/\ + projects/123 --kind=denypolicies + +REQUIRED FLAGS + --attachment-point=ATTACHMENT_POINT + Resource to which the policy is attached. + + --kind=KIND + Kind of the policy. + +FLAGS + --page_token=PAGE_TOKEN + Page token received from a previous call. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta iam policies list + diff --git a/gcloud/alpha/iam/policies/update b/gcloud/alpha/iam/policies/update new file mode 100644 index 000000000..4f315a0da --- /dev/null +++ b/gcloud/alpha/iam/policies/update @@ -0,0 +1,59 @@ +NAME + gcloud alpha iam policies update - update the policy on the given + attachment point with the given name + +SYNOPSIS + gcloud alpha iam policies update POLICY_ID + --attachment-point=ATTACHMENT_POINT --kind=KIND + --policy-file=POLICY_FILE [--etag=ETAG] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Update the policy on the given attachment point with the given + name. + +EXAMPLES + The following command updates the IAM policy defined at the resource + project 123 of kind denypolicies and id my-deny-policy, with etag abc: + + $ gcloud alpha iam policies update my-deny-policy \ + --attachment-point=cloudresourcemanager.googleapis.com/\ + projects/123 --kind=denypolicies --policy-file=policy.json \ + --etag=abc + + If etag isn't provided, the command will try to get the etag using the + calling user permissions. + +POSITIONAL ARGUMENTS + POLICY_ID + Id of the policy. + +REQUIRED FLAGS + --attachment-point=ATTACHMENT_POINT + Resource to which the policy is attached. + + --kind=KIND + Kind of the policy. + + --policy-file=POLICY_FILE + Contents of the policy. + +OPTIONAL FLAGS + --etag=ETAG + Etag of the existing 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. This variant is also available: + + $ gcloud beta iam policies update + diff --git a/gcloud/alpha/iam/workload-identity-pools/create b/gcloud/alpha/iam/workload-identity-pools/create index bb2bda151..15b8d6184 100644 --- a/gcloud/alpha/iam/workload-identity-pools/create +++ b/gcloud/alpha/iam/workload-identity-pools/create @@ -17,11 +17,9 @@ EXAMPLES all required and optional parameters are provided. $ gcloud alpha iam workload-identity-pools create \ - my-workload-identity-pool \ - --location="global" \ + my-workload-identity-pool --location="global" \ --display-name="My workload pool" \ - --description="My workload pool description" \ - --disabled + --description="My workload pool description" --disabled POSITIONAL ARGUMENTS Workload identity pool resource - The workload identity pool to create. diff --git a/gcloud/alpha/iam/workload-identity-pools/providers/create-aws b/gcloud/alpha/iam/workload-identity-pools/providers/create-aws index 60d67081b..d9df9ef88 100644 --- a/gcloud/alpha/iam/workload-identity-pools/providers/create-aws +++ b/gcloud/alpha/iam/workload-identity-pools/providers/create-aws @@ -20,15 +20,12 @@ EXAMPLES Explicit values for all required and optional parameters are provided. $ gcloud alpha iam workload-identity-pools providers create-aws \ - my-workload-identity-pool-provider \ - --location="global" \ + my-workload-identity-pool-provider --location="global" \ --workload-identity-pool="my-workload-identity-pool" \ --display-name="My workload pool provider" \ --description="My workload pool provider description" \ - --disabled \ - --attribute-mapping="google.subject=assertion.arn" \ - --attribute-condition="true" \ - --account-id=1234567890 + --disabled --attribute-mapping="google.subject=assertion.arn" \ + --attribute-condition="true" --account-id=1234567890 POSITIONAL ARGUMENTS Workload identity pool provider resource - The workload identity pool diff --git a/gcloud/alpha/iam/workload-identity-pools/providers/create-oidc b/gcloud/alpha/iam/workload-identity-pools/providers/create-oidc index 54184b48f..92a587476 100644 --- a/gcloud/alpha/iam/workload-identity-pools/providers/create-oidc +++ b/gcloud/alpha/iam/workload-identity-pools/providers/create-oidc @@ -20,16 +20,15 @@ EXAMPLES Explicit values for all required and optional parameters are provided. $ gcloud alpha iam workload-identity-pools providers create-oidc \ - my-workload-identity-pool-provider \ - --location="global" \ + my-workload-identity-pool-provider --location="global" \ --workload-identity-pool="my-workload-identity-pool" \ --display-name="My workload pool provider" \ --description="My workload pool provider description" \ - --disabled \ - --attribute-mapping="google.subject=assertion.sub" \ + --disabled --attribute-mapping="google.subject=assertion.sub" \ --attribute-condition="true" \ --issuer-uri="https://test-idp.com" \ - --allowed-audiences=https://test-audience-1.com,https://test-audience-2.com + --allowed-audiences=https://test-audience-1.com,https://\ + test-audience-2.com POSITIONAL ARGUMENTS Workload identity pool provider resource - The workload identity pool diff --git a/gcloud/alpha/iam/workload-identity-pools/providers/delete b/gcloud/alpha/iam/workload-identity-pools/providers/delete index 2e3efc208..b6c948a2e 100644 --- a/gcloud/alpha/iam/workload-identity-pools/providers/delete +++ b/gcloud/alpha/iam/workload-identity-pools/providers/delete @@ -17,8 +17,8 @@ EXAMPLES $ gcloud alpha iam workload-identity-pools providers delete \ my-workload-identity-pool-provider \ - --workload-identity-pool="my-workload-identity-pool" \ - --location="global" + --workload-identity-pool="my-workload-identity-pool" \ + --location="global" POSITIONAL ARGUMENTS Workload identity pool provider resource - The workload identity pool diff --git a/gcloud/alpha/iam/workload-identity-pools/providers/describe b/gcloud/alpha/iam/workload-identity-pools/providers/describe index 5ea215912..f8a7fb11a 100644 --- a/gcloud/alpha/iam/workload-identity-pools/providers/describe +++ b/gcloud/alpha/iam/workload-identity-pools/providers/describe @@ -16,9 +16,9 @@ EXAMPLES the ID my-workload-identity-pool-provider: $ gcloud alpha iam workload-identity-pools providers describe \ - my-workload-identity-pool-provider \ - --workload-identity-pool="my-workload-identity-pool" \ - --location="global" + my-workload-identity-pool-provider \ + --workload-identity-pool="my-workload-identity-pool" \ + --location="global" POSITIONAL ARGUMENTS Workload identity pool provider resource - The workload identity pool diff --git a/gcloud/alpha/iam/workload-identity-pools/providers/list b/gcloud/alpha/iam/workload-identity-pools/providers/list index cc91e9473..077f141b9 100644 --- a/gcloud/alpha/iam/workload-identity-pools/providers/list +++ b/gcloud/alpha/iam/workload-identity-pools/providers/list @@ -15,10 +15,9 @@ EXAMPLES The following command lists all workload identity pool providers in the workload identity pool, including soft-deleted providers: - $ gcloud alpha iam workload-identity-pools providers list \ - --workload-identity-pool="my-workload-identity-pool" \ - --location="global" \ - --show-deleted + $ gcloud alpha iam workload-identity-pools providers list \ + --workload-identity-pool="my-workload-identity-pool" \ + --location="global" --show-deleted REQUIRED FLAGS Workload identity pool resource - The location to list workload identity diff --git a/gcloud/alpha/iam/workload-identity-pools/providers/operations/describe b/gcloud/alpha/iam/workload-identity-pools/providers/operations/describe index 8403689ee..ec494acb4 100644 --- a/gcloud/alpha/iam/workload-identity-pools/providers/operations/describe +++ b/gcloud/alpha/iam/workload-identity-pools/providers/operations/describe @@ -18,8 +18,7 @@ EXAMPLES $ gcloud alpha iam workload-identity-pools providers operations \ describe my-operation \ --workload-identity-pool="my-workload-identity-pool" \ - --provider="my-provider" \ - --location="global" + --provider="my-provider" --location="global" POSITIONAL ARGUMENTS Workload identity pool provider operation resource - The workload identity diff --git a/gcloud/alpha/iam/workload-identity-pools/providers/undelete b/gcloud/alpha/iam/workload-identity-pools/providers/undelete index e4ce6b8c7..290c92b60 100644 --- a/gcloud/alpha/iam/workload-identity-pools/providers/undelete +++ b/gcloud/alpha/iam/workload-identity-pools/providers/undelete @@ -17,8 +17,8 @@ EXAMPLES $ gcloud alpha iam workload-identity-pools providers undelete \ my-workload-identity-pool-provider \ - --workload-identity-pool="my-workload-identity-pool" \ - --location="global" + --workload-identity-pool="my-workload-identity-pool" \ + --location="global" POSITIONAL ARGUMENTS Workload identity pool provider resource - The workload identity pool diff --git a/gcloud/alpha/iam/workload-identity-pools/providers/update-aws b/gcloud/alpha/iam/workload-identity-pools/providers/update-aws index 7fd025a01..a1e305ae6 100644 --- a/gcloud/alpha/iam/workload-identity-pools/providers/update-aws +++ b/gcloud/alpha/iam/workload-identity-pools/providers/update-aws @@ -24,10 +24,8 @@ EXAMPLES --workload-identity-pool="my-workload-identity-pool" \ --display-name="My workload pool provider" \ --description="My workload pool provider description" \ - --disabled \ - --attribute-mapping="google.subject=assertion.arn" \ - --attribute-condition="true" \ - --account-id=1234567890 + --disabled --attribute-mapping="google.subject=assertion.arn" \ + --attribute-condition="true" --account-id=1234567890 POSITIONAL ARGUMENTS Workload identity pool provider resource - The workload identity pool diff --git a/gcloud/alpha/iam/workload-identity-pools/providers/update-oidc b/gcloud/alpha/iam/workload-identity-pools/providers/update-oidc index 52180e06b..9e55e1311 100644 --- a/gcloud/alpha/iam/workload-identity-pools/providers/update-oidc +++ b/gcloud/alpha/iam/workload-identity-pools/providers/update-oidc @@ -21,16 +21,15 @@ EXAMPLES and optional parameters are provided: $ gcloud alpha iam workload-identity-pools providers update-oidc \ - my-workload-identity-pool-provider \ - --location="global" \ + my-workload-identity-pool-provider --location="global" \ --workload-identity-pool="my-workload-identity-pool" \ --display-name="My workload pool provider" \ --description="My workload pool provider description" \ - --disabled \ - --attribute-mapping="google.subject=assertion.sub" \ + --disabled --attribute-mapping="google.subject=assertion.sub" \ --attribute-condition="true" \ - --issuer-uri="https://test-idp.com" - --allowed-audiences=https://test-audience-1.com,https://test-audience-2.com + --issuer-uri="https://test-idp.com" \ + --allowed-audiences=https://test-audience-1.com,https://\ + test-audience-2.com POSITIONAL ARGUMENTS Workload identity pool provider resource - The workload identity pool diff --git a/gcloud/alpha/iam/workload-identity-pools/update b/gcloud/alpha/iam/workload-identity-pools/update index 12ca86a04..bb2a52842 100644 --- a/gcloud/alpha/iam/workload-identity-pools/update +++ b/gcloud/alpha/iam/workload-identity-pools/update @@ -16,11 +16,9 @@ EXAMPLES my-workload-identity-pool: $ gcloud alpha iam workload-identity-pools update \ - my-workload-identity-pool \ - --location="global" + my-workload-identity-pool --location="global" \ --display-name="My workload pool" \ - --description="My workload pool description" \ - --disabled + --description="My workload pool description" --disabled POSITIONAL ARGUMENTS Workload identity pool resource - The workload identity pool to update. diff --git a/gcloud/alpha/iap/gateway/add-iam-policy-binding b/gcloud/alpha/iap/gateway/add-iam-policy-binding index 694539d38..5846d51f3 100644 --- a/gcloud/alpha/iap/gateway/add-iam-policy-binding +++ b/gcloud/alpha/iap/gateway/add-iam-policy-binding @@ -29,8 +29,8 @@ EXAMPLES the role of 'roles/browser' and the user 'test-user@gmail.com' , run: $ gcloud alpha iap gateway add-iam-policy-binding \ - --member='user:test-user@gmail.com' - --role='roles/browser' --condition='expression=request.time < + --member='user:test-user@gmail.com' --role='roles/browser' \ + --condition='expression=request.time < timestamp("2019-01-01T00:00:00Z"),title=expires_end_of_2018, description=Expires at midnight on 2018-12-31' diff --git a/gcloud/alpha/iap/gateway/remove-iam-policy-binding b/gcloud/alpha/iap/gateway/remove-iam-policy-binding index 8a4e34000..fd64f42b0 100644 --- a/gcloud/alpha/iap/gateway/remove-iam-policy-binding +++ b/gcloud/alpha/iap/gateway/remove-iam-policy-binding @@ -30,7 +30,7 @@ EXAMPLES for the role of 'roles/browser' for the user 'test-user@gmail.com', run: $ gcloud alpha iap gateway remove-iam-policy-binding \ - --member='user:test-user@gmail.com' --role='roles/browser' + --member='user:test-user@gmail.com' --role='roles/browser' \ --condition='expression=request.time < timestamp("2019-01-01T00:00:00Z"),title=expires_end_of_2018, description=Expires at midnight on 2018-12-31' @@ -39,8 +39,7 @@ EXAMPLES of 'roles/browser' and for the user 'test-user@gmail.com', run: $ gcloud alpha iap gateway remove-iam-policy-binding \ - --member='user:test-user@gmail.com' --role='roles/browser' - --all + --member='user:test-user@gmail.com' --role='roles/browser' --all See https://cloud.google.com/iam/docs/managing-policies for details of policy role and member types. diff --git a/gcloud/alpha/iap/oauth-brands/create b/gcloud/alpha/iap/oauth-brands/create index 27c111a3e..50c935311 100644 --- a/gcloud/alpha/iap/oauth-brands/create +++ b/gcloud/alpha/iap/oauth-brands/create @@ -27,7 +27,7 @@ EXAMPLES To create a Cloud OAuth brand for the project PROJECT_ID, run: - $ gcloud alpha iap oauth-brands create \ + $ gcloud alpha iap oauth-brands create \ --application_title=APPLICATION_TITLE \ --support_email=SUPPORT_EMAIL --project=PROJECT_ID diff --git a/gcloud/alpha/iap/oauth-brands/list b/gcloud/alpha/iap/oauth-brands/list index 063bd10b1..1f4fb3786 100644 --- a/gcloud/alpha/iap/oauth-brands/list +++ b/gcloud/alpha/iap/oauth-brands/list @@ -16,7 +16,7 @@ EXAMPLES To list all Cloud OAuth brands in the project PROJECT_ID, run: - $ gcloud alpha iap oauth-brands list --project=PROJECT_ID + $ gcloud alpha iap oauth-brands list --project=PROJECT_ID LIST COMMAND FLAGS --filter=EXPRESSION diff --git a/gcloud/alpha/iap/settings/get b/gcloud/alpha/iap/settings/get index fe7783908..eee6ab2bb 100644 --- a/gcloud/alpha/iap/settings/get +++ b/gcloud/alpha/iap/settings/get @@ -43,7 +43,7 @@ EXAMPLES run: $ gcloud alpha iap settings get --project=PROJECT_ID \ - --resource-type=app-engine --service=SERVICE_ID + --resource-type=app-engine --service=SERVICE_ID \ --version=VERSION_ID To get the IAP setting for all backend services within a project, run: diff --git a/gcloud/alpha/iap/settings/set b/gcloud/alpha/iap/settings/set index 2622b8722..3627f219d 100644 --- a/gcloud/alpha/iap/settings/set +++ b/gcloud/alpha/iap/settings/set @@ -44,7 +44,7 @@ EXAMPLES run: $ gcloud alpha iap settings set SETTING_FILE --project=PROJECT_ID \ - --resource-type=app-engine --service=SERVICE_ID + --resource-type=app-engine --service=SERVICE_ID \ --version=VERSION_ID To set the IAP setting for all backend services within a project, run: diff --git a/gcloud/alpha/iap/web/add-iam-policy-binding b/gcloud/alpha/iap/web/add-iam-policy-binding index f34d807c5..e7a80bbe8 100644 --- a/gcloud/alpha/iap/web/add-iam-policy-binding +++ b/gcloud/alpha/iap/web/add-iam-policy-binding @@ -25,16 +25,14 @@ EXAMPLES $ gcloud alpha iap web add-iam-policy-binding \ --resource-type=IAP_IAM_RESOURCE \ - --member='user:test-user@gmail.com' - --role='roles/editor' + --member='user:test-user@gmail.com' --role='roles/editor' To add an IAM policy binding for the role of 'roles/editor' for all authenticated users on IAP IAM resource IAP_IAM_RESOURCE, run: $ gcloud alpha iap web add-iam-policy-binding \ --resource-type=IAP_IAM_RESOURCE \ - --member='allAuthenticatedUsers' - --role='roles/editor' + --member='allAuthenticatedUsers' --role='roles/editor' To add an IAM policy binding which expires at the end of the year 2018 for the role of 'roles/browser' and the user 'test-user@gmail.com' on IAP IAM @@ -42,8 +40,8 @@ EXAMPLES $ gcloud alpha iap web add-iam-policy-binding \ --resource-type=IAP_IAM_RESOURCE \ - --member='user:test-user@gmail.com' - --role='roles/browser' --condition='expression=request.time < + --member='user:test-user@gmail.com' --role='roles/browser' \ + --condition='expression=request.time < timestamp("2019-01-01T00:00:00Z"),title=expires_end_of_2018, description=Expires at midnight on 2018-12-31' diff --git a/gcloud/alpha/iap/web/enable b/gcloud/alpha/iap/web/enable index d6a627cd2..cb4aead0b 100644 --- a/gcloud/alpha/iap/web/enable +++ b/gcloud/alpha/iap/web/enable @@ -17,13 +17,13 @@ DESCRIPTION EXAMPLES To enable IAP on an App Engine application, run: - $ gcloud alpha iap web enable --resource-type=app-engine + $ gcloud alpha iap web enable --resource-type=app-engine \ --oauth2-client-id=CLIENT_ID --oauth2-client-secret=SECRET To enable IAP on a backend service, run: - $ gcloud alpha iap web enable --resource-type=backend-services - --oauth2-client-id=CLIENT_ID --oauth2-client-secret=SECRET + $ gcloud alpha iap web enable --resource-type=backend-services \ + --oauth2-client-id=CLIENT_ID --oauth2-client-secret=SECRET \ --service=SERVICE_ID FLAGS diff --git a/gcloud/alpha/iap/web/get-iam-policy b/gcloud/alpha/iap/web/get-iam-policy index fb5c50a9d..5d77007d5 100644 --- a/gcloud/alpha/iap/web/get-iam-policy +++ b/gcloud/alpha/iap/web/get-iam-policy @@ -43,8 +43,7 @@ EXAMPLES within an App Engine service version, run: $ gcloud alpha iap web get-iam-policy --resource-type=app-engine \ - --service=SERVICE_ID - --version=VERSION + --service=SERVICE_ID --version=VERSION To get the IAM policy for the web accesses to the IAP protected resources within all backend services, run: diff --git a/gcloud/alpha/iap/web/remove-iam-policy-binding b/gcloud/alpha/iap/web/remove-iam-policy-binding index 2533f07cc..6c05a31dc 100644 --- a/gcloud/alpha/iap/web/remove-iam-policy-binding +++ b/gcloud/alpha/iap/web/remove-iam-policy-binding @@ -26,16 +26,14 @@ EXAMPLES $ gcloud alpha iap web remove-iam-policy-binding \ --resource-type=IAP_IAM_RESOURCE \ - --member='user:test-user@gmail.com' - --role='roles/editor' + --member='user:test-user@gmail.com' --role='roles/editor' To remove an IAM policy binding for the role of 'roles/editor' from all authenticated users on IAP IAM resource IAP_IAM_RESOURCE,run: $ gcloud alpha iap web remove-iam-policy-binding \ --resource-type=IAP_IAM_RESOURCE \ - --member='allAuthenticatedUsers' - --role='roles/editor' + --member='allAuthenticatedUsers' --role='roles/editor' To remove an IAM policy binding with a condition of expression='request.time < timestamp("2019-01-01T00:00:00Z")', @@ -45,8 +43,8 @@ EXAMPLES $ gcloud alpha iap web remove-iam-policy-binding \ --resource-type=IAP_IAM_RESOURCE \ - --member='user:test-user@gmail.com' - --role='roles/browser' --condition='expression=request.time < + --member='user:test-user@gmail.com' --role='roles/browser' \ + --condition='expression=request.time < timestamp("2019-01-01T00:00:00Z"),title=expires_end_of_2018, description=Expires at midnight on 2018-12-31' @@ -56,8 +54,7 @@ EXAMPLES $ gcloud alpha iap web remove-iam-policy-binding \ --resource-type=IAP_IAM_RESOURCE \ - --member='user:test-user@gmail.com' - --role='roles/browser' --all + --member='user:test-user@gmail.com' --role='roles/browser' --all See https://cloud.google.com/iam/docs/managing-policies for details of policy role and member types. diff --git a/gcloud/alpha/iap/web/set-iam-policy b/gcloud/alpha/iap/web/set-iam-policy index e95eea042..76a18d092 100644 --- a/gcloud/alpha/iap/web/set-iam-policy +++ b/gcloud/alpha/iap/web/set-iam-policy @@ -40,15 +40,14 @@ EXAMPLES within an App Engine service, run: $ gcloud alpha iap web set-iam-policy POLICY_FILE \ - --resource-type=app-engine - --service=SERVICE_ID + --resource-type=app-engine --service=SERVICE_ID To set the IAM policy for the web accesses to the IAP protected resources within an App Engine service version, run: $ gcloud alpha iap web set-iam-policy POLICY_FILE \ - --resource-type=app-engine - --service=SERVICE_ID --version=VERSION + --resource-type=app-engine --service=SERVICE_ID \ + --version=VERSION To set the IAM policy for the web accesses to the IAP protected resources within all backend services, run: @@ -60,8 +59,7 @@ EXAMPLES within a backend service, run: $ gcloud alpha iap web set-iam-policy POLICY_FILE \ - --resource-type=backend-services - --service=SERVICE_ID + --resource-type=backend-services --service=SERVICE_ID POSITIONAL ARGUMENTS POLICY_FILE diff --git a/gcloud/alpha/identity/groups/create b/gcloud/alpha/identity/groups/create index 756bdb291..2b8665adb 100644 --- a/gcloud/alpha/identity/groups/create +++ b/gcloud/alpha/identity/groups/create @@ -23,23 +23,20 @@ EXAMPLES descripton: $ gcloud alpha identity groups create eng-discuss@example.com \ - --organization="example.com" \ - --display-name="Engineer Discuss" \ + --organization="example.com" --display-name="Engineer Discuss" \ --description="Group for engineering discussions" To create a new security group: - $ gcloud alpha identity groups create security-group@example.com \ - --organization="example.com" \ - --group-type="security" \ - --display-name="Security Group" \ + $ gcloud alpha identity groups create security-group@example.com \ + --organization="example.com" --group-type="security" \ + --display-name="Security Group" \ --description="Description of Security Group" To create a new POSIX group: $ gcloud alpha identity groups create eng-discuss@example.com \ - --organization="example.com" \ - --posix-group=name=eng,gid=1005 + --organization="example.com" --posix-group=name=eng,gid=1005 POSITIONAL ARGUMENTS EMAIL diff --git a/gcloud/alpha/identity/groups/memberships/add b/gcloud/alpha/identity/groups/memberships/add index daa7c64d5..8c756eca5 100644 --- a/gcloud/alpha/identity/groups/memberships/add +++ b/gcloud/alpha/identity/groups/memberships/add @@ -15,7 +15,7 @@ EXAMPLES To create a new membership in a group: $ gcloud alpha identity groups memberships add \ - --group-email="eng-discuss@foo.com" \ + --group-email="eng-discuss@foo.com" \ --member-email="user@foo.com" REQUIRED FLAGS diff --git a/gcloud/alpha/identity/groups/memberships/modify-membership-roles b/gcloud/alpha/identity/groups/memberships/modify-membership-roles index 62a8ec6c8..437723be0 100644 --- a/gcloud/alpha/identity/groups/memberships/modify-membership-roles +++ b/gcloud/alpha/identity/groups/memberships/modify-membership-roles @@ -17,9 +17,8 @@ EXAMPLES To add a new membership role to an existing group-member pair. $ gcloud alpha identity groups memberships modify-membership-roles \ - --group-email="eng-discuss@foo.com" \ - --member-email="user@foo.com" \ - --add-roles=OWNER + --group-email="eng-discuss@foo.com" \ + --member-email="user@foo.com" --add-roles=OWNER REQUIRED FLAGS --group-email=GROUP_EMAIL diff --git a/gcloud/alpha/identity/groups/search b/gcloud/alpha/identity/groups/search index 23dda6c08..643515894 100644 --- a/gcloud/alpha/identity/groups/search +++ b/gcloud/alpha/identity/groups/search @@ -14,10 +14,9 @@ DESCRIPTION EXAMPLES To Search groups: - $ gcloud alpha identity groups search --organization="5149234212" \ - --labels="cloudidentity.googleapis.com/groups.discussion_forum" \ - --page-size=3 \ - --page-token="ala9glealanal908" + $ gcloud alpha identity groups search --organization="5149234212" \ + --labels="cloudidentity.googleapis.com/groups.discussion_forum" \ + --page-size=3 --page-token="ala9glealanal908" REQUIRED FLAGS --labels=LABELS diff --git a/gcloud/alpha/identity/groups/update b/gcloud/alpha/identity/groups/update index 75a58d824..183195ad2 100644 --- a/gcloud/alpha/identity/groups/update +++ b/gcloud/alpha/identity/groups/update @@ -16,8 +16,8 @@ DESCRIPTION EXAMPLES To update a group: - $ gcloud alpha identity groups update eng-discuss@foo.com \ - --display-name="New Engineer Discuss" \ + $ gcloud alpha identity groups update eng-discuss@foo.com \ + --display-name="New Engineer Discuss" \ --description="Group for engineering discussions" To create a POSIX group from an existing Google Group: diff --git a/gcloud/alpha/kms/asymmetric-decrypt b/gcloud/alpha/kms/asymmetric-decrypt index 09de5d221..3a4147848 100644 --- a/gcloud/alpha/kms/asymmetric-decrypt +++ b/gcloud/alpha/kms/asymmetric-decrypt @@ -22,13 +22,10 @@ EXAMPLES it using the asymmetric CryptoKey dont-panic Version 3 and write the plaintext to '/tmp/my/secret.file.dec'. - $ gcloud alpha kms asymmetric-decrypt \ - --location=us-central1 \ - --keyring=hitchhiker \ - --key=dont-panic \ - --version=3 \ - --ciphertext-file=/tmp/my/secret.file.enc \ - --plaintext-file=/tmp/my/secret.file.dec + $ gcloud alpha kms asymmetric-decrypt --location=us-central1 \ + --keyring=hitchhiker --key=dont-panic --version=3 \ + --ciphertext-file=/tmp/my/secret.file.enc \ + --plaintext-file=/tmp/my/secret.file.dec REQUIRED FLAGS --ciphertext-file=CIPHERTEXT_FILE diff --git a/gcloud/alpha/kms/asymmetric-sign b/gcloud/alpha/kms/asymmetric-sign index d999a77b1..1b5af8f6f 100644 --- a/gcloud/alpha/kms/asymmetric-sign +++ b/gcloud/alpha/kms/asymmetric-sign @@ -25,14 +25,10 @@ EXAMPLES CryptoKey dont-panic Version 3, and save the signature in base64 format to '/tmp/my/signature'. - $ gcloud alpha kms asymmetric-sign \ - --location=us-central1 \ - --keyring=hitchhiker \ - --key=dont-panic \ - --version=3 \ - --digest-algorithm=sha256 \ - --input-file=/tmp/my/file.to.sign \ - --signature-file=/tmp/my/signature + $ gcloud alpha kms asymmetric-sign --location=us-central1 \ + --keyring=hitchhiker --key=dont-panic --version=3 \ + --digest-algorithm=sha256 --input-file=/tmp/my/file.to.sign \ + --signature-file=/tmp/my/signature REQUIRED FLAGS --input-file=INPUT_FILE diff --git a/gcloud/alpha/kms/decrypt b/gcloud/alpha/kms/decrypt index 8d5e64047..a5058e236 100644 --- a/gcloud/alpha/kms/decrypt +++ b/gcloud/alpha/kms/decrypt @@ -38,24 +38,18 @@ EXAMPLES fellowship and location global and write the plaintext to 'path/to/plaintext.dec', run: - $ gcloud alpha kms decrypt \ - --key=frodo \ - --keyring=fellowship \ - --location=global \ - --ciphertext-file=path/to/input/ciphertext \ + $ gcloud alpha kms decrypt --key=frodo --keyring=fellowship \ + --location=global --ciphertext-file=path/to/input/ciphertext \ --plaintext-file=path/to/output/plaintext.dec To decrypt the file 'path/to/ciphertext' using the key frodo and the additional authenticated data that was used to encrypt the ciphertext, and write the decrypted plaintext to stdout, run: - $ gcloud alpha kms decrypt \ - --key=frodo \ - --keyring=fellowship \ + $ gcloud alpha kms decrypt --key=frodo --keyring=fellowship \ --location=global \ --additional-authenticated-data-file=path/to/aad \ - --ciphertext-file=path/to/input/ciphertext \ - --plaintext-file='-' + --ciphertext-file=path/to/input/ciphertext --plaintext-file='-' REQUIRED FLAGS --ciphertext-file=CIPHERTEXT_FILE diff --git a/gcloud/alpha/kms/ekm-connections/add-iam-policy-binding b/gcloud/alpha/kms/ekm-connections/add-iam-policy-binding index c960a46b8..4f3d90fef 100644 --- a/gcloud/alpha/kms/ekm-connections/add-iam-policy-binding +++ b/gcloud/alpha/kms/ekm-connections/add-iam-policy-binding @@ -136,7 +136,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 kms ekm-connections add-iam-policy-binding $ gcloud beta kms ekm-connections add-iam-policy-binding diff --git a/gcloud/alpha/kms/ekm-connections/create b/gcloud/alpha/kms/ekm-connections/create index 28ea01669..b925e4fe1 100644 --- a/gcloud/alpha/kms/ekm-connections/create +++ b/gcloud/alpha/kms/ekm-connections/create @@ -16,10 +16,8 @@ EXAMPLES location us-central1: $ gcloud alpha kms ekm-connections create laplace \ - --location=us-central1 \ - --service-directory-service="foo" \ - --endpoint-filter="foo > bar" \ - --hostname="hostname.foo" \ + --location=us-central1 --service-directory-service="foo" \ + --endpoint-filter="foo > bar" --hostname="hostname.foo" \ --server-certificates-files=foo.pem,bar.pem POSITIONAL ARGUMENTS @@ -78,7 +76,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud kms ekm-connections create $ gcloud beta kms ekm-connections create diff --git a/gcloud/alpha/kms/ekm-connections/describe b/gcloud/alpha/kms/ekm-connections/describe index 9c391f650..1decba59a 100644 --- a/gcloud/alpha/kms/ekm-connections/describe +++ b/gcloud/alpha/kms/ekm-connections/describe @@ -54,7 +54,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 kms ekm-connections describe $ gcloud beta kms ekm-connections describe diff --git a/gcloud/alpha/kms/ekm-connections/get-iam-policy b/gcloud/alpha/kms/ekm-connections/get-iam-policy index 7471f34f5..1f847e91c 100644 --- a/gcloud/alpha/kms/ekm-connections/get-iam-policy +++ b/gcloud/alpha/kms/ekm-connections/get-iam-policy @@ -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 kms ekm-connections get-iam-policy $ gcloud beta kms ekm-connections get-iam-policy diff --git a/gcloud/alpha/kms/ekm-connections/help b/gcloud/alpha/kms/ekm-connections/help index d56c29b70..954317c83 100644 --- a/gcloud/alpha/kms/ekm-connections/help +++ b/gcloud/alpha/kms/ekm-connections/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 kms ekm-connections $ gcloud beta kms ekm-connections diff --git a/gcloud/alpha/kms/ekm-connections/list b/gcloud/alpha/kms/ekm-connections/list index 1334f1848..816ed6f18 100644 --- a/gcloud/alpha/kms/ekm-connections/list +++ b/gcloud/alpha/kms/ekm-connections/list @@ -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 kms ekm-connections list $ gcloud beta kms ekm-connections list diff --git a/gcloud/alpha/kms/ekm-connections/remove-iam-policy-binding b/gcloud/alpha/kms/ekm-connections/remove-iam-policy-binding index 88a83486a..6287180e5 100644 --- a/gcloud/alpha/kms/ekm-connections/remove-iam-policy-binding +++ b/gcloud/alpha/kms/ekm-connections/remove-iam-policy-binding @@ -153,7 +153,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 kms ekm-connections remove-iam-policy-binding $ gcloud beta kms ekm-connections remove-iam-policy-binding diff --git a/gcloud/alpha/kms/ekm-connections/set-iam-policy b/gcloud/alpha/kms/ekm-connections/set-iam-policy index 6c1c94823..f7c85760f 100644 --- a/gcloud/alpha/kms/ekm-connections/set-iam-policy +++ b/gcloud/alpha/kms/ekm-connections/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 kms ekm-connections set-iam-policy $ gcloud beta kms ekm-connections set-iam-policy diff --git a/gcloud/alpha/kms/ekm-connections/update b/gcloud/alpha/kms/ekm-connections/update index 4c54b8dc0..738a7678d 100644 --- a/gcloud/alpha/kms/ekm-connections/update +++ b/gcloud/alpha/kms/ekm-connections/update @@ -19,18 +19,15 @@ EXAMPLES resolver's hostname within location us-east1: $ gcloud alpha kms ekm-connections update laplace \ - --location=us-east1 \ - --hostname=newhostname.foo \ + --location=us-east1 --hostname=newhostname.foo \ The following command updates an ekm-connection named laplace service resolver's service_directory_service, endpoint_filter, hostname, and server_certificates within location us-east1: $ gcloud alpha kms ekm-connections update laplace \ - --location=us-east1 \ - --service-directory-service="foo" \ - --endpoint-filter="foo > bar" \ - --hostname="newhostname.foo" \ + --location=us-east1 --service-directory-service="foo" \ + --endpoint-filter="foo > bar" --hostname="newhostname.foo" \ --server-certificates-files=foo.pem,bar.pem POSITIONAL ARGUMENTS @@ -88,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 kms ekm-connections update $ gcloud beta kms ekm-connections update diff --git a/gcloud/alpha/kms/encrypt b/gcloud/alpha/kms/encrypt index b7d81fd15..550ba62fd 100644 --- a/gcloud/alpha/kms/encrypt +++ b/gcloud/alpha/kms/encrypt @@ -33,11 +33,8 @@ EXAMPLES using the CryptoKey frodo with the KeyRing fellowship and Location global, and write the ciphertext to 'path/to/ciphertext'. - $ gcloud alpha kms encrypt \ - --key=frodo \ - --keyring=fellowship \ - --location=global \ - --plaintext-file=path/to/input/plaintext \ + $ gcloud alpha kms encrypt --key=frodo --keyring=fellowship \ + --location=global --plaintext-file=path/to/input/plaintext \ --ciphertext-file=path/to/output/ciphertext REQUIRED FLAGS diff --git a/gcloud/alpha/kms/import-jobs/create b/gcloud/alpha/kms/import-jobs/create index 5d198adff..1c915c947 100644 --- a/gcloud/alpha/kms/import-jobs/create +++ b/gcloud/alpha/kms/import-jobs/create @@ -14,8 +14,8 @@ EXAMPLES 'fellowship' keyring, and 'us-central1' location: $ gcloud alpha kms import-jobs create strider \ - --location=us-central1 \ - --keyring=fellowship --import-method=rsa-oaep-3072-sha1-aes-256 \ + --location=us-central1 --keyring=fellowship \ + --import-method=rsa-oaep-3072-sha1-aes-256 \ --protection-level=hsm POSITIONAL ARGUMENTS diff --git a/gcloud/alpha/kms/keys/create b/gcloud/alpha/kms/keys/create index 78a53ef79..f4b7f8465 100644 --- a/gcloud/alpha/kms/keys/create +++ b/gcloud/alpha/kms/keys/create @@ -57,75 +57,59 @@ EXAMPLES The following command creates a key named frodo with protection level software within the keyring fellowship and location us-east1: - $ gcloud alpha kms keys create frodo \ - --location=us-east1 \ - --keyring=fellowship \ - --purpose=encryption + $ gcloud alpha kms keys create frodo --location=us-east1 \ + --keyring=fellowship --purpose=encryption The following command creates a key named strider with protection level software within the keyring rangers and location global with a specified rotation schedule: - $ gcloud alpha kms keys create strider \ - --location=global --keyring=rangers \ - --purpose=encryption \ - --rotation-period=30d \ + $ gcloud alpha kms keys create strider --location=global \ + --keyring=rangers --purpose=encryption --rotation-period=30d \ --next-rotation-time=2017-10-12T12:34:56.1234Z The following command creates a key named foo with protection level software within the keyring fellowship and location us-east1 with two specified labels: - $ gcloud alpha kms keys create foo \ - --location=us-east1 \ - --keyring=fellowship \ - --purpose=encryption \ + $ gcloud alpha kms keys create foo --location=us-east1 \ + --keyring=fellowship --purpose=encryption \ --labels=env=prod,team=kms The following command creates an asymmetric key named samwise with protection level software and default algorithm ec-sign-p256-sha256 within the keyring fellowship and location us-east1: - $ gcloud alpha kms keys create samwise \ - --location=us-east1 \ - --keyring=fellowship \ - --purpose=asymmetric-signing \ + $ gcloud alpha kms keys create samwise --location=us-east1 \ + --keyring=fellowship --purpose=asymmetric-signing \ --default-algorithm=ec-sign-p256-sha256 The following command creates a key named gimli with protection level hsm and default algorithm google-symmetric-encryption within the keyring fellowship and location us-east1: - $ gcloud alpha kms keys create gimli \ - --location=us-east1 \ - --keyring=fellowship \ - --purpose=encryption \ - --protection-level=hsm + $ gcloud alpha kms keys create gimli --location=us-east1 \ + --keyring=fellowship --purpose=encryption --protection-level=hsm The following command creates a key named legolas with protection level external and default algorithm external-symmetric-encryption within the keyring fellowship and location us-central1: - $ gcloud alpha kms keys create legolas \ - --location=us-central1 \ - --keyring=fellowship \ - --purpose=encryption \ + $ gcloud alpha kms keys create legolas --location=us-central1 \ + --keyring=fellowship --purpose=encryption \ --default-algorithm=external-symmetric-encryption \ - --protection-level=external - --skip-initial-version-creation + --protection-level=external --skip-initial-version-creation The following command creates a key named bilbo with protection level external-vpc and default algorithm external-symmetric-encryption and an EkmConnection of eagles within the keyring fellowship and location us-central1: - $ gcloud alpha kms keys create bilbo \ - --location=us-central1 \ - --keyring=fellowship \ - --purpose=encryption \ + $ gcloud alpha kms keys create bilbo --location=us-central1 \ + --keyring=fellowship --purpose=encryption \ --default-algorithm=external-symmetric-encryption \ - --protection-level=external-vpc - --skip-initial-version-creation + --protection-level=external-vpc \ + --skip-initial-version-creation \ --crypto-key-backend="projects/$(gcloud config get project)/ locations/us-central1/ekmConnections/eagles" diff --git a/gcloud/alpha/kms/keys/remove-rotation-schedule b/gcloud/alpha/kms/keys/remove-rotation-schedule index 7ff4bab71..8a63427d1 100644 --- a/gcloud/alpha/kms/keys/remove-rotation-schedule +++ b/gcloud/alpha/kms/keys/remove-rotation-schedule @@ -14,8 +14,7 @@ EXAMPLES within the keyring fellowship and location global: $ gcloud alpha kms keys remove-rotation-schedule frodo \ - --location=global \ - --keyring=fellowship + --location=global --keyring=fellowship POSITIONAL ARGUMENTS KEY diff --git a/gcloud/alpha/kms/keys/set-rotation-schedule b/gcloud/alpha/kms/keys/set-rotation-schedule index 687725c88..7a6fc9ca6 100644 --- a/gcloud/alpha/kms/keys/set-rotation-schedule +++ b/gcloud/alpha/kms/keys/set-rotation-schedule @@ -25,9 +25,7 @@ EXAMPLES time: $ gcloud alpha kms keys set-rotation-schedule frodo \ - --location=global \ - --keyring=fellowship \ - --rotation-period=30d \ + --location=global --keyring=fellowship --rotation-period=30d \ --next-rotation-time=2017-10-12T12:34:56.1234Z POSITIONAL ARGUMENTS diff --git a/gcloud/alpha/kms/keys/update b/gcloud/alpha/kms/keys/update index af4047c37..640e07c70 100644 --- a/gcloud/alpha/kms/keys/update +++ b/gcloud/alpha/kms/keys/update @@ -36,52 +36,41 @@ EXAMPLES within the keyring fellowship and location global starting at the specified time: - $ gcloud alpha kms keys update frodo \ - --location=global \ - --keyring=fellowship \ - --rotation-period=30d \ + $ gcloud alpha kms keys update frodo --location=global \ + --keyring=fellowship --rotation-period=30d \ --next-rotation-time=2017-10-12T12:34:56.1234Z The following command removes the rotation schedule for the key named frodo within the keyring fellowship and location global: - $ gcloud alpha kms keys update frodo \ - --location=global \ - --keyring=fellowship \ - --remove-rotation-schedule + $ gcloud alpha kms keys update frodo --location=global \ + --keyring=fellowship --remove-rotation-schedule The following command updates the labels value for the key named frodo within the keyring fellowship and location global. If the label key does not exist at the time, it will be added: - $ gcloud alpha kms keys update frodo \ - --location=global \ - --keyring=fellowship \ - --update-labels=k1=v1 + $ gcloud alpha kms keys update frodo --location=global \ + --keyring=fellowship --update-labels=k1=v1 The following command removes labels k1 and k2 from the key named frodo within the keyring fellowship and location global: - $ gcloud alpha kms keys update frodo \ - --location=global \ - --keyring=fellowship \ - --remove-labels=k1,k2 + $ gcloud alpha kms keys update frodo --location=global \ + --keyring=fellowship --remove-labels=k1,k2 The following command updates the primary version for the key named frodo within the keyring fellowship and location global: - $ gcloud alpha kms keys update frodo \ - --location=global \ - --keyring=fellowship \ - --primary-version=1 + $ gcloud alpha kms keys update frodo --location=global \ + --keyring=fellowship --primary-version=1 The following command updates the default algorithm for the key named frodo within the keyring fellowship and location global, assuming the key originally has purpose 'asymmetric-encryption' and algorithm 'rsa-decrypt-oaep-2048-sha256': - $ gcloud alpha kms keys update frodo \ - --location=global \ + $ gcloud alpha kms keys update frodo --location=global \ --keyring=fellowship \ --default-algorithm=rsa-decrypt-oaep-4096-sha256 diff --git a/gcloud/alpha/kms/keys/versions/create b/gcloud/alpha/kms/keys/versions/create index 14e581f27..04ff988b5 100644 --- a/gcloud/alpha/kms/keys/versions/create +++ b/gcloud/alpha/kms/keys/versions/create @@ -15,8 +15,7 @@ EXAMPLES fellowship keyring, and global location and sets it as the primary version: $ gcloud alpha kms keys versions create --location=global \ - --keyring=fellowship \ - --key=frodo --primary + --keyring=fellowship --key=frodo --primary The following command creates a new version within the legolas key, fellowship keyring, us-central1 location, @@ -24,8 +23,7 @@ EXAMPLES and sets it as the key's primary version: $ gcloud alpha kms keys versions create --location=us-central1 \ - --keyring=fellowship \ - --key=legolas \ + --keyring=fellowship --key=legolas \ --external-key-uri=https://example.kms/v0/some/key/path \ --primary @@ -35,10 +33,8 @@ EXAMPLES version: $ gcloud alpha kms keys versions create --location=us-central1 \ - --keyring=fellowship \ - --key=bilbo \ - --ekm-connection-key-path=v0/some/key/path \ - --primary + --keyring=fellowship --key=bilbo \ + --ekm-connection-key-path=v0/some/key/path --primary FLAGS --ekm-connection-key-path=EKM_CONNECTION_KEY_PATH diff --git a/gcloud/alpha/kms/keys/versions/get-public-key b/gcloud/alpha/kms/keys/versions/get-public-key index 04b05870e..5bedc8f2a 100644 --- a/gcloud/alpha/kms/keys/versions/get-public-key +++ b/gcloud/alpha/kms/keys/versions/get-public-key @@ -18,11 +18,9 @@ EXAMPLES The following command saves the public key for CryptoKey frodo Version 2 to '/tmp/my/pem.file': - $ gcloud alpha kms keys versions get-public-key 2 \ - --key=frodo \ - --keyring=fellowship \ - --location=us-east1 \ - --output-file=/tmp/my/pem.file + $ gcloud alpha kms keys versions get-public-key 2 --key=frodo \ + --keyring=fellowship --location=us-east1 \ + --output-file=/tmp/my/pem.file POSITIONAL ARGUMENTS VERSION diff --git a/gcloud/alpha/kms/keys/versions/import b/gcloud/alpha/kms/keys/versions/import index dccf9e7cc..65ffcd915 100644 --- a/gcloud/alpha/kms/keys/versions/import +++ b/gcloud/alpha/kms/keys/versions/import @@ -23,11 +23,9 @@ EXAMPLES the provided key material. $ gcloud alpha kms keys versions import --location=global \ - --keyring=fellowship \ - --key=frodo \ - --import-job=strider \ - --rsa-aes-wrapped-key-file=path/to/target/key \ - --algorithm=google-symmetric-encryption + --keyring=fellowship --key=frodo --import-job=strider \ + --rsa-aes-wrapped-key-file=path/to/target/key \ + --algorithm=google-symmetric-encryption REQUIRED FLAGS --algorithm=ALGORITHM diff --git a/gcloud/alpha/kms/keys/versions/list b/gcloud/alpha/kms/keys/versions/list index 649b85850..600190b10 100644 --- a/gcloud/alpha/kms/keys/versions/list +++ b/gcloud/alpha/kms/keys/versions/list @@ -15,8 +15,7 @@ EXAMPLES fellowship, and location global: $ gcloud alpha kms keys versions list --location=global \ - --keyring=fellowship \ - --key=frodo + --keyring=fellowship --key=frodo FLAGS --key=KEY diff --git a/gcloud/alpha/kms/keys/versions/update b/gcloud/alpha/kms/keys/versions/update index eb0175de1..955dabc0f 100644 --- a/gcloud/alpha/kms/keys/versions/update +++ b/gcloud/alpha/kms/keys/versions/update @@ -19,33 +19,27 @@ EXAMPLES fellowship and location us-east1: $ gcloud alpha kms keys versions update 8 --location=us-east1 \ - --keyring=fellowship \ - --key=frodo \ - --state=enabled + --keyring=fellowship --key=frodo --state=enabled The following command disables the key version 8 of key frodo within keyring fellowship and location us-east1: $ gcloud alpha kms keys versions update 8 --location=us-east1 \ - --keyring=fellowship \ - --key=frodo \ - --state=disabled + --keyring=fellowship --key=frodo --state=disabled The following command updates the external key URI of version 8 of key frodo within keyring fellowship and location us-east1: $ gcloud alpha kms keys versions update 8 --location=us-east1 \ - --keyring=fellowship \ - --key=frodo \ - --external-key-uri=https://example.kms/v0/some/key/path + --keyring=fellowship --key=frodo \ + --external-key-uri=https://example.kms/v0/some/key/path The following command updates the ekm connection key path of version 8 of key bilbo within keyring fellowship and location us-east1: $ gcloud alpha kms keys versions update 8 --location=us-east1 \ - --keyring=fellowship \ - --key=bilbo \ - --ekm-connection-key-path=v0/some/key/path + --keyring=fellowship --key=bilbo \ + --ekm-connection-key-path=v0/some/key/path POSITIONAL ARGUMENTS VERSION diff --git a/gcloud/alpha/kms/mac-sign b/gcloud/alpha/kms/mac-sign index 0d0360aea..ea6b8b1a7 100644 --- a/gcloud/alpha/kms/mac-sign +++ b/gcloud/alpha/kms/mac-sign @@ -22,13 +22,10 @@ EXAMPLES it using the symmetric MAC CryptoKey dont-panic Version 3, and save the signature in base64 format to '/tmp/my/signature'. - $ gcloud alpha kms mac-sign \ - --location=us-central1 \ - --keyring=hitchhiker \ - --key=dont-panic \ - --version=3 \ - --input-file=/tmp/my/file.to.sign \ - --signature-file=/tmp/my/signature + $ gcloud alpha kms mac-sign --location=us-central1 \ + --keyring=hitchhiker --key=dont-panic --version=3 \ + --input-file=/tmp/my/file.to.sign \ + --signature-file=/tmp/my/signature REQUIRED FLAGS --input-file=INPUT_FILE diff --git a/gcloud/alpha/kms/mac-verify b/gcloud/alpha/kms/mac-verify index aa8af4eb5..07a6ba4f8 100644 --- a/gcloud/alpha/kms/mac-verify +++ b/gcloud/alpha/kms/mac-verify @@ -22,13 +22,10 @@ EXAMPLES file used previously to generate the MAC tag ('/tmp/my/original.data.file'). - $ gcloud alpha kms mac-verify \ - --location=us-central1 \ - --keyring=hitchhiker \ - --key=dont-panic \ - --version=3 \ - --input-file=/tmp/my/original.data.file \ - --signature-file=/tmp/my/file.to.verify + $ gcloud alpha kms mac-verify --location=us-central1 \ + --keyring=hitchhiker --key=dont-panic --version=3 \ + --input-file=/tmp/my/original.data.file \ + --signature-file=/tmp/my/file.to.verify REQUIRED FLAGS --input-file=INPUT_FILE diff --git a/gcloud/alpha/lifesciences/pipelines/run b/gcloud/alpha/lifesciences/pipelines/run index b1c4c5790..b7dfe825b 100644 --- a/gcloud/alpha/lifesciences/pipelines/run +++ b/gcloud/alpha/lifesciences/pipelines/run @@ -142,8 +142,9 @@ OTHER FLAGS 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 to run the pipeline. If unspecified, defaults - to the Compute Engine service account for your project. + 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 diff --git a/gcloud/alpha/logging/settings/update b/gcloud/alpha/logging/settings/update index f764987b4..db8eb075e 100644 --- a/gcloud/alpha/logging/settings/update +++ b/gcloud/alpha/logging/settings/update @@ -28,8 +28,9 @@ EXAMPLES To enable CMEK for the Logs Router for an organization, run: $ gcloud alpha logging settings update \ - --organization=[ORGANIZATION_ID] - --kms-key-name='projects/my-project/locations/my-location/keyRings/my-keyring/cryptoKeys/key' + --organization=[ORGANIZATION_ID] \ + --kms-key-name='projects/my-project/locations/my-location/keyRin\ + gs/my-keyring/cryptoKeys/key' To disable CMEK for the Logs Router for an organization, run: @@ -39,8 +40,8 @@ EXAMPLES To update storage location for the Logs Router for an organization, run: $ gcloud alpha logging settings update \ - --organization=[ORGANIZATION_ID] - --storage-location=[LOCATION_ID] + --organization=[ORGANIZATION_ID] \ + --storage-location=[LOCATION_ID] To update storage location for the Logs Router for a folder, run: diff --git a/gcloud/alpha/logging/sinks/create b/gcloud/alpha/logging/sinks/create index 109d59a28..c4a41d290 100644 --- a/gcloud/alpha/logging/sinks/create +++ b/gcloud/alpha/logging/sinks/create @@ -38,8 +38,9 @@ DESCRIPTION EXAMPLES To route all Google Compute Engine logs to BigQuery, run: - $ gcloud alpha logging sinks create my-bq-sink - bigquery.googleapis.com/projects/my-project/datasets/my_dataset --log-filter='resource.type="gce_instance"' + $ gcloud alpha logging sinks create my-bq-sink \ + bigquery.googleapis.com/projects/my-project/datasets/\ + my_dataset --log-filter='resource.type="gce_instance"' To route "syslog" from App Engine Flexible to a Cloud Storage bucket, run: @@ -50,13 +51,15 @@ EXAMPLES To route Google App Engine logs with ERROR severity, run: - $ gcloud alpha logging sinks create my-error-logs - bigquery.googleapis.com/projects/my-project/datasets/my_dataset --log-filter='resource.type="gae_app" AND severity=ERROR' + $ gcloud alpha logging sinks create my-error-logs \ + bigquery.googleapis.com/projects/my-project/datasets/\ + my_dataset --log-filter='resource.type="gae_app" AND severity=ERROR' To route all logs to a log bucket in a different project, run: - $ gcloud alpha logging sinks create my-sink - logging.googleapis.com/projects/my-central-project/locations/global/buckets/my-central-bucket + $ gcloud alpha logging sinks create my-sink \ + logging.googleapis.com/projects/my-central-project/locations/\ + global/buckets/my-central-bucket POSITIONAL ARGUMENTS SINK_NAME diff --git a/gcloud/alpha/logging/views/update b/gcloud/alpha/logging/views/update index 9f812e00a..6ea80f454 100644 --- a/gcloud/alpha/logging/views/update +++ b/gcloud/alpha/logging/views/update @@ -16,8 +16,7 @@ EXAMPLES To update a view in your project, run: $ gcloud alpha logging views update my-view --bucket=my-bucket \ - --location=global - --description=my-new-description + --location=global --description=my-new-description POSITIONAL ARGUMENTS VIEW_ID diff --git a/gcloud/alpha/memcache/instances/create b/gcloud/alpha/memcache/instances/create index 23d21b399..bd826892a 100644 --- a/gcloud/alpha/memcache/instances/create +++ b/gcloud/alpha/memcache/instances/create @@ -23,8 +23,8 @@ EXAMPLES 'us-central1' with 3 nodes, each with 2 CPUs and 2GB of memory, run: $ gcloud alpha memcache instances create my-memcache-instance \ - --region=us-central1 \ - --node-count=3 --node-cpu=2 --node-memory=2GB + --region=us-central1 --node-count=3 --node-cpu=2 \ + --node-memory=2GB POSITIONAL ARGUMENTS Instance resource - Arguments and flags that specify the Memcached diff --git a/gcloud/alpha/metastore/services/import/gcs b/gcloud/alpha/metastore/services/import/gcs index 5352d9424..566bc0b4b 100644 --- a/gcloud/alpha/metastore/services/import/gcs +++ b/gcloud/alpha/metastore/services/import/gcs @@ -24,7 +24,7 @@ EXAMPLES $ gcloud alpha metastore services import gcs my-service \ --import-id=my-import --description='testing description' \ - --dump-type=mysql --database-dump=gs://database-dump + --dump-type=mysql --database-dump=gs://database-dump POSITIONAL ARGUMENTS Service resource - Arguments and flags that specify the Dataproc Metastore diff --git a/gcloud/alpha/metastore/services/imports/create b/gcloud/alpha/metastore/services/imports/create index 35687df5d..50b763ee7 100644 --- a/gcloud/alpha/metastore/services/imports/create +++ b/gcloud/alpha/metastore/services/imports/create @@ -23,7 +23,7 @@ EXAMPLES $ gcloud alpha metastore services imports create my-import \ --service=my-service --description='testing description' \ - --database-type=mysql --database-dump=gs://database-dump + --database-type=mysql --database-dump=gs://database-dump POSITIONAL ARGUMENTS Import resource - Arguments and flags that specify the metadata import you diff --git a/gcloud/alpha/ml-engine/explain b/gcloud/alpha/ml-engine/explain index 02f392aec..baf2a59e4 100644 --- a/gcloud/alpha/ml-engine/explain +++ b/gcloud/alpha/ml-engine/explain @@ -18,7 +18,7 @@ EXAMPLES 'version' and with the name 'model-name', run: $ gcloud alpha ml-engine explain explain --model=model-name \ - --version=version --json-instances=instances.json + --version=version --json-instances=instances.json REQUIRED FLAGS --model=MODEL diff --git a/gcloud/alpha/ml-engine/models/delete b/gcloud/alpha/ml-engine/models/delete index 0b7324f3f..623373951 100644 --- a/gcloud/alpha/ml-engine/models/delete +++ b/gcloud/alpha/ml-engine/models/delete @@ -9,8 +9,8 @@ EXAMPLES To delete all models matching the regular expression vision[0-9]+, run: $ gcloud alpha ml-engine models list --uri \ - --filter 'name ~ vision[0-9]+' | - xargs -n 1 gcloud alpha ml-engine models delete + --filter 'name ~ vision[0-9]+' | xargs -n 1 gcloud alpha \ + ml-engine models delete POSITIONAL ARGUMENTS MODEL diff --git a/gcloud/alpha/ml/language/classify-text b/gcloud/alpha/ml/language/classify-text index 84b546b8a..4411921dd 100644 --- a/gcloud/alpha/ml/language/classify-text +++ b/gcloud/alpha/ml/language/classify-text @@ -32,7 +32,7 @@ EXAMPLES $ gcloud alpha ml language classify-text \ --content-file='gs://bucket_name/mycontent.html' \ - --content-type=HTML --language=ja-JP + --content-type=HTML --language=ja-JP REQUIRED FLAGS Exactly one of these must be specified: diff --git a/gcloud/alpha/ml/speech/recognize b/gcloud/alpha/ml/speech/recognize index cf392abf0..d2bdac7f1 100644 --- a/gcloud/alpha/ml/speech/recognize +++ b/gcloud/alpha/ml/speech/recognize @@ -42,8 +42,8 @@ EXAMPLES custom sampling rate and encoding that uses hints and filters profanity: $ gcloud alpha ml speech recognize 'gs://bucket/myaudio' \ - --language-code=es-ES --sample-rate=2200 --hints=Bueno \ - --encoding=OGG_OPUS --filter-profanity + --language-code=es-ES --sample-rate=2200 --hints=Bueno \ + --encoding=OGG_OPUS --filter-profanity POSITIONAL ARGUMENTS AUDIO @@ -117,6 +117,12 @@ OPTIONAL FLAGS audio that is not one of the specific audio models. For example, long-form audio. Ideally the audio is high-fidelity, recorded at a 16khz or greater sampling rate. + medical_conversation + Best for audio that originated from a conversation between a + medical provider and patient. + medical_dictation + Best for audio that originated from dictation notes by a medical + provider. phone_call audio that originated from a phone call (typically recorded at an 8khz sampling rate). diff --git a/gcloud/alpha/ml/speech/recognize-long-running b/gcloud/alpha/ml/speech/recognize-long-running index 6b0d4f3c7..ae8d10ba2 100644 --- a/gcloud/alpha/ml/speech/recognize-long-running +++ b/gcloud/alpha/ml/speech/recognize-long-running @@ -126,6 +126,12 @@ OPTIONAL FLAGS audio that is not one of the specific audio models. For example, long-form audio. Ideally the audio is high-fidelity, recorded at a 16khz or greater sampling rate. + medical_conversation + Best for audio that originated from a conversation between a + medical provider and patient. + medical_dictation + Best for audio that originated from dictation notes by a medical + provider. phone_call audio that originated from a phone call (typically recorded at an 8khz sampling rate). diff --git a/gcloud/alpha/ml/vision/detect-text-pdf b/gcloud/alpha/ml/vision/detect-text-pdf index 4a0a4e48b..db79f948b 100644 --- a/gcloud/alpha/ml/vision/detect-text-pdf +++ b/gcloud/alpha/ml/vision/detect-text-pdf @@ -19,8 +19,8 @@ EXAMPLES To detect text for input PDF file 'gs://my_bucket/input_file' and store output in 'gs://my_bucket/out_put_prefix': - $ gcloud alpha ml vision detect-text-pdf gs://my_bucket/input_file - gs://my_bucket/out_put_prefix + $ gcloud alpha ml vision detect-text-pdf gs://my_bucket/input_file \ + gs://my_bucket/out_put_prefix POSITIONAL ARGUMENTS INPUT_FILE diff --git a/gcloud/alpha/ml/vision/detect-text-tiff b/gcloud/alpha/ml/vision/detect-text-tiff index 948de7d07..2a2aa4335 100644 --- a/gcloud/alpha/ml/vision/detect-text-tiff +++ b/gcloud/alpha/ml/vision/detect-text-tiff @@ -19,8 +19,8 @@ EXAMPLES To detect text for input TIFF file gs://my_bucket/input_file and store output in gs://my_bucket/out_put_prefix: - $ gcloud alpha ml vision detect-text-tiff gs://my_bucket/input_file - gs://my_bucket/out_put_prefix + $ gcloud alpha ml vision detect-text-tiff \ + gs://my_bucket/input_file gs://my_bucket/out_put_prefix POSITIONAL ARGUMENTS INPUT_FILE diff --git a/gcloud/alpha/monitoring/channels/create b/gcloud/alpha/monitoring/channels/create index bf5ff37ff..3613e2e6f 100644 --- a/gcloud/alpha/monitoring/channels/create +++ b/gcloud/alpha/monitoring/channels/create @@ -34,18 +34,16 @@ EXAMPLES existing channels. It is also a best practice to supply at least two channels of different types for a given person. - $ gcloud alpha monitoring channels create \ - --display-name="Foo Team Lead (Primary)" \ - --description="Primary contact method for the Foo team lead" \ - --type=email \ - --user-labels=team=foo,role=lead,ord=1 \ + $ gcloud alpha monitoring channels create \ + --display-name="Foo Team Lead (Primary)" \ + --description="Primary contact method for the Foo team lead" \ + --type=email --user-labels=team=foo,role=lead,ord=1 \ --channel-labels=email_address=user@somedomain.tld - $ gcloud alpha monitoring channels create \ - --display-name="Foo Team Lead (Secondary)" \ + $ gcloud alpha monitoring channels create \ + --display-name="Foo Team Lead (Secondary)" \ --description="Secondary contact method for the Foo team lead" \ - --type=sms \ - --user-labels=team=foo,role=lead,ord=2 \ + --type=sms --user-labels=team=foo,role=lead,ord=2 \ --channel-labels=number=123-456-7890 FLAGS diff --git a/gcloud/alpha/monitoring/channels/list b/gcloud/alpha/monitoring/channels/list index ca0744845..e392f001e 100644 --- a/gcloud/alpha/monitoring/channels/list +++ b/gcloud/alpha/monitoring/channels/list @@ -21,10 +21,9 @@ EXAMPLES The following command lists all of the email addresses alphabetically: - $ gcloud alpha monitoring channels list \ - --filter='type="email"' \ - --sort-by=labels.email_address \ - --format="value(labels.email_address)" + $ gcloud alpha monitoring channels list --filter='type="email"' \ + --sort-by=labels.email_address \ + --format="value(labels.email_address)" FLAGS --type=TYPE diff --git a/gcloud/alpha/monitoring/channels/update b/gcloud/alpha/monitoring/channels/update index 4d5c94f18..687ec2574 100644 --- a/gcloud/alpha/monitoring/channels/update +++ b/gcloud/alpha/monitoring/channels/update @@ -36,7 +36,7 @@ EXAMPLES point from its original email address to "newaddress@newdomain.tld": $ gcloud alpha monitoring channels update \ - "projects/12345/notificationChannels/67890" \ + "projects/12345/notificationChannels/67890" \ --update-channel-labels=email_address=newaddress@newdomain.tld POSITIONAL ARGUMENTS diff --git a/gcloud/alpha/network-connectivity/internal-ranges/create b/gcloud/alpha/network-connectivity/internal-ranges/create index 0ad425b1c..f27a8ce84 100644 --- a/gcloud/alpha/network-connectivity/internal-ranges/create +++ b/gcloud/alpha/network-connectivity/internal-ranges/create @@ -20,20 +20,18 @@ EXAMPLES https://www.googleapis.com/compute/v1/projects/my-project/locations/global/networks/my-network and region global: - $ gcloud alpha network-connectivity internal-ranges create my-range - --ip-cidr-range="192.168.0.0/25" - --network="https://www.googleapis.com/compute/v1/projects/my-project/locations/global/networks/my-network" - --project=my-project - --region=global + $ gcloud alpha network-connectivity internal-ranges create \ + my-range --ip-cidr-range="192.168.0.0/25" \ + --network="https://www.googleapis.com/compute/v1/projects/my-pro\ + ject/locations/global/networks/my-network" --project=my-project \ + --region=global Create an internal range with name my-range and auto-allocated /25 block (prefix-length 25) in network my-network and region global: - $ gcloud alpha network-connectivity internal-ranges create my-range - --prefix-length=25 - --network="my-network" - --project=my-project - --region=global + $ gcloud alpha network-connectivity internal-ranges create \ + my-range --prefix-length=25 --network="my-network" \ + --project=my-project --region=global POSITIONAL ARGUMENTS Internal range resource - Name of the internal range to be created. The diff --git a/gcloud/alpha/network-connectivity/internal-ranges/update b/gcloud/alpha/network-connectivity/internal-ranges/update index 507bc89a9..6741dc809 100644 --- a/gcloud/alpha/network-connectivity/internal-ranges/update +++ b/gcloud/alpha/network-connectivity/internal-ranges/update @@ -15,18 +15,15 @@ EXAMPLES Update ip-cidr-range of an internal range named my-range in project my-project and region global: - $ gcloud alpha network-connectivity internal-ranges update my-range - --ip-cidr-range="192.168.0.0/24" - --project=my-project - --region=global + $ gcloud alpha network-connectivity internal-ranges update \ + my-range --ip-cidr-range="192.168.0.0/24" --project=my-project \ + --region=global Extend an internal range named my-range in project my-project and region global to an address block of /24: - $ gcloud alpha network-connectivity internal-ranges update my-range - --prefix-length=24 - --project=my-project - --region=global + $ gcloud alpha network-connectivity internal-ranges update \ + my-range --prefix-length=24 --project=my-project --region=global POSITIONAL ARGUMENTS Internal range resource - Name of the internal range to be created. The diff --git a/gcloud/alpha/network-connectivity/policy-based-routes/create b/gcloud/alpha/network-connectivity/policy-based-routes/create index 763d5e274..149da8fe5 100644 --- a/gcloud/alpha/network-connectivity/policy-based-routes/create +++ b/gcloud/alpha/network-connectivity/policy-based-routes/create @@ -22,8 +22,8 @@ EXAMPLES in default network to a ilb with vip 10.0.0.1, run: $ gcloud alpha network-connectivity policy-based-routes create \ - my-pbr --network="projects/my-project/global/networks/default" - --next-hop-ilb-ip=10.0.0.1 + my-pbr --network="projects/my-project/global/networks/default" \ + --next-hop-ilb-ip=10.0.0.1 POSITIONAL ARGUMENTS Policy based route resource - Name of the policy based route to be diff --git a/gcloud/alpha/policy-troubleshoot/iam b/gcloud/alpha/policy-troubleshoot/iam index 9ba8c77b5..95e076b00 100644 --- a/gcloud/alpha/policy-troubleshoot/iam +++ b/gcloud/alpha/policy-troubleshoot/iam @@ -17,9 +17,9 @@ EXAMPLES To troubleshoot a permission of a principal on a resource, run: $ gcloud alpha policy-troubleshoot iam \ - //cloudresourcemanager.googleapis.com/projects/project-id - --principal-email=my-iam-account@somedomain.com - --permission=resourcemanager.projects.get + //cloudresourcemanager.googleapis.com/projects/project-id \ + --principal-email=my-iam-account@somedomain.com \ + --permission=resourcemanager.projects.get See https://cloud.google.com/iam/docs/policies for more information about IAM policies. @@ -29,12 +29,14 @@ EXAMPLES $ gcloud alpha policy-troubleshoot iam \ //cloudresourcemanager.googleapis.com/projects/project-id \ - --principal-email=my-iam-account@somedomain.com \ - --permission=resourcemanager.projects.get \ - --resource-name=//compute.googleapis.com/projects/{project-id}/global/images/{image-id}'\ - --resource-service='compute.googleapis.com' \ - --resource-type='compute.googleapis.com/Image' \ - --destination-ip='192.2.2.2'--destination-port=8080 --request-time='2021-01-01T00:00:00Z' + --principal-email=my-iam-account@somedomain.com \ + --permission=resourcemanager.projects.get \ + --resource-name=//compute.googleapis.com/projects/{project-id}/\ + global/images/\ + {image-id}'--resource-service='compute.googleapis.com' + --resource-type='compute.googleapis.com/Image' \ + --destination-ip='192.2.2.2'--destination-port=8080 \ + --request-time='2021-01-01T00:00:00Z' See https://cloud.google.com/iam/docs/policies for more information about IAM policies. diff --git a/gcloud/alpha/pubsub/lite-reservations/create b/gcloud/alpha/pubsub/lite-reservations/create index 4df743001..427a9dcea 100644 --- a/gcloud/alpha/pubsub/lite-reservations/create +++ b/gcloud/alpha/pubsub/lite-reservations/create @@ -14,8 +14,7 @@ EXAMPLES To create a Pub/Sub lite-reservation, run: $ gcloud alpha pubsub lite-reservations create myreservation \ - --location=us-central1 \ - --throughput-capacity=2 + --location=us-central1 --throughput-capacity=2 POSITIONAL ARGUMENTS RESERVATION diff --git a/gcloud/alpha/pubsub/lite-reservations/delete b/gcloud/alpha/pubsub/lite-reservations/delete index 9a2608d54..7bea405b7 100644 --- a/gcloud/alpha/pubsub/lite-reservations/delete +++ b/gcloud/alpha/pubsub/lite-reservations/delete @@ -13,7 +13,7 @@ EXAMPLES To delete a Pub/Sub Lite reservation, run: $ gcloud alpha pubsub lite-reservations delete myreservation \ - --location=us-central1 + --location=us-central1 POSITIONAL ARGUMENTS Reservation resource - Reservation to delete. The arguments in this group diff --git a/gcloud/alpha/pubsub/lite-reservations/describe b/gcloud/alpha/pubsub/lite-reservations/describe index 92f9bd160..5d9e3deff 100644 --- a/gcloud/alpha/pubsub/lite-reservations/describe +++ b/gcloud/alpha/pubsub/lite-reservations/describe @@ -13,7 +13,7 @@ EXAMPLES To describe a Pub/Sub Lite reservation, run: $ gcloud alpha pubsub lite-reservations describe myreservation \ - --location=us-central1 + --location=us-central1 POSITIONAL ARGUMENTS Reservation resource - Reservation to describe. The arguments in this diff --git a/gcloud/alpha/pubsub/lite-reservations/list b/gcloud/alpha/pubsub/lite-reservations/list index 2d1da39e7..61c84e168 100644 --- a/gcloud/alpha/pubsub/lite-reservations/list +++ b/gcloud/alpha/pubsub/lite-reservations/list @@ -12,8 +12,8 @@ DESCRIPTION EXAMPLES To list Pub/Sub Lite reservations, run: - $ gcloud alpha pubsub lite-reservations list --location=us-central1 \ - --limit=5 + $ gcloud alpha pubsub lite-reservations list \ + --location=us-central1 --limit=5 REQUIRED FLAGS Location resource - Location to list reservations for. This represents a diff --git a/gcloud/alpha/pubsub/lite-reservations/list-topics b/gcloud/alpha/pubsub/lite-reservations/list-topics index 91a842141..fa1215eb3 100644 --- a/gcloud/alpha/pubsub/lite-reservations/list-topics +++ b/gcloud/alpha/pubsub/lite-reservations/list-topics @@ -15,7 +15,7 @@ EXAMPLES To list Pub/Sub Lite topics for a given Lite reservation, run: $ gcloud alpha pubsub lite-reservations list-topics myreservation \ - --location=us-central1 + --location=us-central1 POSITIONAL ARGUMENTS Reservation resource - Reservation to list topics for. The arguments in diff --git a/gcloud/alpha/pubsub/lite-reservations/update b/gcloud/alpha/pubsub/lite-reservations/update index fa399245f..f26046770 100644 --- a/gcloud/alpha/pubsub/lite-reservations/update +++ b/gcloud/alpha/pubsub/lite-reservations/update @@ -14,8 +14,7 @@ EXAMPLES To update a Pub/Sub Lite reservation, run: $ gcloud alpha pubsub lite-reservations update myreservation \ - --location=us-central1 \ - --throughput-capacity=2 + --location=us-central1 --throughput-capacity=2 POSITIONAL ARGUMENTS Reservation resource - Reservation to update. The arguments in this group diff --git a/gcloud/alpha/pubsub/lite-subscriptions/ack-up-to b/gcloud/alpha/pubsub/lite-subscriptions/ack-up-to index 2b10bb907..f106d8c62 100644 --- a/gcloud/alpha/pubsub/lite-subscriptions/ack-up-to +++ b/gcloud/alpha/pubsub/lite-subscriptions/ack-up-to @@ -16,9 +16,7 @@ EXAMPLES To acknowledge messages on a Pub/Sub Lite subscription, run: $ gcloud alpha pubsub lite-subscriptions ack-up-to mysubscription \ - --location=us-central1-a \ - --partition=0 \ - --offset=10 + --location=us-central1-a --partition=0 --offset=10 POSITIONAL ARGUMENTS Subscription resource - Subscription on which to acknowledge messages. The diff --git a/gcloud/alpha/pubsub/lite-subscriptions/create b/gcloud/alpha/pubsub/lite-subscriptions/create index 42800559c..b35287371 100644 --- a/gcloud/alpha/pubsub/lite-subscriptions/create +++ b/gcloud/alpha/pubsub/lite-subscriptions/create @@ -16,16 +16,14 @@ EXAMPLES To create a Pub/Sub Lite subscription, run: $ gcloud alpha pubsub lite-subscriptions create mysubscription \ - --location=us-central1-a \ - --topic=mytopic + --location=us-central1-a --topic=mytopic To create a Pub/Sub Lite subscription at the offset of the oldest retained message, run: $ gcloud alpha pubsub lite-subscriptions create mysubscription \ - --location=us-central1-a \ - --topic=mytopic \ - --starting-offset=beginning + --location=us-central1-a --topic=mytopic \ + --starting-offset=beginning POSITIONAL ARGUMENTS SUBSCRIPTION diff --git a/gcloud/alpha/pubsub/lite-subscriptions/delete b/gcloud/alpha/pubsub/lite-subscriptions/delete index d8023d46c..23776fe67 100644 --- a/gcloud/alpha/pubsub/lite-subscriptions/delete +++ b/gcloud/alpha/pubsub/lite-subscriptions/delete @@ -13,7 +13,7 @@ EXAMPLES To delete a Pub/Sub Lite subscription, run: $ gcloud alpha pubsub lite-subscriptions delete mysubscription \ - --location=us-central1-a + --location=us-central1-a POSITIONAL ARGUMENTS Subscription resource - Subscription to delete. The arguments in this diff --git a/gcloud/alpha/pubsub/lite-subscriptions/describe b/gcloud/alpha/pubsub/lite-subscriptions/describe index 5cb84509c..b52004b76 100644 --- a/gcloud/alpha/pubsub/lite-subscriptions/describe +++ b/gcloud/alpha/pubsub/lite-subscriptions/describe @@ -13,7 +13,7 @@ EXAMPLES To describe a Pub/Sub Lite subscription, run: $ gcloud alpha pubsub lite-subscriptions describe mysubscription \ - --location=us-central1-a + --location=us-central1-a POSITIONAL ARGUMENTS Subscription resource - Subscription to describe. The arguments in this diff --git a/gcloud/alpha/pubsub/lite-subscriptions/list b/gcloud/alpha/pubsub/lite-subscriptions/list index b9f586861..c7735eb48 100644 --- a/gcloud/alpha/pubsub/lite-subscriptions/list +++ b/gcloud/alpha/pubsub/lite-subscriptions/list @@ -14,8 +14,7 @@ EXAMPLES To list Pub/Sub Lite subscriptions, run: $ gcloud alpha pubsub lite-subscriptions list \ - --location=us-central1-a \ - --limit=5 + --location=us-central1-a --limit=5 FLAGS Location resource - ID of the location or fully qualified identifier for diff --git a/gcloud/alpha/pubsub/lite-subscriptions/seek b/gcloud/alpha/pubsub/lite-subscriptions/seek index d7e0c9fdc..b90eb432a 100644 --- a/gcloud/alpha/pubsub/lite-subscriptions/seek +++ b/gcloud/alpha/pubsub/lite-subscriptions/seek @@ -24,16 +24,14 @@ EXAMPLES backlog, run: $ gcloud alpha pubsub lite-subscriptions seek mysubscription \ - --location=us-central1-a \ - --starting-offset=beginning + --location=us-central1-a --starting-offset=beginning To seek a Pub/Sub Lite subscription to a publish time without waiting for the operation to complete, run: $ gcloud alpha pubsub lite-subscriptions seek mysubscription \ - --location=us-central1-a \ - --publish-time="2021-01-01T12:00:00Z" - --async + --location=us-central1-a --publish-time="2021-01-01T12:00:00Z" \ + --async POSITIONAL ARGUMENTS Subscription resource - Subscription to seek. The arguments in this group diff --git a/gcloud/alpha/pubsub/lite-subscriptions/update b/gcloud/alpha/pubsub/lite-subscriptions/update index 5eed68584..9cfd83d0b 100644 --- a/gcloud/alpha/pubsub/lite-subscriptions/update +++ b/gcloud/alpha/pubsub/lite-subscriptions/update @@ -14,8 +14,8 @@ EXAMPLES To update a Cloud Pub/Sub lite-subscription, run: $ gcloud alpha pubsub lite-subscriptions update mysubscription \ - --location=us-central1-a \ - --delivery-requirement=DELIVER_IMMEDIATELY + --location=us-central1-a \ + --delivery-requirement=DELIVER_IMMEDIATELY POSITIONAL ARGUMENTS Subscription resource - Subscription to update. The arguments in this diff --git a/gcloud/alpha/pubsub/lite-topics/create b/gcloud/alpha/pubsub/lite-topics/create index 6fff18a04..e28cc5192 100644 --- a/gcloud/alpha/pubsub/lite-topics/create +++ b/gcloud/alpha/pubsub/lite-topics/create @@ -17,10 +17,8 @@ EXAMPLES To create a Pub/Sub lite-topic, run: $ gcloud alpha pubsub lite-topics create mytopic \ - --location=us-central1-a \ - --partitions=1 \ - --per-partition-bytes=30GiB \ - --message-retention-period=2w + --location=us-central1-a --partitions=1 \ + --per-partition-bytes=30GiB --message-retention-period=2w POSITIONAL ARGUMENTS TOPIC diff --git a/gcloud/alpha/pubsub/lite-topics/delete b/gcloud/alpha/pubsub/lite-topics/delete index 1b2d408e2..396a7ba9e 100644 --- a/gcloud/alpha/pubsub/lite-topics/delete +++ b/gcloud/alpha/pubsub/lite-topics/delete @@ -12,7 +12,7 @@ EXAMPLES To delete a Pub/Sub Lite topic, run: $ gcloud alpha pubsub lite-topics delete mytopic \ - --location=us-central1-a + --location=us-central1-a POSITIONAL ARGUMENTS Topic resource - Topic to delete. The arguments in this group can be used diff --git a/gcloud/alpha/pubsub/lite-topics/describe b/gcloud/alpha/pubsub/lite-topics/describe index f0c890962..b4e7eb315 100644 --- a/gcloud/alpha/pubsub/lite-topics/describe +++ b/gcloud/alpha/pubsub/lite-topics/describe @@ -12,7 +12,7 @@ EXAMPLES To describe a Pub/Sub Lite topic, run: $ gcloud alpha pubsub lite-topics describe mytopic \ - --location=us-central1-a + --location=us-central1-a POSITIONAL ARGUMENTS Topic resource - Topic to describe. The arguments in this group can be diff --git a/gcloud/alpha/pubsub/lite-topics/list b/gcloud/alpha/pubsub/lite-topics/list index b5f4db18c..329b8efe6 100644 --- a/gcloud/alpha/pubsub/lite-topics/list +++ b/gcloud/alpha/pubsub/lite-topics/list @@ -13,7 +13,7 @@ EXAMPLES To list Pub/Sub Lite topics, run: $ gcloud alpha pubsub lite-topics list --location=us-central1-a \ - --limit=5 + --limit=5 FLAGS Location resource - Zone to list topics for. This represents a Cloud diff --git a/gcloud/alpha/pubsub/lite-topics/list-subscriptions b/gcloud/alpha/pubsub/lite-topics/list-subscriptions index d432644d1..36e225075 100644 --- a/gcloud/alpha/pubsub/lite-topics/list-subscriptions +++ b/gcloud/alpha/pubsub/lite-topics/list-subscriptions @@ -14,7 +14,7 @@ EXAMPLES To list Pub/Sub Lite subscriptions for a given Lite topic, run: $ gcloud alpha pubsub lite-topics list-subscriptions mytopic \ - --location=us-central1-a + --location=us-central1-a POSITIONAL ARGUMENTS Topic resource - Topic to list subscriptions for. The arguments in this diff --git a/gcloud/alpha/pubsub/lite-topics/update b/gcloud/alpha/pubsub/lite-topics/update index 4fbe2724f..ba0b270bc 100644 --- a/gcloud/alpha/pubsub/lite-topics/update +++ b/gcloud/alpha/pubsub/lite-topics/update @@ -17,8 +17,7 @@ EXAMPLES To update a Pub/Sub Lite topic, run: $ gcloud alpha pubsub lite-topics update mytopic \ - --location=us-central1-a \ - --per-partition-publish-mib=10 + --location=us-central1-a --per-partition-publish-mib=10 POSITIONAL ARGUMENTS Topic resource - Topic to update. The arguments in this group can be used diff --git a/gcloud/alpha/pubsub/subscriptions/add-iam-policy-binding b/gcloud/alpha/pubsub/subscriptions/add-iam-policy-binding index b673ca268..abe8ad615 100644 --- a/gcloud/alpha/pubsub/subscriptions/add-iam-policy-binding +++ b/gcloud/alpha/pubsub/subscriptions/add-iam-policy-binding @@ -27,8 +27,8 @@ EXAMPLES $ gcloud alpha pubsub subscriptions add-iam-policy-binding \ my-subscription \ - --member='serviceAccount:my-iam-account@my-project.iam.gserviceaccount.com' \ - --role='roles/editor' + --member='serviceAccount:my-iam-account@my-project.iam.gservicea\ + ccount.com' --role='roles/editor' To add an IAM policy binding which expires at the end of the year 2018 for the role of 'roles/pubsub.subscriber' and the user 'test-user@example.com' diff --git a/gcloud/alpha/pubsub/subscriptions/create b/gcloud/alpha/pubsub/subscriptions/create index ddbb14d2f..c1228a7b8 100644 --- a/gcloud/alpha/pubsub/subscriptions/create +++ b/gcloud/alpha/pubsub/subscriptions/create @@ -5,9 +5,9 @@ NAME SYNOPSIS gcloud alpha pubsub subscriptions create SUBSCRIPTION [SUBSCRIPTION ...] (--topic=TOPIC : --topic-project=TOPIC_PROJECT) - [--ack-deadline=ACK_DEADLINE] [--enable-message-ordering] - [--expiration-period=EXPIRATION_PERIOD] [--labels=[KEY=VALUE,...]] - [--message-filter=MESSAGE_FILTER] + [--ack-deadline=ACK_DEADLINE] [--enable-exactly-once-delivery] + [--enable-message-ordering] [--expiration-period=EXPIRATION_PERIOD] + [--labels=[KEY=VALUE,...]] [--message-filter=MESSAGE_FILTER] [--message-retention-duration=MESSAGE_RETENTION_DURATION] [--push-auth-service-account=SERVICE_ACCOUNT_EMAIL] [--push-auth-token-audience=OPTIONAL_AUDIENCE_OVERRIDE] @@ -70,6 +70,14 @@ OPTIONAL FLAGS The number of seconds the system will wait for a subscriber to acknowledge receiving a message before re-attempting delivery. + --enable-exactly-once-delivery + Whether or not to enble exactly once delivery on the subscription. If + true, Pub/Sub provides the following guarantees for the delivery of a + message with a given value of message_id on this subscription: The + message sent to a subscriber is guaranteed not to be resent before the + message's acknowledgement deadline expires. An acknowledged message + will not be resent to a subscriber. + --enable-message-ordering Whether to receive messages with the same ordering key in order. If set, messages with the same ordering key are sent to subscribers in the diff --git a/gcloud/alpha/pubsub/subscriptions/update b/gcloud/alpha/pubsub/subscriptions/update index 5e4626197..55d347d65 100644 --- a/gcloud/alpha/pubsub/subscriptions/update +++ b/gcloud/alpha/pubsub/subscriptions/update @@ -4,7 +4,8 @@ NAME SYNOPSIS gcloud alpha pubsub subscriptions update SUBSCRIPTION - [--ack-deadline=ACK_DEADLINE] [--expiration-period=EXPIRATION_PERIOD] + [--ack-deadline=ACK_DEADLINE] [--enable-exactly-once-delivery] + [--expiration-period=EXPIRATION_PERIOD] [--message-retention-duration=MESSAGE_RETENTION_DURATION] [--push-auth-service-account=SERVICE_ACCOUNT_EMAIL] [--push-auth-token-audience=OPTIONAL_AUDIENCE_OVERRIDE] @@ -43,6 +44,14 @@ FLAGS The number of seconds the system will wait for a subscriber to acknowledge receiving a message before re-attempting delivery. + --enable-exactly-once-delivery + Whether or not to enble exactly once delivery on the subscription. If + true, Pub/Sub provides the following guarantees for the delivery of a + message with a given value of message_id on this subscription: The + message sent to a subscriber is guaranteed not to be resent before the + message's acknowledgement deadline expires. An acknowledged message + will not be resent to a subscriber. + --expiration-period=EXPIRATION_PERIOD The subscription will expire if it is inactive for the given period. Valid values are strings of the form INTEGER[UNIT], where UNIT is one diff --git a/gcloud/alpha/recommender/recommendations/describe b/gcloud/alpha/recommender/recommendations/describe index b2918f2be..8f662e867 100644 --- a/gcloud/alpha/recommender/recommendations/describe +++ b/gcloud/alpha/recommender/recommendations/describe @@ -17,8 +17,8 @@ EXAMPLES To describe a recommendation: $ gcloud alpha recommender recommendations describe \ - RECOMMENDATION_ID --project=${PROJECT} --location=${LOCATION} - --recommender=${RECOMMENDER} + RECOMMENDATION_ID --project=${PROJECT} --location=${LOCATION} \ + --recommender=${RECOMMENDER} POSITIONAL ARGUMENTS RECOMMENDATION diff --git a/gcloud/alpha/recommender/recommendations/list b/gcloud/alpha/recommender/recommendations/list index a3b3e82b8..b23038001 100644 --- a/gcloud/alpha/recommender/recommendations/list +++ b/gcloud/alpha/recommender/recommendations/list @@ -11,7 +11,7 @@ SYNOPSIS [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) This command will list all recommendations for a give + (ALPHA) This command will list all recommendations for a given cloud_entity_id, location and recommender. Supported recommenders can be found here: https://cloud.google.com/recommender/docs/recommenders. Currently the following cloud_entity_types are supported: project, diff --git a/gcloud/alpha/recommender/recommendations/mark-active b/gcloud/alpha/recommender/recommendations/mark-active index b686d3b94..d57ff4e47 100644 --- a/gcloud/alpha/recommender/recommendations/mark-active +++ b/gcloud/alpha/recommender/recommendations/mark-active @@ -18,8 +18,8 @@ EXAMPLES To mark a recommenation as ACTIVE: $ gcloud alpha recommender recommendations mark-active \ - RECOMMENDATION_ID --project=${PROJECT} --location=${LOCATION} - --recommender=${RECOMMENDER} --etag=etag + RECOMMENDATION_ID --project=${PROJECT} --location=${LOCATION} \ + --recommender=${RECOMMENDER} --etag=etag POSITIONAL ARGUMENTS RECOMMENDATION diff --git a/gcloud/alpha/recommender/recommendations/mark-claimed b/gcloud/alpha/recommender/recommendations/mark-claimed index c4d8495db..a13f5368e 100644 --- a/gcloud/alpha/recommender/recommendations/mark-claimed +++ b/gcloud/alpha/recommender/recommendations/mark-claimed @@ -20,9 +20,9 @@ EXAMPLES To mark a recommendation as CLAIMED: $ gcloud alpha recommender recommendations mark-claimed \ - RECOMMENDATION --project=project-name --location=global - --recommender=google.compute.instance.MachineTypeRecommender --etag=abc123 - --state-metadata=key1=value1,key2=value2 + RECOMMENDATION --project=project-name --location=global \ + --recommender=google.compute.instance.MachineTypeRecommender \ + --etag=abc123 --state-metadata=key1=value1,key2=value2 POSITIONAL ARGUMENTS RECOMMENDATION diff --git a/gcloud/alpha/recommender/recommendations/mark-dismissed b/gcloud/alpha/recommender/recommendations/mark-dismissed index f60486f84..ed7ba3b75 100644 --- a/gcloud/alpha/recommender/recommendations/mark-dismissed +++ b/gcloud/alpha/recommender/recommendations/mark-dismissed @@ -19,8 +19,9 @@ EXAMPLES To mark a recommendation as DISMISSED: $ gcloud alpha recommender recommendations mark-dismissed \ - abcd-1234 --project=project-name --location=global - --recommender=google.compute.instance.MachineTypeRecommender --etag=abc123 + abcd-1234 --project=project-name --location=global \ + --recommender=google.compute.instance.MachineTypeRecommender \ + --etag=abc123 POSITIONAL ARGUMENTS RECOMMENDATION diff --git a/gcloud/alpha/resource-config/terraform/init-provider b/gcloud/alpha/resource-config/terraform/init-provider index f7cb350d0..c420775ce 100644 --- a/gcloud/alpha/resource-config/terraform/init-provider +++ b/gcloud/alpha/resource-config/terraform/init-provider @@ -22,7 +22,7 @@ EXAMPLES To generate a main.tf file in the current directory using the user suppplied values for zone, region and project run: - $ gcloud alpha resource-config terraform init-provider \ + $ gcloud alpha resource-config terraform init-provider \ --project="my-project-id" --region="us-central1" \ --zone="us-central1-c diff --git a/gcloud/alpha/resource-manager/tags/keys/create b/gcloud/alpha/resource-manager/tags/keys/create index 2575fa6ec..5f3ebf367 100644 --- a/gcloud/alpha/resource-manager/tags/keys/create +++ b/gcloud/alpha/resource-manager/tags/keys/create @@ -12,8 +12,7 @@ EXAMPLES description 'description', run: $ gcloud alpha resource-manager tags keys create env \ - --parent=organizations/123 - --description=description + --parent=organizations/123 --description=description POSITIONAL ARGUMENTS TagKey. diff --git a/gcloud/alpha/resource-manager/tags/values/create b/gcloud/alpha/resource-manager/tags/values/create index ad711b539..85124347f 100644 --- a/gcloud/alpha/resource-manager/tags/values/create +++ b/gcloud/alpha/resource-manager/tags/values/create @@ -19,15 +19,13 @@ EXAMPLES 'organizations/123', run: $ gcloud alpha resource-manager tags values create test \ - --parent=123/env - --description=description + --parent=123/env --description=description To create a TagValue with the short name 'test' under TagKey with id '456', run: $ gcloud alpha resource-manager tags values create test \ - --parent=tagKeys/456 - --description=description + --parent=tagKeys/456 --description=description POSITIONAL ARGUMENTS TagValue. diff --git a/gcloud/alpha/scc/findings/list b/gcloud/alpha/scc/findings/list index f54511f68..e05ea3a34 100644 --- a/gcloud/alpha/scc/findings/list +++ b/gcloud/alpha/scc/findings/list @@ -35,7 +35,7 @@ EXAMPLES Only list category and resource_name of all ACTIVE findings under organization 123456 and source 5678: - $ gcloud alpha scc findings list 123456 --source=5678 \ + $ gcloud alpha scc findings list 123456 --source=5678 \ --filter="state=\"ACTIVE\"" \ --field-mask="finding.category,finding.resource_name" diff --git a/gcloud/alpha/scc/settings/services/disable b/gcloud/alpha/scc/settings/services/disable index ad58b0abe..3497bc75c 100644 --- a/gcloud/alpha/scc/settings/services/disable +++ b/gcloud/alpha/scc/settings/services/disable @@ -13,7 +13,7 @@ DESCRIPTION EXAMPLES To disable WEB_SECURITY_SCANNER of organization id="12345", run: - $ gcloud alpha scc settings services disable --organization=12345 \ + $ gcloud alpha scc settings services disable --organization=12345 \ --service=WEB_SECURITY_SCANNER REQUIRED FLAGS diff --git a/gcloud/alpha/scc/settings/services/enable b/gcloud/alpha/scc/settings/services/enable index 82c515b38..e0d0d02de 100644 --- a/gcloud/alpha/scc/settings/services/enable +++ b/gcloud/alpha/scc/settings/services/enable @@ -13,7 +13,7 @@ DESCRIPTION EXAMPLES To enable WEB_SECURITY_SCANNER of organization id="12345", run: - $ gcloud alpha scc settings services enable --organization=12345 \ + $ gcloud alpha scc settings services enable --organization=12345 \ --service=WEB_SECURITY_SCANNER REQUIRED FLAGS diff --git a/gcloud/alpha/scc/settings/services/inherit b/gcloud/alpha/scc/settings/services/inherit index 7e3e86fc0..678306b1e 100644 --- a/gcloud/alpha/scc/settings/services/inherit +++ b/gcloud/alpha/scc/settings/services/inherit @@ -14,7 +14,7 @@ EXAMPLES To set WEB_SECURITY_SCANNER enablement state to "inherited" for folder "12345", run: - $ gcloud alpha scc settings services inherit --folder=12345 \ + $ gcloud alpha scc settings services inherit --folder=12345 \ --service=WEB_SECURITY_SCANNER REQUIRED FLAGS diff --git a/gcloud/alpha/scc/settings/services/modules/disable b/gcloud/alpha/scc/settings/services/modules/disable index 9824e7e00..a5a3ca8dc 100644 --- a/gcloud/alpha/scc/settings/services/modules/disable +++ b/gcloud/alpha/scc/settings/services/modules/disable @@ -16,7 +16,7 @@ EXAMPLES SECURITY_HEALTH_ANALYTICS of organization "12345", run: $ gcloud alpha scc settings services modules disable \ - --organization=12345 --service=SECURITY_HEALTH_ANALYTICS \ + --organization=12345 --service=SECURITY_HEALTH_ANALYTICS \ --module=PUBLIC_BUCKET_ACL REQUIRED FLAGS diff --git a/gcloud/alpha/scc/settings/services/modules/enable b/gcloud/alpha/scc/settings/services/modules/enable index 6b4854569..a92f61fe5 100644 --- a/gcloud/alpha/scc/settings/services/modules/enable +++ b/gcloud/alpha/scc/settings/services/modules/enable @@ -16,7 +16,7 @@ EXAMPLES SECURITY_HEALTH_ANALYTICS of organization "12345", run: $ gcloud alpha scc settings services modules enable \ - --organization=12345 --service=SECURITY_HEALTH_ANALYTICS \ + --organization=12345 --service=SECURITY_HEALTH_ANALYTICS \ --module=PUBLIC_BUCKET_ACL REQUIRED FLAGS diff --git a/gcloud/alpha/scc/settings/services/modules/update b/gcloud/alpha/scc/settings/services/modules/update index 197a9e241..8796617ca 100644 --- a/gcloud/alpha/scc/settings/services/modules/update +++ b/gcloud/alpha/scc/settings/services/modules/update @@ -17,7 +17,7 @@ EXAMPLES EVENT_THREAT_DETECTION of organization "12345", run: $ gcloud alpha scc settings services modules update \ - --organization=12345 --service=EVENT_THREAT_DETECTION \ + --organization=12345 --service=EVENT_THREAT_DETECTION \ --module=CONFIGURABLE_BAD_DOMAIN --enablement-state=ENABLED \ --config='{ "domains": { @@ -37,7 +37,7 @@ EXAMPLES organization "12345", run: $ gcloud alpha scc settings services modules update \ - --organization=12345 --service=EVENT_THREAT_DETECTION \ + --organization=12345 --service=EVENT_THREAT_DETECTION \ --module=CONFIGURABLE_BAD_DOMAIN --enablement-state=DISABLED \ --clear-config diff --git a/gcloud/alpha/scheduler/jobs/create/app-engine b/gcloud/alpha/scheduler/jobs/create/app-engine index bd3d9812f..4efd277d2 100644 --- a/gcloud/alpha/scheduler/jobs/create/app-engine +++ b/gcloud/alpha/scheduler/jobs/create/app-engine @@ -26,8 +26,7 @@ EXAMPLES '/cron-handler' path in you App Engine app every 3 hours: $ gcloud alpha scheduler jobs create app-engine my-job \ - --schedule="0 */3 * * *" - --relative-url="/cron-handler" + --schedule="0 */3 * * *" --relative-url="/cron-handler" POSITIONAL ARGUMENTS Job resource - Job to create. The arguments in this group can be used to diff --git a/gcloud/alpha/scheduler/jobs/create/http b/gcloud/alpha/scheduler/jobs/create/http index 271f0cb96..6972d955e 100644 --- a/gcloud/alpha/scheduler/jobs/create/http +++ b/gcloud/alpha/scheduler/jobs/create/http @@ -28,8 +28,8 @@ EXAMPLES 'http://example.com/path' every 3 hours: $ gcloud alpha scheduler jobs create http my-job \ - --schedule="0 */3 * * *" - --uri="http://example.com/path" --http-method=GET + --schedule="0 */3 * * *" --uri="http://example.com/path" \ + --http-method=GET POSITIONAL ARGUMENTS Job resource - Job to create. The arguments in this group can be used to diff --git a/gcloud/alpha/scheduler/jobs/create/pubsub b/gcloud/alpha/scheduler/jobs/create/pubsub index 20e624440..589f433c1 100644 --- a/gcloud/alpha/scheduler/jobs/create/pubsub +++ b/gcloud/alpha/scheduler/jobs/create/pubsub @@ -22,8 +22,8 @@ EXAMPLES 'Hello' to the Pub/Sub topic 'cron-topic' every 3 hours: $ gcloud alpha scheduler jobs create pubsub my-job \ - --schedule="0 */3 * * *" - --topic=cron-topic --message-body="Hello" + --schedule="0 */3 * * *" --topic=cron-topic \ + --message-body="Hello" POSITIONAL ARGUMENTS Job resource - Job to create. The arguments in this group can be used to diff --git a/gcloud/alpha/services/api-keys/describe b/gcloud/alpha/services/api-keys/describe index ffff2384c..e8b89e62b 100644 --- a/gcloud/alpha/services/api-keys/describe +++ b/gcloud/alpha/services/api-keys/describe @@ -12,12 +12,9 @@ EXAMPLES To describe an API key: $ gcloud alpha services api-keys describe \ - projects/myproject/locations/global/keys/1234 - OR - $ gcloud alpha services api-keys describe 1234 - OR - $ gcloud alpha services api-keys describe 1234 --project=myproject - OR + projects/myproject/locations/global/keys/1234 OR + $ gcloud alpha services api-keys describe 1234 OR + $ gcloud alpha services api-keys describe 1234 --project=myproject OR $ gcloud alpha services api-keys describe 1234 --project=myproject \ --location=global diff --git a/gcloud/alpha/services/api-keys/update b/gcloud/alpha/services/api-keys/update index 56631141f..55671eb63 100644 --- a/gcloud/alpha/services/api-keys/update +++ b/gcloud/alpha/services/api-keys/update @@ -55,7 +55,7 @@ EXAMPLES 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/keys/my-key-id --flags-file=my-flags.yaml The content of 'my-flags.yaml' is as following: diff --git a/gcloud/alpha/services/peered-dns-domains/create b/gcloud/alpha/services/peered-dns-domains/create index a1e24cab3..9fdef397e 100644 --- a/gcloud/alpha/services/peered-dns-domains/create +++ b/gcloud/alpha/services/peered-dns-domains/create @@ -21,15 +21,14 @@ EXAMPLES my-network in the current project, run: $ gcloud alpha services peered-dns-domains create example-com \ - --network=my-network \ - --service=peering-service --dns-suffix=example.com. + --network=my-network --service=peering-service \ + --dns-suffix=example.com. To run the same command asynchronously (non-blocking), run: $ gcloud alpha services peered-dns-domains create example-com \ - --network=my-network \ - --service=peering-service --dns-suffix=example.com. \ - --async + --network=my-network --service=peering-service \ + --dns-suffix=example.com. --async POSITIONAL ARGUMENTS NAME diff --git a/gcloud/alpha/services/peered-dns-domains/delete b/gcloud/alpha/services/peered-dns-domains/delete index f031841a3..0b55a4058 100644 --- a/gcloud/alpha/services/peered-dns-domains/delete +++ b/gcloud/alpha/services/peered-dns-domains/delete @@ -18,14 +18,12 @@ EXAMPLES my-network in the current project, run: $ gcloud alpha services peered-dns-domains delete example-com \ - --network=my-network \ - --service=peering-service + --network=my-network --service=peering-service To run the same command asynchronously (non-blocking), run: $ gcloud alpha services peered-dns-domains delete example-com \ - --network=my-network \ - --service=peering-service --async + --network=my-network --service=peering-service --async POSITIONAL ARGUMENTS NAME diff --git a/gcloud/alpha/services/quota/create b/gcloud/alpha/services/quota/create index 45ed22b6c..f37bfd00c 100644 --- a/gcloud/alpha/services/quota/create +++ b/gcloud/alpha/services/quota/create @@ -14,30 +14,30 @@ EXAMPLES To create a quota override for a project with project number, run: $ gcloud alpha services quota create \ - --service=example.googleapis.com --consumer=projects/12321 - --metric=example.googleapis.com/default_requests + --service=example.googleapis.com --consumer=projects/12321 \ + --metric=example.googleapis.com/default_requests \ --unit=1/min/{project} --value=360 To create a quota override for a project with project ID, run: $ gcloud alpha services quota create \ - --service=example.googleapis.com --consumer=projects/hello - --metric=example.googleapis.com/default_requests + --service=example.googleapis.com --consumer=projects/hello \ + --metric=example.googleapis.com/default_requests \ --unit=1/min/{project} --value=360 To create a quota override for an organization, run: $ gcloud alpha services quota create \ - --service=example.googleapis.com --consumer=organizations/555 - --metric=example.googleapis.com/default_requests + --service=example.googleapis.com --consumer=organizations/555 \ + --metric=example.googleapis.com/default_requests \ --unit=1/min/{project} --value=360 To force the creation of a quota override with dimensions, run: $ gcloud alpha services quota create \ - --service=example.googleapis.com --consumer=projects/12321 - --metric=example.googleapis.com/default_requests - --unit=1/min/{project} --dimensions=regions=us-central1 + --service=example.googleapis.com --consumer=projects/12321 \ + --metric=example.googleapis.com/default_requests \ + --unit=1/min/{project} --dimensions=regions=us-central1 \ --dimensions=zones=us-central1-c --value=360 --force REQUIRED FLAGS diff --git a/gcloud/alpha/services/quota/delete b/gcloud/alpha/services/quota/delete index ca47ecbee..ad7c1ae1a 100644 --- a/gcloud/alpha/services/quota/delete +++ b/gcloud/alpha/services/quota/delete @@ -15,29 +15,29 @@ EXAMPLES To delete a quota override for a project with project number, run: $ gcloud alpha services quota delete \ - --service=example.googleapis.com --consumer=projects/12321 - --metric=example.googleapis.com/default_requests + --service=example.googleapis.com --consumer=projects/12321 \ + --metric=example.googleapis.com/default_requests \ --unit=1/min/{project} To delete a quota override for a project with project ID, run: $ gcloud alpha services quota delete \ - --service=example.googleapis.com --consumer=projects/hello - --metric=example.googleapis.com/default_requests + --service=example.googleapis.com --consumer=projects/hello \ + --metric=example.googleapis.com/default_requests \ --unit=1/min/{project} To delete a quota override for an organization, run: $ gcloud alpha services quota delete \ - --service=example.googleapis.com --consumer=organizations/555 - --metric=example.googleapis.com/default_requests + --service=example.googleapis.com --consumer=organizations/555 \ + --metric=example.googleapis.com/default_requests \ --unit=1/min/{project} To force the deletion of a quota override, run: $ gcloud alpha services quota delete \ - --service=example.googleapis.com --consumer=projects/12321 - --metric=example.googleapis.com/default_requests + --service=example.googleapis.com --consumer=projects/12321 \ + --metric=example.googleapis.com/default_requests \ --unit=1/min/{project} --force REQUIRED FLAGS diff --git a/gcloud/alpha/services/quota/update b/gcloud/alpha/services/quota/update index 688197576..5d800b501 100644 --- a/gcloud/alpha/services/quota/update +++ b/gcloud/alpha/services/quota/update @@ -15,31 +15,30 @@ EXAMPLES To update a quota override for project with project number, run: $ gcloud alpha services quota update \ - --service=example.googleapis.com --consumer=projects/12321 - --metric=example.googleapis.com/default_requests + --service=example.googleapis.com --consumer=projects/12321 \ + --metric=example.googleapis.com/default_requests \ --unit=1/min/{project} --value=360 To update a quota override for project with project ID, run: $ gcloud alpha services quota update \ - --service=example.googleapis.com --consumer=projects/hello - --metric=example.googleapis.com/default_requests + --service=example.googleapis.com --consumer=projects/hello \ + --metric=example.googleapis.com/default_requests \ --unit=1/min/{project} --value=360 To update a quota override for an organization, run: $ gcloud alpha services quota update \ - --service=example.googleapis.com --consumer=organizations/555 - --metric=example.googleapis.com/default_requests + --service=example.googleapis.com --consumer=organizations/555 \ + --metric=example.googleapis.com/default_requests \ --unit=1/min/{project} --value=360 To force the update of a quota override, run: $ gcloud alpha services quota update \ - --service=example.googleapis.com --consumer=projects/12321 - --metric=example.googleapis.com/default_requests - --unit=1/min/{project} - --dimensions=regions=us-central1 + --service=example.googleapis.com --consumer=projects/12321 \ + --metric=example.googleapis.com/default_requests \ + --unit=1/min/{project} --dimensions=regions=us-central1 \ --dimensions=zones=us-central1-c --value=360 --force REQUIRED FLAGS diff --git a/gcloud/alpha/services/vpc-peerings/connect b/gcloud/alpha/services/vpc-peerings/connect index 8e504fcd7..6d2641e0e 100644 --- a/gcloud/alpha/services/vpc-peerings/connect +++ b/gcloud/alpha/services/vpc-peerings/connect @@ -18,14 +18,13 @@ EXAMPLES the service to use, run: $ gcloud alpha services vpc-peerings connect --network=my-network \ - --service=your-service \ - --ranges=google-range-1,google-range-2 + --service=your-service --ranges=google-range-1,google-range-2 To run the same command asynchronously (non-blocking), run: $ gcloud alpha services vpc-peerings connect --network=my-network \ - --service=your-service \ - --ranges=google-range-1,google-range-2 --async + --service=your-service --ranges=google-range-1,google-range-2 \ + --async REQUIRED FLAGS --network=NETWORK diff --git a/gcloud/alpha/services/vpc-peerings/update b/gcloud/alpha/services/vpc-peerings/update index 1f2bb1e17..6f4155b06 100644 --- a/gcloud/alpha/services/vpc-peerings/update +++ b/gcloud/alpha/services/vpc-peerings/update @@ -18,14 +18,13 @@ EXAMPLES google-range-1,google-range-2 for the service to use, run: $ gcloud alpha services vpc-peerings update --network=my-network \ - --service=your-service \ - --ranges=google-range-1,google-range-2 + --service=your-service --ranges=google-range-1,google-range-2 To run the same command asynchronously (non-blocking), run: $ gcloud alpha services vpc-peerings update --network=my-network \ - --service=your-service \ - --ranges=google-range-1,google-range-2 --async + --service=your-service --ranges=google-range-1,google-range-2 \ + --async REQUIRED FLAGS --network=NETWORK diff --git a/gcloud/alpha/source/repos/clone b/gcloud/alpha/source/repos/clone index e55fbe0b0..8aa9bbe4b 100644 --- a/gcloud/alpha/source/repos/clone +++ b/gcloud/alpha/source/repos/clone @@ -26,8 +26,8 @@ EXAMPLES $ gcloud alpha source repos clone REPOSITORY_NAME DIRECTORY_NAME - $ cd DIRECTORY_NAME - ... create/edit files and create one or more commits ... + $ cd DIRECTORY_NAME ... create/edit files and create one or more \ + commits ... $ git push origin master diff --git a/gcloud/alpha/source/repos/update b/gcloud/alpha/source/repos/update index 6d03c56ec..f4ac4cd03 100644 --- a/gcloud/alpha/source/repos/update +++ b/gcloud/alpha/source/repos/update @@ -14,8 +14,7 @@ EXAMPLES notifications, run: $ gcloud alpha source repos update --add-topic=TOPIC_NAME \ - --service-account=SERVICE_ACCOUNT_EMAIL \ - --message-format=json + --service-account=SERVICE_ACCOUNT_EMAIL --message-format=json POSITIONAL ARGUMENTS Repo resource - Name of the Cloud Source repository to update. This diff --git a/gcloud/alpha/spanner/backups/add-iam-policy-binding b/gcloud/alpha/spanner/backups/add-iam-policy-binding index 3adc1971c..f47c4f589 100644 --- a/gcloud/alpha/spanner/backups/add-iam-policy-binding +++ b/gcloud/alpha/spanner/backups/add-iam-policy-binding @@ -19,8 +19,7 @@ EXAMPLES instance 'example-instance', run: $ gcloud alpha spanner backups add-iam-policy-binding \ - example-backup \ - --instance='example-instance' \ + example-backup --instance='example-instance' \ --member='user:test-user@gmail.com' \ --role='roles/spanner.backupAdmin' @@ -29,11 +28,12 @@ EXAMPLES with backup 'example-backup' and instance 'example-instance', run: $ gcloud alpha spanner backups add-iam-policy-binding \ - example-backup \ - --instance='example-instance' \ + example-backup --instance='example-instance' \ --member='user:test-user@gmail.com' \ --role='roles/spanner.backupAdmin' \ - --condition='expression=request.time < timestamp("2019-01-01T00:00:00Z"),title=expires_end_of_2018,description=Expires at midnight on 2018-12-31' + --condition='expression=request.time < + timestamp("2019-01-01T00:00:00Z"),title=expires_end_of_2018,descrip\ + tion=Expires at midnight on 2018-12-31' See https://cloud.google.com/iam/docs/managing-policies for details of policy role and member types. diff --git a/gcloud/alpha/spanner/backups/remove-iam-policy-binding b/gcloud/alpha/spanner/backups/remove-iam-policy-binding index 106d24e46..b33960055 100644 --- a/gcloud/alpha/spanner/backups/remove-iam-policy-binding +++ b/gcloud/alpha/spanner/backups/remove-iam-policy-binding @@ -19,8 +19,7 @@ EXAMPLES instance 'example-instance', run: $ gcloud alpha spanner backups remove-iam-policy-binding \ - example-backup \ - --instance='example-instance' \ + example-backup --instance='example-instance' \ --member='user:test-user@gmail.com' \ --role='roles/spanner.backupAdmin' @@ -29,11 +28,12 @@ EXAMPLES with backup 'example-backup' and instance 'example-instance', run: $ gcloud alpha spanner backups remove-iam-policy-binding \ - example-backup \ - --instance='example-instance' \ + example-backup --instance='example-instance' \ --member='user:test-user@gmail.com' \ --role='roles/spanner.backupAdmin' \ - --condition='expression=request.time < timestamp("2019-01-01T00:00:00Z"),title=expires_end_of_2018,description=Expires at midnight on 2018-12-31' + --condition='expression=request.time < + timestamp("2019-01-01T00:00:00Z"),title=expires_end_of_2018,descrip\ + tion=Expires at midnight on 2018-12-31' See https://cloud.google.com/iam/docs/managing-policies for details of policy role and member types. diff --git a/gcloud/alpha/spanner/databases/create b/gcloud/alpha/spanner/databases/create index 38b5257d5..ad6b7bd2c 100644 --- a/gcloud/alpha/spanner/databases/create +++ b/gcloud/alpha/spanner/databases/create @@ -21,14 +21,13 @@ EXAMPLES To create a Cloud Spanner database with populated schema, run: $ gcloud alpha spanner databases create testdb \ - --instance=my-instance-id + --instance=my-instance-id \ --ddl='CREATE TABLE mytable (a INT64, b INT64) PRIMARY KEY(a)' To create a Cloud Spanner database with the PostgreSQL dialect, run: $ gcloud alpha spanner databases create testdb \ - --instance=my-instance-id - --database-dialect=POSTGRESQL + --instance=my-instance-id --database-dialect=POSTGRESQL POSITIONAL ARGUMENTS Database resource - The Cloud Spanner database to create. The arguments in diff --git a/gcloud/alpha/spanner/databases/ddl/update b/gcloud/alpha/spanner/databases/ddl/update index 1470e7902..6cb3f258d 100644 --- a/gcloud/alpha/spanner/databases/ddl/update +++ b/gcloud/alpha/spanner/databases/ddl/update @@ -13,7 +13,7 @@ EXAMPLES To add a column to a table in the given Cloud Spanner database, run: $ gcloud alpha spanner databases ddl update my-database-id \ - --instance=my-instance-id + --instance=my-instance-id \ --ddl='ALTER TABLE test_table ADD COLUMN a INT64' POSITIONAL ARGUMENTS diff --git a/gcloud/alpha/spanner/databases/sessions/delete b/gcloud/alpha/spanner/databases/sessions/delete index c09c055f5..ccb5c8bcb 100644 --- a/gcloud/alpha/spanner/databases/sessions/delete +++ b/gcloud/alpha/spanner/databases/sessions/delete @@ -14,8 +14,7 @@ EXAMPLES To delete a Cloud Spanner session, run: $ gcloud alpha spanner databases sessions delete my-session-id \ - --instance=my-instance-id - --database=my-database-id + --instance=my-instance-id --database=my-database-id POSITIONAL ARGUMENTS Session resource - The Cloud Spanner session to delete. The arguments in diff --git a/gcloud/alpha/spanner/operations/cancel b/gcloud/alpha/spanner/operations/cancel index ddab60bea..76fc0f7f1 100644 --- a/gcloud/alpha/spanner/operations/cancel +++ b/gcloud/alpha/spanner/operations/cancel @@ -17,15 +17,13 @@ EXAMPLES To cancel a database operation with ID auto_12345, run: - $ gcloud alpha spanner operations cancel _auto_12345 \ - --instance=my-instance-id - --database=my-database-id + $ gcloud alpha spanner operations cancel _auto_12345 \ + --instance=my-instance-id --database=my-database-id To cancel a backup operation with ID auto_12345, run: - $ gcloud alpha spanner operations cancel _auto_12345 \ - --instance=my-instance-id - --backup=my-backup-id + $ gcloud alpha spanner operations cancel _auto_12345 \ + --instance=my-instance-id --backup=my-backup-id POSITIONAL ARGUMENTS OPERATION-ID diff --git a/gcloud/alpha/spanner/operations/describe b/gcloud/alpha/spanner/operations/describe index 44e6751c6..49639784d 100644 --- a/gcloud/alpha/spanner/operations/describe +++ b/gcloud/alpha/spanner/operations/describe @@ -18,15 +18,13 @@ EXAMPLES To describe a Cloud Spanner database operation, run: - $ gcloud alpha spanner operations describe _auto_12345 \ - --instance=my-instance-id - --database=my-database-id + $ gcloud alpha spanner operations describe _auto_12345 \ + --instance=my-instance-id --database=my-database-id To describe a Cloud Spanner backup operation, run: - $ gcloud alpha spanner operations describe _auto_12345 \ - --instance=my-instance-id - --backup=my-backup-id + $ gcloud alpha spanner operations describe _auto_12345 \ + --instance=my-instance-id --backup=my-backup-id POSITIONAL ARGUMENTS OPERATION-ID diff --git a/gcloud/alpha/sql/import/sql b/gcloud/alpha/sql/import/sql index 0836c9fbf..90e56e42f 100644 --- a/gcloud/alpha/sql/import/sql +++ b/gcloud/alpha/sql/import/sql @@ -17,7 +17,7 @@ EXAMPLES To import data from a SQL dump file into a database, testdb, on the specified Cloud SQL instance test-instance-1, run: - $ gcloud sql import sql test-instance-1 \ + $ gcloud sql import sql test-instance-1 \ gs://test-bucket/test-file.sql.gz --database=testdb POSITIONAL ARGUMENTS diff --git a/gcloud/alpha/tasks/create-http-task b/gcloud/alpha/tasks/create-http-task index 78bcfdc17..4dafa46b3 100644 --- a/gcloud/alpha/tasks/create-http-task +++ b/gcloud/alpha/tasks/create-http-task @@ -18,7 +18,7 @@ DESCRIPTION EXAMPLES To create a task: - $ gcloud alpha tasks create-http-task --queue=my-queue + $ gcloud alpha tasks create-http-task --queue=my-queue \ --url=http://example.com/handler-path my-task POSITIONAL ARGUMENTS diff --git a/gcloud/alpha/tasks/queues/create b/gcloud/alpha/tasks/queues/create index 8e507c327..abea032c6 100644 --- a/gcloud/alpha/tasks/queues/create +++ b/gcloud/alpha/tasks/queues/create @@ -18,13 +18,10 @@ DESCRIPTION EXAMPLES To create a Cloud Tasks queue: - $ gcloud alpha tasks queues create my-queue - --max-attempts=10 --max-retry-duration=5s - --max-doublings=4 --min-backoff=1s - --max-backoff=10s - --max-tasks-dispatched-per-second=100 - --max-concurrent-tasks=10 - --routing-override=service:abc + $ gcloud alpha tasks queues create my-queue --max-attempts=10 \ + --max-retry-duration=5s --max-doublings=4 --min-backoff=1s \ + --max-backoff=10s --max-tasks-dispatched-per-second=100 \ + --max-concurrent-tasks=10 --routing-override=service:abc POSITIONAL ARGUMENTS QUEUE diff --git a/gcloud/alpha/tasks/queues/create-app-engine-queue b/gcloud/alpha/tasks/queues/create-app-engine-queue index aaa7ba25e..4e6ffe047 100644 --- a/gcloud/alpha/tasks/queues/create-app-engine-queue +++ b/gcloud/alpha/tasks/queues/create-app-engine-queue @@ -28,13 +28,11 @@ DESCRIPTION EXAMPLES To create a Cloud Tasks queue: - $ gcloud alpha tasks queues create-app-engine-queue my-queue - --max-attempts=10 --max-retry-duration=5s - --max-doublings=4 --min-backoff=1s - --max-backoff=10s - --max-tasks-dispatched-per-second=100 - --max-concurrent-tasks=10 - --routing-override=service:abc + $ gcloud alpha tasks queues create-app-engine-queue my-queue \ + --max-attempts=10 --max-retry-duration=5s --max-doublings=4 \ + --min-backoff=1s --max-backoff=10s \ + --max-tasks-dispatched-per-second=100 \ + --max-concurrent-tasks=10 --routing-override=service:abc POSITIONAL ARGUMENTS QUEUE diff --git a/gcloud/alpha/tasks/queues/create-pull-queue b/gcloud/alpha/tasks/queues/create-pull-queue index e4348e825..a912cfe04 100644 --- a/gcloud/alpha/tasks/queues/create-pull-queue +++ b/gcloud/alpha/tasks/queues/create-pull-queue @@ -18,8 +18,8 @@ DESCRIPTION EXAMPLES To create a Cloud Tasks pull queue: - $ gcloud alpha tasks queues create-pull-queue my-queue - --max-attempts=10 --max-retry-duration=10s + $ gcloud alpha tasks queues create-pull-queue my-queue \ + --max-attempts=10 --max-retry-duration=10s POSITIONAL ARGUMENTS QUEUE diff --git a/gcloud/alpha/tasks/queues/update b/gcloud/alpha/tasks/queues/update index e1ed0b1dd..4f42adfcb 100644 --- a/gcloud/alpha/tasks/queues/update +++ b/gcloud/alpha/tasks/queues/update @@ -23,13 +23,11 @@ DESCRIPTION EXAMPLES To update a Cloud Tasks queue: - $ gcloud alpha tasks queues update my-queue - --clear-max-attempts --clear-max-retry-duration - --clear-max-doublings --clear-min-backoff - --clear-max-backoff - --clear-max-tasks-dispatched-per-second - --clear-max-concurrent-tasks - --clear-routing-override + $ gcloud alpha tasks queues update my-queue --clear-max-attempts \ + --clear-max-retry-duration --clear-max-doublings \ + --clear-min-backoff --clear-max-backoff \ + --clear-max-tasks-dispatched-per-second \ + --clear-max-concurrent-tasks --clear-routing-override POSITIONAL ARGUMENTS QUEUE diff --git a/gcloud/alpha/tasks/queues/update-app-engine-queue b/gcloud/alpha/tasks/queues/update-app-engine-queue index b3bee9062..686a40d48 100644 --- a/gcloud/alpha/tasks/queues/update-app-engine-queue +++ b/gcloud/alpha/tasks/queues/update-app-engine-queue @@ -32,13 +32,11 @@ DESCRIPTION EXAMPLES To update a Cloud Tasks queue: - $ gcloud alpha tasks queues update-app-engine-queue my-queue - --clear-max-attempts --clear-max-retry-duration - --clear-max-doublings --clear-min-backoff - --clear-max-backoff - --clear-max-tasks-dispatched-per-second - --clear-max-concurrent-tasks - --clear-routing-override + $ gcloud alpha tasks queues update-app-engine-queue my-queue \ + --clear-max-attempts --clear-max-retry-duration \ + --clear-max-doublings --clear-min-backoff --clear-max-backoff \ + --clear-max-tasks-dispatched-per-second \ + --clear-max-concurrent-tasks --clear-routing-override POSITIONAL ARGUMENTS QUEUE diff --git a/gcloud/alpha/trace/sinks/create b/gcloud/alpha/trace/sinks/create index d6f1db1af..6586a9fab 100644 --- a/gcloud/alpha/trace/sinks/create +++ b/gcloud/alpha/trace/sinks/create @@ -24,8 +24,8 @@ DESCRIPTION is created. EXAMPLES - $ gcloud alpha trace sinks create my-sink - bigquery.googleapis.com/projects/my-project/datasets/my_dataset + $ gcloud alpha trace sinks create my-sink \ + bigquery.googleapis.com/projects/my-project/datasets/my_dataset POSITIONAL ARGUMENTS SINK_NAME diff --git a/gcloud/anthos/auth/login b/gcloud/anthos/auth/login index d9fa52269..e57feb9de 100644 --- a/gcloud/anthos/auth/login +++ b/gcloud/anthos/auth/login @@ -18,7 +18,7 @@ EXAMPLES To add credentials to custom kubeconfig file: - $ gcloud anthos auth login --cluster=testcluster \ + $ gcloud anthos auth login --cluster=testcluster \ --login-config=kubectl-anthos-config.yaml \ --kubeconfig=my.kubeconfig diff --git a/gcloud/api-gateway/apis/remove-iam-policy-binding b/gcloud/api-gateway/apis/remove-iam-policy-binding index b445f5204..bdbc5a1fe 100644 --- a/gcloud/api-gateway/apis/remove-iam-policy-binding +++ b/gcloud/api-gateway/apis/remove-iam-policy-binding @@ -14,8 +14,7 @@ EXAMPLES 'test-user@gmail.com' on API 'my-api', run: $ gcloud api-gateway apis remove-iam-policy-binding my-api \ - --member='user:test-user@gmail.com' - --role='roles/editor' + --member='user:test-user@gmail.com' --role='roles/editor' POSITIONAL ARGUMENTS Api resource - Name for API which IAM policy binding will be added to. diff --git a/gcloud/api-gateway/gateways/remove-iam-policy-binding b/gcloud/api-gateway/gateways/remove-iam-policy-binding index 0f3994190..c855a3ab8 100644 --- a/gcloud/api-gateway/gateways/remove-iam-policy-binding +++ b/gcloud/api-gateway/gateways/remove-iam-policy-binding @@ -15,8 +15,7 @@ EXAMPLES 'test-user@gmail.com' on Gateway 'my-gateway' in us-central1, run: $ gcloud api-gateway gateways remove-iam-policy-binding my-gateway \ - --location='us-central1' - --member='user:test-user@gmail.com' + --location='us-central1' --member='user:test-user@gmail.com' \ --role='roles/editor' POSITIONAL ARGUMENTS diff --git a/gcloud/apigee/products/update b/gcloud/apigee/products/update index e0e858ed2..31109e3c0 100644 --- a/gcloud/apigee/products/update +++ b/gcloud/apigee/products/update @@ -69,7 +69,7 @@ EXAMPLES that attribute if it exists and creating it if it doesn't, and remove the attribute baz if it exists, run: - $ gcloud apigee products update my-prod --add-attribute="foo=bar" \ + $ gcloud apigee products update my-prod --add-attribute="foo=bar" \ --remove-attribute=baz To update the list of API proxies included in the API product, run: diff --git a/gcloud/app/firewall-rules/create b/gcloud/app/firewall-rules/create index 144ba9c27..1376b5e4d 100644 --- a/gcloud/app/firewall-rules/create +++ b/gcloud/app/firewall-rules/create @@ -12,9 +12,8 @@ DESCRIPTION EXAMPLES To create a new App Engine firewall rule, run: - $ gcloud app firewall-rules create 1234 - --source-range='2001:db8::/32' - --action=deny + $ gcloud app firewall-rules create 1234 \ + --source-range='2001:db8::/32' --action=deny \ --description='block traffic from the example range.' POSITIONAL ARGUMENTS diff --git a/gcloud/app/firewall-rules/update b/gcloud/app/firewall-rules/update index 905b2b1c9..d25f6d2a4 100644 --- a/gcloud/app/firewall-rules/update +++ b/gcloud/app/firewall-rules/update @@ -12,10 +12,9 @@ DESCRIPTION EXAMPLES To update an App Engine firewall rule, run: - $ gcloud app firewall-rules update 1234 - --source-range='2001:db8::/32' - --action=allow - --description='This is an example rule.' + $ gcloud app firewall-rules update 1234 \ + --source-range='2001:db8::/32' --action=allow \ + --description='This is an example rule.' POSITIONAL ARGUMENTS PRIORITY diff --git a/gcloud/app/ssl-certificates/create b/gcloud/app/ssl-certificates/create index 8acdc95dc..c429633c6 100644 --- a/gcloud/app/ssl-certificates/create +++ b/gcloud/app/ssl-certificates/create @@ -14,8 +14,8 @@ EXAMPLES To add a new SSL certificate to App Engine, run: $ gcloud app ssl-certificates create --display-name='example cert' \ - --certificate='/home/user/me/my_cert.cer' \ - --private-key='/home/user/me/my_key.pfx' + --certificate='/home/user/me/my_cert.cer' \ + --private-key='/home/user/me/my_key.pfx' REQUIRED FLAGS --certificate=LOCAL_FILE_PATH diff --git a/gcloud/app/ssl-certificates/update b/gcloud/app/ssl-certificates/update index 0d5537361..e4a921745 100644 --- a/gcloud/app/ssl-certificates/update +++ b/gcloud/app/ssl-certificates/update @@ -13,8 +13,8 @@ EXAMPLES To update an App Engine SSL certificate, run: $ gcloud app ssl-certificates update 1234 \ - --display-name='updated name' \ - --certificate='/home/user/me/new_cert.cer' \ + --display-name='updated name' \ + --certificate='/home/user/me/new_cert.cer' \ --private-key='/home/user/me/new_key.pfx' POSITIONAL ARGUMENTS diff --git a/gcloud/artifacts/repositories/help b/gcloud/artifacts/repositories/help index f7860feb0..810151566 100644 --- a/gcloud/artifacts/repositories/help +++ b/gcloud/artifacts/repositories/help @@ -32,14 +32,14 @@ EXAMPLES To add an IAM policy binding for the role of 'roles/editor' for the user 'test-user@gmail.com' on repository my-repo, run: - $ gcloud artifacts repositories add-iam-policy-binding my-repo - --member='user:test-user@gmail.com' --role='roles/editor' + $ gcloud artifacts repositories add-iam-policy-binding my-repo \ + --member='user:test-user@gmail.com' --role='roles/editor' To remove an IAM policy binding for the role of 'roles/editor' for the user 'test-user@gmail.com' on repository my-repo, run: - $ gcloud artifacts repositories remove-iam-policy-binding my-repo - --member='user:test-user@gmail.com' --role='roles/editor' + $ gcloud artifacts repositories remove-iam-policy-binding my-repo \ + --member='user:test-user@gmail.com' --role='roles/editor' GCLOUD WIDE FLAGS These flags are available to all commands: --help. diff --git a/gcloud/asset/feeds/create b/gcloud/asset/feeds/create index 11b656959..d24062f57 100644 --- a/gcloud/asset/feeds/create +++ b/gcloud/asset/feeds/create @@ -19,9 +19,10 @@ EXAMPLES To create a new feed 'feed1' in project 'p1' which alerts on compute disks and network resources types, run: - $ gcloud asset feeds create feed1 --project=p1 - --asset-types=compute.googleapis.com/Network,compute.googleapis.com/Disk - --content-type=resource --pubsub-topic=projects/project1/topics/feed-topic + $ gcloud asset feeds create feed1 --project=p1 \ + --asset-types=compute.googleapis.com/Network,\ + compute.googleapis.com/Disk --content-type=resource \ + --pubsub-topic=projects/project1/topics/feed-topic POSITIONAL ARGUMENTS FEED_ID diff --git a/gcloud/asset/feeds/update b/gcloud/asset/feeds/update index ab3f60336..5ac02b8fc 100644 --- a/gcloud/asset/feeds/update +++ b/gcloud/asset/feeds/update @@ -26,8 +26,8 @@ DESCRIPTION EXAMPLES To add an asset-type to an existing feed, run: - $ gcloud asset feeds update feed1 --project=p1 - --add-asset-types=pubsub.googleapis.com/Topic + $ gcloud asset feeds update feed1 --project=p1 \ + --add-asset-types=pubsub.googleapis.com/Topic POSITIONAL ARGUMENTS FEED_ID diff --git a/gcloud/auth/activate-service-account b/gcloud/auth/activate-service-account index 4aa705fd5..892af7103 100644 --- a/gcloud/auth/activate-service-account +++ b/gcloud/auth/activate-service-account @@ -46,7 +46,7 @@ EXAMPLES account while also specifying a project, run: $ gcloud auth activate-service-account SERVICE_ACCOUNT@DOMAIN.COM \ - --key-file=/path/key.json --project=PROJECT_ID + --key-file=/path/key.json --project=PROJECT_ID POSITIONAL ARGUMENTS [ACCOUNT] diff --git a/gcloud/auth/application-default/help b/gcloud/auth/application-default/help index d3ab3f3da..899a0dfaa 100644 --- a/gcloud/auth/application-default/help +++ b/gcloud/auth/application-default/help @@ -29,8 +29,8 @@ EXAMPLES access, run: $ gcloud iam service-accounts create my-account - $ gcloud iam service-accounts keys create key.json - --iam-account=my-account@my-project.iam.gserviceaccount.com + $ gcloud iam service-accounts keys create key.json \ + --iam-account=my-account@my-project.iam.gserviceaccount.com $ export GOOGLE_APPLICATION_CREDENTIALS=key.json $ ./my_application.sh diff --git a/gcloud/auth/configure-docker b/gcloud/auth/configure-docker index 0a0693b78..2d7b4e026 100644 --- a/gcloud/auth/configure-docker +++ b/gcloud/auth/configure-docker @@ -22,16 +22,32 @@ DESCRIPTION For more details on Docker registries, see https://docs.docker.com/registry/. + For more details on how to authenticate to Google Container Registry using + this command, see + https://cloud.google.com/container-registry/docs/advanced-authentication#gcloud-helper. + + For more details on Google Container Registry's standalone credential + helpers, see https://github.com/GoogleCloudPlatform/docker-credential-gcr. + For more details on Docker credential helpers, see https://docs.docker.com/engine/reference/commandline/login/#credential-helpers. - For more details on the Google Container Registry's Docker credential - helper, see https://github.com/GoogleCloudPlatform/docker-credential-gcr. +EXAMPLES + To configure docker authentication after logging into gcloud, run: + + $ gcloud auth configure-docker + + To configure docker authentication with Container Registry, e.g., gcr.io, + run: + + $ gcloud auth configure-docker gcr.io POSITIONAL ARGUMENTS [REGISTRIES] The comma-separated list of registries to configure the credential - helper for. + helper for. Container Registry is a service for storing private + container images. For available registries, see + https://cloud.google.com/container-registry/docs/pushing-and-pulling#add-registry. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/beta/access-context-manager/policies/create b/gcloud/beta/access-context-manager/policies/create index e721f0176..ae17d1553 100644 --- a/gcloud/beta/access-context-manager/policies/create +++ b/gcloud/beta/access-context-manager/policies/create @@ -34,7 +34,7 @@ EXAMPLES $ gcloud beta access-context-manager policies create \ --organization=organizations/123 --scopes=folders/345 \ - --title="My Folder Policy" + --title="My Folder Policy" Only projects within this folder can be added to service perimeters within this policy. @@ -44,7 +44,7 @@ EXAMPLES $ gcloud beta access-context-manager policies create \ --organization=organizations/123 --scopes=projects/567 \ - --title="My Project Policy" + --title="My Project Policy" REQUIRED FLAGS --organization=ORGANIZATION diff --git a/gcloud/beta/active-directory/domains/backups/delete b/gcloud/beta/active-directory/domains/backups/delete index 093807bb2..9e3034113 100644 --- a/gcloud/beta/active-directory/domains/backups/delete +++ b/gcloud/beta/active-directory/domains/backups/delete @@ -22,8 +22,7 @@ EXAMPLES $ gcloud beta active-directory domains backups delete \ projects/my-proj/locations/global/domains/my-domain.com/\ - backups/my-backup \ - --async + backups/my-backup --async POSITIONAL ARGUMENTS Backup resource - Name of the Managed Microsoft AD domain backup you want diff --git a/gcloud/beta/active-directory/domains/backups/update b/gcloud/beta/active-directory/domains/backups/update index fe50bb9e0..37fc9eb70 100644 --- a/gcloud/beta/active-directory/domains/backups/update +++ b/gcloud/beta/active-directory/domains/backups/update @@ -20,8 +20,7 @@ EXAMPLES $ gcloud beta active-directory domains backups update \ projects/my-proj/locations/global/domains/my-domain.com/\ - backups/my-backup \ - --update-labels=l1=1,l2=2 + backups/my-backup --update-labels=l1=1,l2=2 POSITIONAL ARGUMENTS Backup resource - Name of the Managed Microsoft AD domain backup you want diff --git a/gcloud/beta/active-directory/domains/create b/gcloud/beta/active-directory/domains/create index de16aa9de..67711e097 100644 --- a/gcloud/beta/active-directory/domains/create +++ b/gcloud/beta/active-directory/domains/create @@ -25,8 +25,9 @@ EXAMPLES address range 10.172.0.0/24. $ gcloud beta active-directory domains create my-domain.com \ - --region=us-central1 --reserved-ip-range="10.172.0.0/24" - --authorized-networks=projects/my-project/global/networks/my-network + --region=us-central1 --reserved-ip-range="10.172.0.0/24" \ + --authorized-networks=projects/my-project/global/networks/\ + my-network POSITIONAL ARGUMENTS Domain resource - Name of the managed Managed Microsoft AD domain you want diff --git a/gcloud/beta/active-directory/domains/trusts/create b/gcloud/beta/active-directory/domains/trusts/create index 1790ae95b..959f013cd 100644 --- a/gcloud/beta/active-directory/domains/trusts/create +++ b/gcloud/beta/active-directory/domains/trusts/create @@ -27,9 +27,10 @@ EXAMPLES my-domain.com and target-domain.com. $ gcloud beta active-directory domains trusts create my-domain.com \ - --target-domain-name=target-domain.com - --target-dns-ip-addresses=10.177.0.2 --type=EXTERNAL --direction=BIDIRECTIONAL - --selective-authentication=false --async + --target-domain-name=target-domain.com \ + --target-dns-ip-addresses=10.177.0.2 --type=EXTERNAL \ + --direction=BIDIRECTIONAL --selective-authentication=false \ + --async POSITIONAL ARGUMENTS Domain resource - Name of the Managed Microsoft AD domain you want to diff --git a/gcloud/beta/active-directory/domains/trusts/update b/gcloud/beta/active-directory/domains/trusts/update index 6a443b9d0..78eefacfd 100644 --- a/gcloud/beta/active-directory/domains/trusts/update +++ b/gcloud/beta/active-directory/domains/trusts/update @@ -24,9 +24,9 @@ EXAMPLES The following command updates the target DNS IP address for the AD trust between my-domain.com and my-target-domain.com to 10.177.0.3. - $ gcloud beta active-directory domains trusts update \ - my-domain.com --target-domain-name=my-target-domain.com - --target-dns-ip-addresses=10.177.0.3 + $ gcloud beta active-directory domains trusts update my-domain.com \ + --target-domain-name=my-target-domain.com \ + --target-dns-ip-addresses=10.177.0.3 POSITIONAL ARGUMENTS Domain resource - Name of the Managed Microsoft AD trust for which you diff --git a/gcloud/beta/active-directory/domains/update b/gcloud/beta/active-directory/domains/update index 7104fc741..fd93e5bc1 100644 --- a/gcloud/beta/active-directory/domains/update +++ b/gcloud/beta/active-directory/domains/update @@ -25,13 +25,13 @@ EXAMPLES us-west1: $ gcloud beta active-directory domains update my-domain.com \ - --update-labels=env=test,service=foo \ - --add-region=us-west1 + --update-labels=env=test,service=foo --add-region=us-west1 This peers the domain my-domain.com to the network my-network. - $ gcloud beta active-directory domains update my-domain.com - --add-authorized-networks=projects/my-project/global/networks/my-network + $ gcloud beta active-directory domains update my-domain.com \ + --add-authorized-networks=projects/my-project/global/networks/\ + my-network POSITIONAL ARGUMENTS Domain resource - Name of the Managed Microsoft AD domain you want to diff --git a/gcloud/beta/ai-platform/explain b/gcloud/beta/ai-platform/explain index b7cf52012..c942aa680 100644 --- a/gcloud/beta/ai-platform/explain +++ b/gcloud/beta/ai-platform/explain @@ -18,7 +18,7 @@ EXAMPLES 'version' and with the name 'model-name', run: $ gcloud beta ai-platform explain explain --model=model-name \ - --version=version --json-instances=instances.json + --version=version --json-instances=instances.json REQUIRED FLAGS --model=MODEL diff --git a/gcloud/beta/ai-platform/models/delete b/gcloud/beta/ai-platform/models/delete index ad95b8520..1447932ad 100644 --- a/gcloud/beta/ai-platform/models/delete +++ b/gcloud/beta/ai-platform/models/delete @@ -10,8 +10,8 @@ EXAMPLES To delete all models matching the regular expression vision[0-9]+, run: $ gcloud beta ai-platform models list --uri \ - --filter 'name ~ vision[0-9]+' | - xargs -n 1 gcloud beta ai-platform models delete + --filter 'name ~ vision[0-9]+' | xargs -n 1 gcloud beta \ + ai-platform models delete POSITIONAL ARGUMENTS MODEL diff --git a/gcloud/beta/ai/custom-jobs/create b/gcloud/beta/ai/custom-jobs/create index 26e2b9b75..7c2d7b989 100644 --- a/gcloud/beta/ai/custom-jobs/create +++ b/gcloud/beta/ai/custom-jobs/create @@ -20,9 +20,10 @@ EXAMPLES To create a job under project example in region us-central1, run: $ gcloud beta ai custom-jobs create --region=us-central1 \ - --project=example - --worker-pool-spec=replica-count=1,machine-type='n1-highmem-2',container-image-uri='gcr.io/ucaip-test/ucaip-training-test' - --display-name=test + --project=example \ + --worker-pool-spec=replica-count=1,machine-type='n1-highmem-2',\ + container-image-uri='gcr.io/ucaip-test/ucaip-training-test' \ + --display-name=test REQUIRED FLAGS --display-name=DISPLAY_NAME diff --git a/gcloud/beta/ai/endpoints/create b/gcloud/beta/ai/endpoints/create index cd94f796a..db1e35bc2 100644 --- a/gcloud/beta/ai/endpoints/create +++ b/gcloud/beta/ai/endpoints/create @@ -11,8 +11,7 @@ EXAMPLES To create an endpoint under project example in region us-central1, run: $ gcloud beta ai endpoints create --project=example \ - --region=us-central1 - --display-name=my_endpoint + --region=us-central1 --display-name=my_endpoint REQUIRED FLAGS --display-name=DISPLAY_NAME diff --git a/gcloud/beta/ai/endpoints/deploy-model b/gcloud/beta/ai/endpoints/deploy-model index 661316340..f896dcac0 100644 --- a/gcloud/beta/ai/endpoints/deploy-model +++ b/gcloud/beta/ai/endpoints/deploy-model @@ -19,8 +19,8 @@ EXAMPLES us-central1, run: $ gcloud beta ai endpoints deploy-model 123 --project=example \ - --region=us-central1 --model=456 - --display-name=my_deployed_model + --region=us-central1 --model=456 \ + --display-name=my_deployed_model POSITIONAL ARGUMENTS Endpoint resource - The endpoint to deploy a model to. The arguments in diff --git a/gcloud/beta/ai/endpoints/predict b/gcloud/beta/ai/endpoints/predict index 64535959f..93fe36e74 100644 --- a/gcloud/beta/ai/endpoints/predict +++ b/gcloud/beta/ai/endpoints/predict @@ -16,8 +16,7 @@ EXAMPLES us-central1, run: $ gcloud beta ai endpoints predict 123 --project=example \ - --region=us-central1 - --json-request=input.json + --region=us-central1 --json-request=input.json POSITIONAL ARGUMENTS Endpoint resource - The endpoint to do online prediction. The arguments in diff --git a/gcloud/beta/ai/endpoints/raw-predict b/gcloud/beta/ai/endpoints/raw-predict index 70c2bad92..526aacd25 100644 --- a/gcloud/beta/ai/endpoints/raw-predict +++ b/gcloud/beta/ai/endpoints/raw-predict @@ -31,8 +31,8 @@ EXAMPLES To send the image file image.jpeg and set the content type, run: $ gcloud beta ai endpoints raw-predict 123 --project=example \ - --region=us-central1 - --http-headers=Content-Type=image/jpeg --request=@image.jpeg + --region=us-central1 --http-headers=Content-Type=image/jpeg \ + --request=@image.jpeg POSITIONAL ARGUMENTS Endpoint resource - The endpoint to do online raw prediction. The diff --git a/gcloud/beta/ai/endpoints/undeploy-model b/gcloud/beta/ai/endpoints/undeploy-model index 5b1228b70..f48148c25 100644 --- a/gcloud/beta/ai/endpoints/undeploy-model +++ b/gcloud/beta/ai/endpoints/undeploy-model @@ -12,8 +12,7 @@ EXAMPLES region us-central1, run: $ gcloud beta ai endpoints undeploy-model 123 --project=example \ - --region=us-central1 - --deployed-model-id=456 + --region=us-central1 --deployed-model-id=456 POSITIONAL ARGUMENTS Endpoint resource - The endpoint to undeploy a model from. The arguments diff --git a/gcloud/beta/ai/endpoints/update b/gcloud/beta/ai/endpoints/update index 00666cb27..3004b9bbc 100644 --- a/gcloud/beta/ai/endpoints/update +++ b/gcloud/beta/ai/endpoints/update @@ -13,8 +13,7 @@ EXAMPLES To update an endpoint 123 under project example in region us-central1, run: $ gcloud beta ai endpoints update 123 --project=example \ - --region=us-central1 - --display-name=new_name + --region=us-central1 --display-name=new_name POSITIONAL ARGUMENTS Endpoint resource - The endpoint to update. The arguments in this group diff --git a/gcloud/beta/ai/index-endpoints/create b/gcloud/beta/ai/index-endpoints/create index 644a037bb..72fe5053a 100644 --- a/gcloud/beta/ai/index-endpoints/create +++ b/gcloud/beta/ai/index-endpoints/create @@ -12,9 +12,9 @@ EXAMPLES projects/123/global/networks/test-network in region us-central1, run: $ gcloud beta ai index-endpoints create \ - --display-name=index-endpoint --description=test - --network=projects/123/global/networks/test-network - --project=example --region=us-central1 + --display-name=index-endpoint --description=test \ + --network=projects/123/global/networks/test-network \ + --project=example --region=us-central1 REQUIRED FLAGS --display-name=DISPLAY_NAME diff --git a/gcloud/beta/ai/index-endpoints/undeploy-index b/gcloud/beta/ai/index-endpoints/undeploy-index index 3e24e1001..59534c640 100644 --- a/gcloud/beta/ai/index-endpoints/undeploy-index +++ b/gcloud/beta/ai/index-endpoints/undeploy-index @@ -12,8 +12,8 @@ EXAMPLES 456 under project example in region us-central1, run: $ gcloud beta ai index-endpoints undeploy-index 456 \ - --project=example --region=us-central1 - --deployed-index-id=deployed-index-345 + --project=example --region=us-central1 \ + --deployed-index-id=deployed-index-345 POSITIONAL ARGUMENTS Index endpoint resource - The index endpoint to undeploy an index. The diff --git a/gcloud/beta/ai/indexes/create b/gcloud/beta/ai/indexes/create index cfb6cad3c..173215395 100644 --- a/gcloud/beta/ai/indexes/create +++ b/gcloud/beta/ai/indexes/create @@ -11,9 +11,8 @@ EXAMPLES To create an index under project example in region us-central1, run: $ gcloud beta ai indexes create --display-name=index \ - --description=test - --metadata-file=path/to/your/metadata.json - --project=example --region=us-central1 + --description=test --metadata-file=path/to/your/metadata.json \ + --project=example --region=us-central1 REQUIRED FLAGS --display-name=DISPLAY_NAME diff --git a/gcloud/beta/ai/indexes/update b/gcloud/beta/ai/indexes/update index 454cf408f..fa255aa4f 100644 --- a/gcloud/beta/ai/indexes/update +++ b/gcloud/beta/ai/indexes/update @@ -10,9 +10,9 @@ SYNOPSIS EXAMPLES To update index 123 under project example in region us-central1, run: - $ gcloud beta ai indexes update --display-name=new-name - --metadata-file=path/to/your/metadata.json --project=example - --region=us-central1 + $ gcloud beta ai indexes update --display-name=new-name \ + --metadata-file=path/to/your/metadata.json --project=example \ + --region=us-central1 POSITIONAL ARGUMENTS Index resource - Index to update. The arguments in this group can be used diff --git a/gcloud/beta/ai/models/upload b/gcloud/beta/ai/models/upload index 2d047574e..e236aa18e 100644 --- a/gcloud/beta/ai/models/upload +++ b/gcloud/beta/ai/models/upload @@ -23,9 +23,10 @@ EXAMPLES To upload a model under project example in region us-central1, run: $ gcloud beta ai models upload \ - --container-image-uri="gcr.io/example/my-image" - --description=example-model --display-name=my-model - --artifact-uri='gs://bucket/path' --project=example --region=us-central1 + --container-image-uri="gcr.io/example/my-image" \ + --description=example-model --display-name=my-model \ + --artifact-uri='gs://bucket/path' --project=example \ + --region=us-central1 REQUIRED FLAGS --container-image-uri=CONTAINER_IMAGE_URI diff --git a/gcloud/beta/anthos/auth/login b/gcloud/beta/anthos/auth/login index 785a2aef8..4770c97c7 100644 --- a/gcloud/beta/anthos/auth/login +++ b/gcloud/beta/anthos/auth/login @@ -19,7 +19,7 @@ EXAMPLES To add credentials to custom kubeconfig file: - $ gcloud beta anthos auth login --cluster=testcluster \ + $ gcloud beta anthos auth login --cluster=testcluster \ --login-config=kubectl-anthos-config.yaml \ --kubeconfig=my.kubeconfig diff --git a/gcloud/beta/api-gateway/apis/remove-iam-policy-binding b/gcloud/beta/api-gateway/apis/remove-iam-policy-binding index 0f8617a5d..3f8aff97d 100644 --- a/gcloud/beta/api-gateway/apis/remove-iam-policy-binding +++ b/gcloud/beta/api-gateway/apis/remove-iam-policy-binding @@ -14,8 +14,7 @@ EXAMPLES 'test-user@gmail.com' on API 'my-api', run: $ gcloud beta api-gateway apis remove-iam-policy-binding my-api \ - --member='user:test-user@gmail.com' - --role='roles/editor' + --member='user:test-user@gmail.com' --role='roles/editor' POSITIONAL ARGUMENTS Api resource - Name for API which IAM policy binding will be added to. diff --git a/gcloud/beta/api-gateway/gateways/remove-iam-policy-binding b/gcloud/beta/api-gateway/gateways/remove-iam-policy-binding index 0407e643c..bf3705967 100644 --- a/gcloud/beta/api-gateway/gateways/remove-iam-policy-binding +++ b/gcloud/beta/api-gateway/gateways/remove-iam-policy-binding @@ -15,9 +15,8 @@ EXAMPLES 'test-user@gmail.com' on Gateway 'my-gateway' in us-central1, run: $ gcloud beta api-gateway gateways remove-iam-policy-binding \ - my-gateway --location='us-central1' - --member='user:test-user@gmail.com' - --role='roles/editor' + my-gateway --location='us-central1' \ + --member='user:test-user@gmail.com' --role='roles/editor' POSITIONAL ARGUMENTS Gateway resource - Name for gateway which will be IAM policy binding will diff --git a/gcloud/beta/apigee/products/update b/gcloud/beta/apigee/products/update index f30f7acb1..3310699fb 100644 --- a/gcloud/beta/apigee/products/update +++ b/gcloud/beta/apigee/products/update @@ -70,7 +70,7 @@ EXAMPLES attribute baz if it exists, run: $ gcloud beta apigee products update my-prod \ - --add-attribute="foo=bar" --remove-attribute=baz + --add-attribute="foo=bar" --remove-attribute=baz To update the list of API proxies included in the API product, run: diff --git a/gcloud/beta/app/firewall-rules/create b/gcloud/beta/app/firewall-rules/create index 73ce12571..6eec0ae61 100644 --- a/gcloud/beta/app/firewall-rules/create +++ b/gcloud/beta/app/firewall-rules/create @@ -12,9 +12,8 @@ DESCRIPTION EXAMPLES To create a new App Engine firewall rule, run: - $ gcloud beta app firewall-rules create 1234 - --source-range='2001:db8::/32' - --action=deny + $ gcloud beta app firewall-rules create 1234 \ + --source-range='2001:db8::/32' --action=deny \ --description='block traffic from the example range.' POSITIONAL ARGUMENTS diff --git a/gcloud/beta/app/firewall-rules/update b/gcloud/beta/app/firewall-rules/update index 9a92f95fc..1d60bd7e4 100644 --- a/gcloud/beta/app/firewall-rules/update +++ b/gcloud/beta/app/firewall-rules/update @@ -12,10 +12,9 @@ DESCRIPTION EXAMPLES To update an App Engine firewall rule, run: - $ gcloud beta app firewall-rules update 1234 - --source-range='2001:db8::/32' - --action=allow - --description='This is an example rule.' + $ gcloud beta app firewall-rules update 1234 \ + --source-range='2001:db8::/32' --action=allow \ + --description='This is an example rule.' POSITIONAL ARGUMENTS PRIORITY diff --git a/gcloud/beta/app/ssl-certificates/create b/gcloud/beta/app/ssl-certificates/create index ec4efa6a3..e1ae38043 100644 --- a/gcloud/beta/app/ssl-certificates/create +++ b/gcloud/beta/app/ssl-certificates/create @@ -15,8 +15,8 @@ EXAMPLES To add a new SSL certificate to App Engine, run: $ gcloud beta app ssl-certificates create \ - --display-name='example cert' \ - --certificate='/home/user/me/my_cert.cer' \ + --display-name='example cert' \ + --certificate='/home/user/me/my_cert.cer' \ --private-key='/home/user/me/my_key.pfx' REQUIRED FLAGS diff --git a/gcloud/beta/app/ssl-certificates/update b/gcloud/beta/app/ssl-certificates/update index e91ca3a64..99cad497a 100644 --- a/gcloud/beta/app/ssl-certificates/update +++ b/gcloud/beta/app/ssl-certificates/update @@ -13,8 +13,8 @@ EXAMPLES To update an App Engine SSL certificate, run: $ gcloud beta app ssl-certificates update 1234 \ - --display-name='updated name' \ - --certificate='/home/user/me/new_cert.cer' \ + --display-name='updated name' \ + --certificate='/home/user/me/new_cert.cer' \ --private-key='/home/user/me/new_key.pfx' POSITIONAL ARGUMENTS diff --git a/gcloud/beta/artifacts/repositories/help b/gcloud/beta/artifacts/repositories/help index fca403ada..7284b4d34 100644 --- a/gcloud/beta/artifacts/repositories/help +++ b/gcloud/beta/artifacts/repositories/help @@ -33,15 +33,16 @@ EXAMPLES To add an IAM policy binding for the role of 'roles/editor' for the user 'test-user@gmail.com' on repository my-repo, run: - $ gcloud beta artifacts repositories add-iam-policy-binding my-repo - --member='user:test-user@gmail.com' --role='roles/editor' + $ gcloud beta artifacts repositories add-iam-policy-binding \ + my-repo --member='user:test-user@gmail.com' \ + --role='roles/editor' To remove an IAM policy binding for the role of 'roles/editor' for the user 'test-user@gmail.com' on repository my-repo, run: $ gcloud beta artifacts repositories remove-iam-policy-binding \ - my-repo - --member='user:test-user@gmail.com' --role='roles/editor' + my-repo --member='user:test-user@gmail.com' \ + --role='roles/editor' GCLOUD WIDE FLAGS These flags are available to all commands: --help. diff --git a/gcloud/beta/asset/feeds/create b/gcloud/beta/asset/feeds/create index 4f80cd4f7..2d5423a3f 100644 --- a/gcloud/beta/asset/feeds/create +++ b/gcloud/beta/asset/feeds/create @@ -19,9 +19,10 @@ EXAMPLES To create a new feed 'feed1' in project 'p1' which alerts on compute disks and network resources types, run: - $ gcloud beta asset feeds create feed1 --project=p1 - --asset-types=compute.googleapis.com/Network,compute.googleapis.com/Disk - --content-type=resource --pubsub-topic=projects/project1/topics/feed-topic + $ gcloud beta asset feeds create feed1 --project=p1 \ + --asset-types=compute.googleapis.com/Network,\ + compute.googleapis.com/Disk --content-type=resource \ + --pubsub-topic=projects/project1/topics/feed-topic POSITIONAL ARGUMENTS FEED_ID diff --git a/gcloud/beta/asset/feeds/update b/gcloud/beta/asset/feeds/update index ed9804893..68dadb207 100644 --- a/gcloud/beta/asset/feeds/update +++ b/gcloud/beta/asset/feeds/update @@ -27,8 +27,8 @@ DESCRIPTION EXAMPLES To add an asset-type to an existing feed, run: - $ gcloud beta asset feeds update feed1 --project=p1 - --add-asset-types=pubsub.googleapis.com/Topic + $ gcloud beta asset feeds update feed1 --project=p1 \ + --add-asset-types=pubsub.googleapis.com/Topic POSITIONAL ARGUMENTS FEED_ID diff --git a/gcloud/beta/auth/activate-service-account b/gcloud/beta/auth/activate-service-account index d69474c50..7133a2f4b 100644 --- a/gcloud/beta/auth/activate-service-account +++ b/gcloud/beta/auth/activate-service-account @@ -46,8 +46,8 @@ EXAMPLES account while also specifying a project, run: $ gcloud beta auth activate-service-account \ - SERVICE_ACCOUNT@DOMAIN.COM \ - --key-file=/path/key.json --project=PROJECT_ID + SERVICE_ACCOUNT@DOMAIN.COM --key-file=/path/key.json \ + --project=PROJECT_ID POSITIONAL ARGUMENTS [ACCOUNT] diff --git a/gcloud/beta/auth/application-default/help b/gcloud/beta/auth/application-default/help index c51fbf619..8d48b4851 100644 --- a/gcloud/beta/auth/application-default/help +++ b/gcloud/beta/auth/application-default/help @@ -29,8 +29,8 @@ EXAMPLES access, run: $ gcloud iam service-accounts create my-account - $ gcloud iam service-accounts keys create key.json - --iam-account=my-account@my-project.iam.gserviceaccount.com + $ gcloud iam service-accounts keys create key.json \ + --iam-account=my-account@my-project.iam.gserviceaccount.com $ export GOOGLE_APPLICATION_CREDENTIALS=key.json $ ./my_application.sh diff --git a/gcloud/beta/auth/configure-docker b/gcloud/beta/auth/configure-docker index 0e3a94584..a26528512 100644 --- a/gcloud/beta/auth/configure-docker +++ b/gcloud/beta/auth/configure-docker @@ -22,16 +22,32 @@ DESCRIPTION For more details on Docker registries, see https://docs.docker.com/registry/. + For more details on how to authenticate to Google Container Registry using + this command, see + https://cloud.google.com/container-registry/docs/advanced-authentication#gcloud-helper. + + For more details on Google Container Registry's standalone credential + helpers, see https://github.com/GoogleCloudPlatform/docker-credential-gcr. + For more details on Docker credential helpers, see https://docs.docker.com/engine/reference/commandline/login/#credential-helpers. - For more details on the Google Container Registry's Docker credential - helper, see https://github.com/GoogleCloudPlatform/docker-credential-gcr. +EXAMPLES + To configure docker authentication after logging into gcloud, run: + + $ gcloud beta auth configure-docker + + To configure docker authentication with Container Registry, e.g., gcr.io, + run: + + $ gcloud beta auth configure-docker gcr.io POSITIONAL ARGUMENTS [REGISTRIES] The comma-separated list of registries to configure the credential - helper for. + helper for. Container Registry is a service for storing private + container images. For available registries, see + https://cloud.google.com/container-registry/docs/pushing-and-pulling#add-registry. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/beta/bigtable/backups/create b/gcloud/beta/bigtable/backups/create index 01e01c7a9..2e59c9646 100644 --- a/gcloud/beta/bigtable/backups/create +++ b/gcloud/beta/bigtable/backups/create @@ -17,15 +17,16 @@ EXAMPLES which expires at '2019-03-30T10:49:41Z', run: $ gcloud beta bigtable backups create BACKUP_NAME \ - --instance=INSTANCE_NAME --cluster=CLUSTER_NAME - --table=TABLE_NAME --expiration-date=2019-03-30T10:49:41Z --async + --instance=INSTANCE_NAME --cluster=CLUSTER_NAME \ + --table=TABLE_NAME --expiration-date=2019-03-30T10:49:41Z \ + --async To create a backup 'BACKUP_NAME' syncronously from table 'TABLE_NAME' which expires in 2 weeks from now, run: $ gcloud beta bigtable backups create BACKUP_NAME \ - --instance=INSTANCE_NAME --cluster=CLUSTER_NAME - --table=TABLE_NAME --retention-period=2w + --instance=INSTANCE_NAME --cluster=CLUSTER_NAME \ + --table=TABLE_NAME --retention-period=2w POSITIONAL ARGUMENTS Backup resource - The Cloud Bigtable backup to create. The arguments in diff --git a/gcloud/beta/bigtable/backups/update b/gcloud/beta/bigtable/backups/update index af394816d..0c0d14bad 100644 --- a/gcloud/beta/bigtable/backups/update +++ b/gcloud/beta/bigtable/backups/update @@ -16,8 +16,8 @@ EXAMPLES To update the expire time of backup 'BACKUP_NAME' to 7 days from now, run: $ gcloud beta bigtable backups update BACKUP_NAME \ - --instance=INSTANCE_NAME --cluster=CLUSTER_NAME - --retention-period=7d + --instance=INSTANCE_NAME --cluster=CLUSTER_NAME \ + --retention-period=7d POSITIONAL ARGUMENTS Backup resource - Cloud Bigtable backup to update. The arguments in this diff --git a/gcloud/beta/builds/submit b/gcloud/beta/builds/submit index 29ab6b030..32a249f39 100644 --- a/gcloud/beta/builds/submit +++ b/gcloud/beta/builds/submit @@ -25,7 +25,7 @@ EXAMPLES To submit a build with source located at storage URL gs://bucket/object.zip: - $ gcloud beta builds submit "gs://bucket/object.zip" \ + $ gcloud beta builds submit "gs://bucket/object.zip" \ --tag=gcr.io/my-project/image To submit a build with source located at storage URL gs://bucket/object.zip diff --git a/gcloud/beta/builds/worker-pools/create b/gcloud/beta/builds/worker-pools/create index 54b7575cc..58e34241b 100644 --- a/gcloud/beta/builds/worker-pools/create +++ b/gcloud/beta/builds/worker-pools/create @@ -21,10 +21,9 @@ EXAMPLES projects/123/global/networks/default and have a disk size of 64GB, run: $ gcloud beta builds worker-pools create wp1 --project=p1 \ - --region=us-central1 \ - --peered-network=projects/123/global/networks/default \ - --worker-machine-type=e2-standard-2 \ - --worker-disk-size=64GB + --region=us-central1 \ + --peered-network=projects/123/global/networks/default \ + --worker-machine-type=e2-standard-2 --worker-disk-size=64GB POSITIONAL ARGUMENTS WORKER_POOL diff --git a/gcloud/beta/builds/worker-pools/update b/gcloud/beta/builds/worker-pools/update index 11442f25a..824bacd5f 100644 --- a/gcloud/beta/builds/worker-pools/update +++ b/gcloud/beta/builds/worker-pools/update @@ -15,9 +15,8 @@ EXAMPLES To change the machine type and disk size of workers in a worker pool named wp1, run: - $ gcloud beta builds worker-pools update wp1 --region=us-central1 \ - --worker-machine-type=e2-standard-2 \ - --worker-disk-size=64GB + $ gcloud beta builds worker-pools update wp1 --region=us-central1 \ + --worker-machine-type=e2-standard-2 --worker-disk-size=64GB POSITIONAL ARGUMENTS WORKER_POOL diff --git a/gcloud/beta/certificate-manager/certificates/create b/gcloud/beta/certificate-manager/certificates/create index ce13c0c5d..cb1261515 100644 --- a/gcloud/beta/certificate-manager/certificates/create +++ b/gcloud/beta/certificate-manager/certificates/create @@ -37,7 +37,7 @@ EXAMPLES $ gcloud beta certificate-manager certificates create \ api-example-com --dns-authorizations=api-example-com \ - --domains="api.example.com" + --domains="api.example.com" POSITIONAL ARGUMENTS Certificate resource - The name of the certificate to create. The diff --git a/gcloud/beta/certificate-manager/certificates/update b/gcloud/beta/certificate-manager/certificates/update index 39ddd6fc2..733d35a99 100644 --- a/gcloud/beta/certificate-manager/certificates/update +++ b/gcloud/beta/certificate-manager/certificates/update @@ -16,7 +16,7 @@ EXAMPLES To update a certificate with name simple-cert, run: $ gcloud beta certificate-manager certificates update simple-cert \ - --description="desc" --update-labels="key=value" + --description="desc" --update-labels="key=value" \ --certificate-file=cert.pem --private-key-file=key.pem POSITIONAL ARGUMENTS diff --git a/gcloud/beta/certificate-manager/maps/entries/update b/gcloud/beta/certificate-manager/maps/entries/update index cfc3a20a6..c3b18033f 100644 --- a/gcloud/beta/certificate-manager/maps/entries/update +++ b/gcloud/beta/certificate-manager/maps/entries/update @@ -16,8 +16,8 @@ EXAMPLES To update a certificate map entry with name simple-entry, run: $ gcloud beta certificate-manager maps entries update simple-entry \ - --map="simple-map" --description="desc" - --update-labels="key=value" --certificates="simple-cert" + --map="simple-map" --description="desc" \ + --update-labels="key=value" --certificates="simple-cert" POSITIONAL ARGUMENTS Certificate map entry resource - The certificate map entry to update. The diff --git a/gcloud/beta/code/dev b/gcloud/beta/code/dev index 8df3a2e95..8734e57b8 100644 --- a/gcloud/beta/code/dev +++ b/gcloud/beta/code/dev @@ -33,8 +33,8 @@ EXAMPLES this command with the --application-default-credential flag. $ gcloud auth application-default login - $ gcloud beta code dev --dockerfile= \ - --application-default-credential + $ gcloud beta code dev --dockerfile= \ + --application-default-credential POSITIONAL ARGUMENTS [SERVICE_CONFIG] diff --git a/gcloud/beta/compute/addresses/create b/gcloud/beta/compute/addresses/create index 9e7daaf6f..5096da6ee 100644 --- a/gcloud/beta/compute/addresses/create +++ b/gcloud/beta/compute/addresses/create @@ -41,28 +41,27 @@ EXAMPLES $ gcloud beta compute addresses create SHARED-ADDRESS-1 \ --region=us-central1 --subnet=default \ - --purpose=SHARED_LOADBALANCER_VIP + --purpose=SHARED_LOADBALANCER_VIP To reserve an IP range '10.110.0.0/16' from the network 'default' for 'VPC_PEERING', run: $ gcloud beta compute addresses create IP-RANGE-1 --global \ --addresses=10.110.0.0 --prefix-length=16 \ - --purpose=VPC_PEERING --network=default + --purpose=VPC_PEERING --network=default To reserve any IP range with prefix length '16' from the network 'default' for 'VPC_PEERING', run: $ gcloud beta compute addresses create IP-RANGE-1 --global \ - --prefix-length=16 --purpose=VPC_PEERING \ - --network=default + --prefix-length=16 --purpose=VPC_PEERING --network=default To reserve an address from network 'default' for PRIVATE_SERVICE_CONNECT, run: $ gcloud beta compute addresses create PSC-ADDRESS-1 --global \ - --addresses=10.110.0.10 \ - --purpose=PRIVATE_SERVICE_CONNECT --network=default + --addresses=10.110.0.10 --purpose=PRIVATE_SERVICE_CONNECT \ + --network=default POSITIONAL ARGUMENTS [NAME ...] diff --git a/gcloud/beta/compute/addresses/update b/gcloud/beta/compute/addresses/update index f67e596f1..f0a96db85 100644 --- a/gcloud/beta/compute/addresses/update +++ b/gcloud/beta/compute/addresses/update @@ -15,8 +15,8 @@ EXAMPLES address 'example-address', run: $ gcloud beta compute addresses update example-address \ - --region=us-central1 \ - --update-labels=k0=value1,k1=value2 --remove-labels=k3 + --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: diff --git a/gcloud/beta/compute/backend-services/add-service-bindings b/gcloud/beta/compute/backend-services/add-service-bindings index 21de4a2fb..3bb74fb14 100644 --- a/gcloud/beta/compute/backend-services/add-service-bindings +++ b/gcloud/beta/compute/backend-services/add-service-bindings @@ -13,8 +13,8 @@ DESCRIPTION EXAMPLES To add a service binding to a backend service, run: - $ gcloud beta compute backend-services add-service-bindings NAME \ - --service-bindings=SERVICE_BINDING1 --global + $ gcloud beta compute backend-services add-service-bindings NAME \ + --service-bindings=SERVICE_BINDING1 --global POSITIONAL ARGUMENTS BACKEND_SERVICE_NAME diff --git a/gcloud/beta/compute/backend-services/remove-service-bindings b/gcloud/beta/compute/backend-services/remove-service-bindings index fb684175e..a8a85cd30 100644 --- a/gcloud/beta/compute/backend-services/remove-service-bindings +++ b/gcloud/beta/compute/backend-services/remove-service-bindings @@ -14,7 +14,7 @@ EXAMPLES To remove a service binding from a backend service, run: $ gcloud beta compute backend-services remove-service-bindings \ - NAME --service-bindings=SERVICE_BINDING1 --global + NAME --service-bindings=SERVICE_BINDING1 --global POSITIONAL ARGUMENTS BACKEND_SERVICE_NAME diff --git a/gcloud/beta/compute/disks/create b/gcloud/beta/compute/disks/create index 8ea7ae059..0a7fb0671 100644 --- a/gcloud/beta/compute/disks/create +++ b/gcloud/beta/compute/disks/create @@ -293,14 +293,14 @@ FLAGS At most one of these can be specified: --source-disk-region=SOURCE_DISK_REGION - Region of the source disk, this argument is not required if target - disk is in same region of source disk. Overrides the default - compute/region property value for this command invocation. + Region of the source disk. This argument is not required if the + target disk is in the same region as the source disk. Overrides the + default compute/region property value for this command invocation. --source-disk-zone=SOURCE_DISK_ZONE - Zone of the source disk, this argument is not required if target disk - is in same zone of source disk. Overrides the default compute/zone - property value for this command invocation. + Zone of the source disk. This argument is not required if the target + disk is in the same zone as the source disk. 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, diff --git a/gcloud/beta/compute/external-vpn-gateways/update b/gcloud/beta/compute/external-vpn-gateways/update index 851b51217..d80f1194a 100644 --- a/gcloud/beta/compute/external-vpn-gateways/update +++ b/gcloud/beta/compute/external-vpn-gateways/update @@ -31,8 +31,7 @@ EXAMPLES To update labels for an external VPN gateway, run: $ gcloud beta compute external-vpn-gateways update \ - my-external-gateway \ - --update-labels=k0=value1,k1=value2 + my-external-gateway --update-labels=k0=value1,k1=value2 POSITIONAL ARGUMENTS NAME diff --git a/gcloud/beta/compute/firewall-policies/rules/create b/gcloud/beta/compute/firewall-policies/rules/create index 970e86506..c1aa3ded7 100644 --- a/gcloud/beta/compute/firewall-policies/rules/create +++ b/gcloud/beta/compute/firewall-policies/rules/create @@ -22,8 +22,8 @@ EXAMPLES with ID ``123456789", run: $ gcloud beta compute firewall-policies rules create 10 \ - --firewall-policy=123456789 --action=allow - --description=example-rule + --firewall-policy=123456789 --action=allow \ + --description=example-rule POSITIONAL ARGUMENTS PRIORITY diff --git a/gcloud/beta/compute/firewall-policies/rules/update b/gcloud/beta/compute/firewall-policies/rules/update index 9a0cd058d..8924e6a92 100644 --- a/gcloud/beta/compute/firewall-policies/rules/update +++ b/gcloud/beta/compute/firewall-policies/rules/update @@ -23,8 +23,8 @@ EXAMPLES ``new-example-rule", run: $ gcloud beta compute firewall-policies rules update 10 \ - --firewall-policy=123456789 --action=allow - --description=new-example-rule + --firewall-policy=123456789 --action=allow \ + --description=new-example-rule POSITIONAL ARGUMENTS PRIORITY diff --git a/gcloud/beta/compute/firewall-rules/create b/gcloud/beta/compute/firewall-rules/create index 36207708b..bdab12ad5 100644 --- a/gcloud/beta/compute/firewall-rules/create +++ b/gcloud/beta/compute/firewall-rules/create @@ -25,15 +25,17 @@ EXAMPLES To create a firewall rule allowing incoming TCP traffic on port 8080, run: $ gcloud beta compute firewall-rules create FooService \ - --allow=tcp:8080 - --description="Allow incoming traffic on TCP port 8080" --direction=INGRESS + --allow=tcp:8080 \ + --description="Allow incoming traffic on TCP port 8080" \ + --direction=INGRESS To create a firewall rule that allows TCP traffic through port 80 and determines a list of specific IP address blocks that are allowed to make inbound connections, run: - $ gcloud beta compute firewall-rules create "tcp-rule" --allow=tcp:80 - --source-ranges="10.0.0.0/22,10.0.0.0/14" --description="Narrowing TCP traffic" + $ gcloud beta compute firewall-rules create "tcp-rule" \ + --allow=tcp:80 --source-ranges="10.0.0.0/22,10.0.0.0/14" \ + --description="Narrowing TCP traffic" To list existing firewall rules, run: diff --git a/gcloud/beta/compute/forwarding-rules/update b/gcloud/beta/compute/forwarding-rules/update index 04a66d456..392b4c32f 100644 --- a/gcloud/beta/compute/forwarding-rules/update +++ b/gcloud/beta/compute/forwarding-rules/update @@ -22,8 +22,8 @@ EXAMPLES To add/update labels k0 and k1 and remove labels with key k3, run: $ gcloud beta compute forwarding-rules update example-fr \ - --region=us-central1 \ - --update-labels=k0=value1,k1=value2 --remove-labels=k3 + --region=us-central1 --update-labels=k0=value1,k1=value2 \ + --remove-labels=k3 Labels can be used to identify the forwarding rule and to filter them as in diff --git a/gcloud/beta/compute/instance-groups/managed/create-instance b/gcloud/beta/compute/instance-groups/managed/create-instance index ab87ff725..bc013fd4d 100644 --- a/gcloud/beta/compute/instance-groups/managed/create-instance +++ b/gcloud/beta/compute/instance-groups/managed/create-instance @@ -33,12 +33,15 @@ EXAMPLES IP on interface nic1, run: $ gcloud beta compute instance-groups managed create-instance \ - my-group --region=europe-west4 \ - --instance=instance-1 \ - --stateful-disk='device-name=foo,source=https://compute.googleapis.com/compute/alpha/projects/my-project/zones/europe-west4/disks/disk-1,mode=rw,auto-delete=on-permanent-instance-deletion' \ - --stateful-metadata='my-key=my-value' \ - --stateful-internal-ip=address=192.168.0.10,auto-delete=on-permanent-instance-deletion \ - --stateful-external-ip=address=/projects/example-project/regions/europe-west4/addresses/my-address,interface-name=nic1 + my-group --region=europe-west4 --instance=instance-1 \ + --stateful-disk='device-name=foo,source=https://compute.googleap\ + is.com/compute/alpha/projects/my-project/zones/europe-west4/disks/di\ + sk-1,mode=rw,auto-delete=on-permanent-instance-deletion' \ + --stateful-metadata='my-key=my-value' \ + --stateful-internal-ip=address=192.168.0.10,\ + auto-delete=on-permanent-instance-deletion \ + --stateful-external-ip=address=/projects/example-project/\ + regions/europe-west4/addresses/my-address,interface-name=nic1 POSITIONAL ARGUMENTS NAME diff --git a/gcloud/beta/compute/instance-groups/managed/describe-instance b/gcloud/beta/compute/instance-groups/managed/describe-instance index b7e9415e1..570739bda 100644 --- a/gcloud/beta/compute/instance-groups/managed/describe-instance +++ b/gcloud/beta/compute/instance-groups/managed/describe-instance @@ -17,8 +17,7 @@ EXAMPLES run: $ gcloud beta compute instance-groups managed describe-instance \ - my-group --instance=instance-1 \ - --region=europe-west4 + my-group --instance=instance-1 --region=europe-west4 POSITIONAL ARGUMENTS NAME diff --git a/gcloud/beta/compute/instance-groups/managed/list-errors b/gcloud/beta/compute/instance-groups/managed/list-errors index fd5541f7e..08ab779c3 100644 --- a/gcloud/beta/compute/instance-groups/managed/list-errors +++ b/gcloud/beta/compute/instance-groups/managed/list-errors @@ -34,8 +34,8 @@ DESCRIPTION EXAMPLES To list errors on managed instance group 'my-group', run: - $ gcloud beta compute instance-groups managed list-errors \ - my-group --format=yaml + $ gcloud beta compute instance-groups managed list-errors my-group \ + --format=yaml POSITIONAL ARGUMENTS NAME diff --git a/gcloud/beta/compute/instance-groups/managed/list-instances b/gcloud/beta/compute/instance-groups/managed/list-instances index 30ad38cab..7df21d228 100644 --- a/gcloud/beta/compute/instance-groups/managed/list-instances +++ b/gcloud/beta/compute/instance-groups/managed/list-instances @@ -36,7 +36,7 @@ EXAMPLES my-group, including per-instance overrides, run: $ gcloud beta compute instance-groups managed list-instances \ - my-group --format=yaml + my-group --format=yaml POSITIONAL ARGUMENTS NAME diff --git a/gcloud/beta/compute/instance-groups/managed/update-instances b/gcloud/beta/compute/instance-groups/managed/update-instances index 1ee4a2a4d..241c7b4d2 100644 --- a/gcloud/beta/compute/instance-groups/managed/update-instances +++ b/gcloud/beta/compute/instance-groups/managed/update-instances @@ -35,9 +35,8 @@ EXAMPLES minimal-action=none and most-disruptive-allowed-action=restart, run: $ gcloud beta compute instance-groups managed update-instances \ - my-group --instances=instance-1,instance2 \ - --minimal-action=none - --most-disruptive-allowed-action=restart + my-group --instances=instance-1,instance2 \ + --minimal-action=none --most-disruptive-allowed-action=restart POSITIONAL ARGUMENTS NAME diff --git a/gcloud/beta/compute/instance-templates/create-with-container b/gcloud/beta/compute/instance-templates/create-with-container index 4a04fe48d..33a72aebc 100644 --- a/gcloud/beta/compute/instance-templates/create-with-container +++ b/gcloud/beta/compute/instance-templates/create-with-container @@ -64,16 +64,16 @@ EXAMPLES a command, run: $ gcloud beta compute instance-templates create-with-container \ - instance-template-1 \ - --container-image=gcr.io/google-containers/busybox \ + instance-template-1 \ + --container-image=gcr.io/google-containers/busybox \ --container-command='echo "Hello world"' To create a template running gcr.io/google-containers/busybox in privileged mode, run: $ gcloud beta compute instance-templates create-with-container \ - instance-template-1 \ - --container-image=gcr.io/google-containers/busybox \ + instance-template-1 \ + --container-image=gcr.io/google-containers/busybox \ --container-privileged POSITIONAL ARGUMENTS diff --git a/gcloud/beta/compute/instances/create-with-container b/gcloud/beta/compute/instances/create-with-container index a4e3843e1..ff0501cd0 100644 --- a/gcloud/beta/compute/instances/create-with-container +++ b/gcloud/beta/compute/instances/create-with-container @@ -72,15 +72,15 @@ EXAMPLES To run the gcr.io/google-containers/busybox image on an instance named 'instance-1' that executes 'echo "Hello world"' as a run command, run: - $ gcloud beta compute instances create-with-container instance-1 \ - --container-image=gcr.io/google-containers/busybox \ - --container-command='echo "Hello world"' + $ gcloud beta compute instances create-with-container instance-1 \ + --container-image=gcr.io/google-containers/busybox \ + --container-command='echo "Hello world"' To run the gcr.io/google-containers/busybox image in privileged mode, run: - $ gcloud beta compute instances create-with-container instance-1 \ - --container-image=gcr.io/google-containers/busybox - --container-privileged + $ gcloud beta compute instances create-with-container instance-1 \ + --container-image=gcr.io/google-containers/busybox \ + --container-privileged POSITIONAL ARGUMENTS INSTANCE_NAMES [INSTANCE_NAMES ...] diff --git a/gcloud/beta/compute/instances/network-interfaces/get-effective-firewalls b/gcloud/beta/compute/instances/network-interfaces/get-effective-firewalls index 3dbbed5de..db8161345 100644 --- a/gcloud/beta/compute/instances/network-interfaces/get-effective-firewalls +++ b/gcloud/beta/compute/instances/network-interfaces/get-effective-firewalls @@ -20,7 +20,8 @@ EXAMPLES To get the effective firewalls of instance with name example-instance, run: $ gcloud beta compute instances network-interfaces \ - get-effective-firewalls example-instance, + get-effective-firewalls example-instance + To show all fields of the firewall rules, please show in JSON format with option --format=json diff --git a/gcloud/beta/compute/instances/os-inventory/list-instances b/gcloud/beta/compute/instances/os-inventory/list-instances index 29aaad371..291d2103c 100644 --- a/gcloud/beta/compute/instances/os-inventory/list-instances +++ b/gcloud/beta/compute/instances/os-inventory/list-instances @@ -37,43 +37,39 @@ EXAMPLES installed, run: $ gcloud beta compute instances os-inventory list-instances \ - --package-name="google-cloud-sdk" \ - --package-version="235.0.0-0" + --package-name="google-cloud-sdk" --package-version="235.0.0-0" To list all instances with package name matching a regex ^google-cloud available for update through apt, run: $ gcloud beta compute instances os-inventory list-instances \ - --inventory-filter="\ - PackageUpdates.apt[].Name~^google-cloud*" + --inventory-filter="PackageUpdates.apt[].Name~^google-cloud*" To list all instances with package update google-cloud-sdk of version greater than or equal to 235.0.0-0 available through apt, run: $ gcloud beta compute instances os-inventory list-instances \ - --inventory-filter="\ - PackageUpdates.apt[].['google-cloud-sdk'].Version>=235.0.0-0" + --inventory-filter="PackageUpdates.apt[].['google-cloud-sdk'].Ve\ + rsion>=235.0.0-0" To list all instances missing the Stackdriver monitoring package stackdriver-agent, run: $ gcloud beta compute instances os-inventory list-instances \ - --inventory-filter="\ - NOT(InstalledPackages:stackdriver-agent)" + --inventory-filter="NOT(InstalledPackages:stackdriver-agent)" To list all Windows instances with an installed qfe hotfix whose ID equals KB4462930, run: $ gcloud beta compute instances os-inventory list-instances \ - --inventory-filter="\ - InstalledPackages.qfe[].HotFixID=KB4462930" + --inventory-filter="InstalledPackages.qfe[].HotFixID=KB4462930" To list all Windows instances with a wua update whose description contains the word Security, run: $ gcloud beta compute instances os-inventory list-instances \ - --inventory-filter="\ - InstalledPackages.wua[].Description:Security" + --inventory-filter="InstalledPackages.wua[].Description:Security\ + " FLAGS --inventory-filter=INVENTORY_FILTER diff --git a/gcloud/beta/compute/instances/set-iam-policy b/gcloud/beta/compute/instances/set-iam-policy index 13ce8d40c..ac8cc476e 100644 --- a/gcloud/beta/compute/instances/set-iam-policy +++ b/gcloud/beta/compute/instances/set-iam-policy @@ -11,8 +11,11 @@ DESCRIPTION EXAMPLES The following command reads an IAM policy defined in a JSON file - policy.json and sets it for the instance 'my-instance' and zone 'ZONE': $ gcloud beta compute instances set-iam-policy my-instance \ + policy.json and sets it for the instance 'my-instance' and zone 'ZONE': + + $ gcloud beta compute instances set-iam-policy my-instance \ --zone=ZONE policy.json + See https://cloud.google.com/iam/docs/managing-policies for details of policy role and member types. diff --git a/gcloud/beta/compute/instances/set-scheduling b/gcloud/beta/compute/instances/set-scheduling index c3ded34fe..13c1d8160 100644 --- a/gcloud/beta/compute/instances/set-scheduling +++ b/gcloud/beta/compute/instances/set-scheduling @@ -19,7 +19,7 @@ DESCRIPTION EXAMPLES To set instance to be terminated during maintenance, run: - $ gcloud beta compute instances set-scheduling example-instance \ + $ gcloud beta compute instances set-scheduling example-instance \ --maintenance-policy=TERMINATE --zone=us-central1-b POSITIONAL ARGUMENTS diff --git a/gcloud/beta/compute/instances/update-access-config b/gcloud/beta/compute/instances/update-access-config index 7714c2459..f6099c360 100644 --- a/gcloud/beta/compute/instances/update-access-config +++ b/gcloud/beta/compute/instances/update-access-config @@ -20,7 +20,7 @@ EXAMPLES To update network interface of an instance to 'nic0', run: $ gcloud beta compute instances update-access-config \ - example-instance --network-interface=nic0 --zone=us-central1-b + example-instance --network-interface=nic0 --zone=us-central1-b POSITIONAL ARGUMENTS INSTANCE_NAME diff --git a/gcloud/beta/compute/instances/update-container b/gcloud/beta/compute/instances/update-container index bbfea7924..5ea136684 100644 --- a/gcloud/beta/compute/instances/update-container +++ b/gcloud/beta/compute/instances/update-container @@ -40,14 +40,14 @@ EXAMPLES To run the gcr.io/google-containers/busybox image on an instance named 'instance-1' that executes 'echo "Hello world"' as a run command, run: - $ gcloud beta compute instances update-container instance-1 \ - --container-image=gcr.io/google-containers/busybox \ + $ gcloud beta compute instances update-container instance-1 \ + --container-image=gcr.io/google-containers/busybox \ --container-command='echo "Hello world"' To run the gcr.io/google-containers/busybox image in privileged mode, run: - $ gcloud beta compute instances update-container instance-1 \ - --container-image=gcr.io/google-containers/busybox \ + $ gcloud beta compute instances update-container instance-1 \ + --container-image=gcr.io/google-containers/busybox \ --container-privileged POSITIONAL ARGUMENTS diff --git a/gcloud/beta/compute/networks/create b/gcloud/beta/compute/networks/create index bb0e64388..e5d0a1465 100644 --- a/gcloud/beta/compute/networks/create +++ b/gcloud/beta/compute/networks/create @@ -24,8 +24,7 @@ EXAMPLES run: $ gcloud beta compute networks create network-name \ - --bgp-routing-mode=global \ - --subnet-mode=custom + --bgp-routing-mode=global --subnet-mode=custom POSITIONAL ARGUMENTS NAME diff --git a/gcloud/beta/compute/networks/get-effective-firewalls b/gcloud/beta/compute/networks/get-effective-firewalls index bb1df6d6d..e4cfe1780 100644 --- a/gcloud/beta/compute/networks/get-effective-firewalls +++ b/gcloud/beta/compute/networks/get-effective-firewalls @@ -16,7 +16,8 @@ EXAMPLES To get the effective firewalls of network with name example-network, run: $ gcloud beta compute networks get-effective-firewalls \ - example-network, + example-network + To show all fields of the firewall rules, please show in JSON format with option --format=json diff --git a/gcloud/beta/compute/networks/peerings/create b/gcloud/beta/compute/networks/peerings/create index 6356085f4..11c79c954 100644 --- a/gcloud/beta/compute/networks/peerings/create +++ b/gcloud/beta/compute/networks/peerings/create @@ -21,12 +21,10 @@ EXAMPLES imports custom routes and subnet routes with public IPs, run: $ gcloud beta compute networks peerings create peering-name \ - --network=local-network \ - --peer-network=peer-network \ - --export-custom-routes \ - --import-custom-routes \ - --export-subnet-routes-with-public-ip \ - --import-subnet-routes-with-public-ip + --network=local-network --peer-network=peer-network \ + --export-custom-routes --import-custom-routes \ + --export-subnet-routes-with-public-ip \ + --import-subnet-routes-with-public-ip POSITIONAL ARGUMENTS NAME diff --git a/gcloud/beta/compute/networks/peerings/delete b/gcloud/beta/compute/networks/peerings/delete index dcc1209f9..06e392b01 100644 --- a/gcloud/beta/compute/networks/peerings/delete +++ b/gcloud/beta/compute/networks/peerings/delete @@ -15,7 +15,7 @@ EXAMPLES 'local-network', run: $ gcloud beta compute networks peerings delete peering-name \ - --network=local-network + --network=local-network POSITIONAL ARGUMENTS NAME diff --git a/gcloud/beta/compute/networks/peerings/list-routes b/gcloud/beta/compute/networks/peerings/list-routes index 1f522a74c..f929b45fa 100644 --- a/gcloud/beta/compute/networks/peerings/list-routes +++ b/gcloud/beta/compute/networks/peerings/list-routes @@ -16,9 +16,8 @@ DESCRIPTION EXAMPLES List received routes for VPC network peering in us-central1: - $ gcloud beta compute networks peerings list-routes peering-name \ - --network=network-name --region=us-central1 \ - --direction=INCOMING + $ gcloud beta compute networks peerings list-routes peering-name \ + --network=network-name --region=us-central1 --direction=INCOMING POSITIONAL ARGUMENTS NAME diff --git a/gcloud/beta/compute/networks/peerings/update b/gcloud/beta/compute/networks/peerings/update index e665d4278..d02016a5e 100644 --- a/gcloud/beta/compute/networks/peerings/update +++ b/gcloud/beta/compute/networks/peerings/update @@ -13,15 +13,14 @@ EXAMPLES routes, run: $ gcloud beta compute networks peerings update peering-name \ - --export-custom-routes \ - --import-custom-routes + --export-custom-routes --import-custom-routes To update the peering named peering-name to both export and import subnet routes with public ip, run: $ gcloud beta compute networks peerings update peering-name \ - --export-subnet-routes-with-public-ip \ - --import-subnet-routes-with-public-ip + --export-subnet-routes-with-public-ip \ + --import-subnet-routes-with-public-ip POSITIONAL ARGUMENTS NAME diff --git a/gcloud/beta/compute/networks/update b/gcloud/beta/compute/networks/update index 5bec0e3d9..de05e4f81 100644 --- a/gcloud/beta/compute/networks/update +++ b/gcloud/beta/compute/networks/update @@ -14,13 +14,13 @@ EXAMPLES To update regional network with the name 'network-name' to global, run: $ gcloud beta compute networks update network-name \ - --bgp-routing-mode=global + --bgp-routing-mode=global To update an auto subnet mode network with the name 'network-name' to custom subnet mode, run: $ gcloud beta compute networks update network-name \ - --switch-to-custom-subnet-mode + --switch-to-custom-subnet-mode POSITIONAL ARGUMENTS NAME diff --git a/gcloud/beta/compute/networks/vpc-access/connectors/create b/gcloud/beta/compute/networks/vpc-access/connectors/create index 76181a4ec..d14d71df2 100644 --- a/gcloud/beta/compute/networks/vpc-access/connectors/create +++ b/gcloud/beta/compute/networks/vpc-access/connectors/create @@ -25,8 +25,8 @@ EXAMPLES CIDR range of '10.132.0.0/28'. $ gcloud beta compute networks vpc-access connectors create \ - my-vpc-connector --region=us-central1 --network=my-network - --range=10.132.0.0/28 + my-vpc-connector --region=us-central1 --network=my-network \ + --range=10.132.0.0/28 POSITIONAL ARGUMENTS Connector resource - Arguments and flags that specify the VPC Access diff --git a/gcloud/beta/compute/networks/vpc-access/operations/describe b/gcloud/beta/compute/networks/vpc-access/operations/describe index a89b33cf5..bad4fea42 100644 --- a/gcloud/beta/compute/networks/vpc-access/operations/describe +++ b/gcloud/beta/compute/networks/vpc-access/operations/describe @@ -20,8 +20,8 @@ EXAMPLES region us-central1: $ gcloud beta compute networks vpc-access operations describe \ - operation-1564112342235-435a134f8c3f8-81bb4b49-0830c1f8 - --region=us-central + operation-1564112342235-435a134f8c3f8-81bb4b49-0830c1f8 \ + --region=us-central POSITIONAL ARGUMENTS Operation resource - The operation to describe. The arguments in this diff --git a/gcloud/beta/compute/org-security-policies/rules/create b/gcloud/beta/compute/org-security-policies/rules/create index bafbd31aa..a3e25273d 100644 --- a/gcloud/beta/compute/org-security-policies/rules/create +++ b/gcloud/beta/compute/org-security-policies/rules/create @@ -22,8 +22,8 @@ EXAMPLES with ID ``123456789", run: $ gcloud beta compute org-security-policies rules create create 10 \ - --security-policy=123456789 --action=allow - --description=example-rule + --security-policy=123456789 --action=allow \ + --description=example-rule POSITIONAL ARGUMENTS PRIORITY diff --git a/gcloud/beta/compute/org-security-policies/rules/update b/gcloud/beta/compute/org-security-policies/rules/update index fc69e7ad3..2d7e1926e 100644 --- a/gcloud/beta/compute/org-security-policies/rules/update +++ b/gcloud/beta/compute/org-security-policies/rules/update @@ -23,8 +23,8 @@ EXAMPLES ``new-example-rule", run: $ gcloud beta compute org-security-policies rules update create 10 \ - --security-policy=123456789 --action=allow - --description=new-example-rule + --security-policy=123456789 --action=allow \ + --description=new-example-rule POSITIONAL ARGUMENTS PRIORITY diff --git a/gcloud/beta/compute/packet-mirrorings/create b/gcloud/beta/compute/packet-mirrorings/create index 98cf1b752..6d48b3ff8 100644 --- a/gcloud/beta/compute/packet-mirrorings/create +++ b/gcloud/beta/compute/packet-mirrorings/create @@ -19,19 +19,18 @@ EXAMPLES us-central1, and send the mirrored traffic to the collector-fr Forwarding Rule. - $ gcloud beta compute packet-mirrorings create my-pm - --network my-network --region us-central1 - --mirrored-subnets my-subnet --collector-ilb collector-fr - --filter-protocols tcp + $ gcloud beta compute packet-mirrorings create my-pm \ + --network my-network --region us-central1 \ + --mirrored-subnets my-subnet --collector-ilb collector-fr \ + --filter-protocols tcp Mirror all traffic between instances with tag t1 and external server with IP 11.22.33.44 in us-central1, and send the mirrored traffic to the collector-fr Forwarding Rule. - $ gcloud beta compute packet-mirrorings create my-pm - --network my-network --region us-central1 - --mirrored-tags t1 --collector-ilb collector-fr - --filter-cidr-ranges 11.22.33.44/32 + $ gcloud beta compute packet-mirrorings create my-pm \ + --network my-network --region us-central1 --mirrored-tags t1 \ + --collector-ilb collector-fr --filter-cidr-ranges 11.22.33.44/32 POSITIONAL ARGUMENTS NAME diff --git a/gcloud/beta/compute/packet-mirrorings/delete b/gcloud/beta/compute/packet-mirrorings/delete index 626d42c63..410e10bbe 100644 --- a/gcloud/beta/compute/packet-mirrorings/delete +++ b/gcloud/beta/compute/packet-mirrorings/delete @@ -12,8 +12,8 @@ DESCRIPTION EXAMPLES Delete the Packet Mirroring policy pm-1 in region us-central1. - $ gcloud beta compute packet-mirrorings delete pm-1 - --region us-central1 + $ gcloud beta compute packet-mirrorings delete pm-1 \ + --region us-central1 POSITIONAL ARGUMENTS NAME [NAME ...] diff --git a/gcloud/beta/compute/packet-mirrorings/describe b/gcloud/beta/compute/packet-mirrorings/describe index 7a638b9a0..2332fd4d5 100644 --- a/gcloud/beta/compute/packet-mirrorings/describe +++ b/gcloud/beta/compute/packet-mirrorings/describe @@ -12,8 +12,8 @@ DESCRIPTION EXAMPLES Describe the Packet Mirroring policy pm-1 in region us-central1. - $ gcloud beta compute packet-mirrorings describe pm-1 - --region us-central1 + $ gcloud beta compute packet-mirrorings describe pm-1 \ + --region us-central1 POSITIONAL ARGUMENTS NAME diff --git a/gcloud/beta/compute/packet-mirrorings/update b/gcloud/beta/compute/packet-mirrorings/update index 98dec49b9..81779ea17 100644 --- a/gcloud/beta/compute/packet-mirrorings/update +++ b/gcloud/beta/compute/packet-mirrorings/update @@ -28,23 +28,23 @@ DESCRIPTION EXAMPLES Stop mirroring by tags, add subnet-1 as a mirrored subnet. - $ gcloud beta compute packet-mirrorings update my-pm - --region us-central1 --clear-mirrored-tags + $ gcloud beta compute packet-mirrorings update my-pm \ + --region us-central1 --clear-mirrored-tags \ --add-mirrored-subnets subnet-1 Change the load-balancer to send mirrored traffic to. - $ gcloud beta compute packet-mirrorings update my-pm + $ gcloud beta compute packet-mirrorings update my-pm \ --region us-central1 --collector-ilb new-forwarding-rule Disable a Packet Mirroring policy. - $ gcloud beta compute packet-mirrorings update my-pm + $ gcloud beta compute packet-mirrorings update my-pm \ --region us-central1 --no-enable Re-enable a disabled Packet Mirroring policy. - $ gcloud beta compute packet-mirrorings update my-pm + $ gcloud beta compute packet-mirrorings update my-pm \ --region us-central1 --enable POSITIONAL ARGUMENTS diff --git a/gcloud/beta/compute/public-advertised-prefixes/create b/gcloud/beta/compute/public-advertised-prefixes/create index c179a021a..c71d0c3dd 100644 --- a/gcloud/beta/compute/public-advertised-prefixes/create +++ b/gcloud/beta/compute/public-advertised-prefixes/create @@ -12,7 +12,7 @@ EXAMPLES $ gcloud beta compute public-advertised-prefixes create \ my-public-advertised-prefix --range=120.120.10.0/24 \ - --dns-verification-ip=120.120.10.15 + --dns-verification-ip=120.120.10.15 POSITIONAL ARGUMENTS NAME diff --git a/gcloud/beta/compute/public-delegated-prefixes/create b/gcloud/beta/compute/public-delegated-prefixes/create index 9aef62cb3..8fa295bf4 100644 --- a/gcloud/beta/compute/public-delegated-prefixes/create +++ b/gcloud/beta/compute/public-delegated-prefixes/create @@ -13,7 +13,7 @@ EXAMPLES $ gcloud beta compute public-delegated-prefixes create \ my-public-delegated-prefix --public-advertised-prefix=my-pap \ - --range=120.120.10.128/27 --global + --range=120.120.10.128/27 --global POSITIONAL ARGUMENTS NAME diff --git a/gcloud/beta/compute/routers/nats/create b/gcloud/beta/compute/routers/nats/create index 3a29df6a4..9c226daea 100644 --- a/gcloud/beta/compute/routers/nats/create +++ b/gcloud/beta/compute/routers/nats/create @@ -26,14 +26,14 @@ DESCRIPTION EXAMPLES Auto-allocate NAT for all IP addresses of all subnets in the region: - $ gcloud beta compute routers nats create nat1 --router=my-router - --auto-allocate-nat-external-ips --nat-all-subnet-ip-ranges + $ gcloud beta compute routers nats create nat1 --router=my-router \ + --auto-allocate-nat-external-ips --nat-all-subnet-ip-ranges Specify IP addresses for NAT: Each IP address is the name of a reserved static IP address resource in the same region. - $ gcloud beta compute routers nats create nat1 --router=my-router - --nat-external-ip-pool=ip-address1,ip-address2 + $ gcloud beta compute routers nats create nat1 --router=my-router \ + --nat-external-ip-pool=ip-address1,ip-address2 Specify subnet ranges for NAT: @@ -41,9 +41,10 @@ EXAMPLES subnets in the region for the given VPC network. You can restrict which subnet primary and secondary ranges can use NAT. - $ gcloud beta compute routers nats create nat1 --router=my-router - --auto-allocate-nat-external-ips - --nat-custom-subnet-ip-ranges=subnet-1,subnet-3:secondary-range-1 + $ gcloud beta compute routers nats create nat1 --router=my-router \ + --auto-allocate-nat-external-ips \ + --nat-custom-subnet-ip-ranges=subnet-1,\ + subnet-3:secondary-range-1 POSITIONAL ARGUMENTS NAME diff --git a/gcloud/beta/compute/routers/nats/rules/create b/gcloud/beta/compute/routers/nats/rules/create index 1a212159e..01aadb9fb 100644 --- a/gcloud/beta/compute/routers/nats/rules/create +++ b/gcloud/beta/compute/routers/nats/rules/create @@ -17,9 +17,9 @@ EXAMPLES the CIDR Range "203.0.113.0/24". $ gcloud beta compute routers nats rules create 1 --nat=my-nat \ - --router=my-router --region=us-central1 - --match='inIpRange(destination.ip, "203.0.113.0/24")' - --source-nat-active-ips=a1 + --router=my-router --region=us-central1 \ + --match='inIpRange(destination.ip, "203.0.113.0/24")' \ + --source-nat-active-ips=a1 POSITIONAL ARGUMENTS RULE_NUMBER diff --git a/gcloud/beta/compute/routers/nats/rules/update b/gcloud/beta/compute/routers/nats/rules/update index 672d8f6c6..0df691d9a 100644 --- a/gcloud/beta/compute/routers/nats/rules/update +++ b/gcloud/beta/compute/routers/nats/rules/update @@ -19,9 +19,9 @@ EXAMPLES new connections matching Rule 1 in NAT nat-1, run: $ gcloud beta compute routers nats rules update 1 --nat=nat1 \ - --router=my-router --region=us-central1 - --source-nat-drain-ips=address-1 - --source-nat-active-ips=address-2 + --router=my-router --region=us-central1 \ + --source-nat-drain-ips=address-1 \ + --source-nat-active-ips=address-2 POSITIONAL ARGUMENTS RULE_NUMBER diff --git a/gcloud/beta/compute/routers/nats/update b/gcloud/beta/compute/routers/nats/update index 924bc0568..8b62cd0d9 100644 --- a/gcloud/beta/compute/routers/nats/update +++ b/gcloud/beta/compute/routers/nats/update @@ -32,9 +32,10 @@ DESCRIPTION EXAMPLES Change subnetworks and IP address resources associated with NAT: - $ gcloud beta compute routers nats update nat1 --router=my-router - --nat-external-ip-pool=ip-address2,ip-address3 - --nat-custom-subnet-ip-ranges=subnet-2,subnet-3:secondary-range-2 + $ gcloud beta compute routers nats update nat1 --router=my-router \ + --nat-external-ip-pool=ip-address2,ip-address3 \ + --nat-custom-subnet-ip-ranges=subnet-2,\ + subnet-3:secondary-range-2 Change minimum default ports allocated per VM associated with NAT: @@ -43,18 +44,18 @@ EXAMPLES Change connection timeouts associated with NAT: - $ gcloud beta compute routers nats update nat1 --router=my-router - --udp-mapping-idle-timeout=60s - --icmp-mapping-idle-timeout=60s - --tcp-established-connection-idle-timeout=60s - --tcp-transitory-connection-idle-timeout=60s + $ gcloud beta compute routers nats update nat1 --router=my-router \ + --udp-mapping-idle-timeout=60s --icmp-mapping-idle-timeout=60s \ + --tcp-established-connection-idle-timeout=60s \ + --tcp-transitory-connection-idle-timeout=60s Reset connection timeouts associated NAT to default values: - $ gcloud beta compute routers nats update nat1 --router=my-router - --clear-udp-mapping-idle-timeout --clear-icmp-mapping-idle-timeout - --clear-tcp-established-connection-idle-timeout - --clear-tcp-transitory-connection-idle-timeout + $ gcloud beta compute routers nats update nat1 --router=my-router \ + --clear-udp-mapping-idle-timeout \ + --clear-icmp-mapping-idle-timeout \ + --clear-tcp-established-connection-idle-timeout \ + --clear-tcp-transitory-connection-idle-timeout POSITIONAL ARGUMENTS NAME diff --git a/gcloud/beta/compute/routes/create b/gcloud/beta/compute/routes/create index 22b91bbb6..fea6c4755 100644 --- a/gcloud/beta/compute/routes/create +++ b/gcloud/beta/compute/routes/create @@ -42,8 +42,8 @@ EXAMPLES '0.0.0.0/0' and with next hop gateway 'default-internet-gateway', run: $ gcloud beta compute routes create route-name \ - --destination-range=0.0.0.0/0 \ - --next-hop-gateway=default-internet-gateway + --destination-range=0.0.0.0/0 \ + --next-hop-gateway=default-internet-gateway POSITIONAL ARGUMENTS NAME diff --git a/gcloud/beta/compute/shared-vpc/organizations/list-host-projects b/gcloud/beta/compute/shared-vpc/organizations/list-host-projects index 62c6dd878..2d096af5b 100644 --- a/gcloud/beta/compute/shared-vpc/organizations/list-host-projects +++ b/gcloud/beta/compute/shared-vpc/organizations/list-host-projects @@ -17,6 +17,7 @@ EXAMPLES $ gcloud beta compute shared-vpc organizations list-host-projects \ 12345 + NAME CREATION_TIMESTAMP XPN_PROJECT_STATUS xpn-host1 2000-01-01T12:00:00.00-00:00 HOST xpn-host2 2000-01-02T12:00:00.00-00:00 HOST diff --git a/gcloud/beta/compute/tpus/create b/gcloud/beta/compute/tpus/create index b6f898d6d..b71605b09 100644 --- a/gcloud/beta/compute/tpus/create +++ b/gcloud/beta/compute/tpus/create @@ -20,12 +20,9 @@ EXAMPLES The following command creates a TPU with ID my-tpu with explicit values for all required and optional parameters: - $ gcloud beta compute tpus create my-tpu \ - --zone=us-central1-a \ - --range='10.240.0.0/29' \ - --accelerator-type='v2-8' \ - --network=my-tf-network \ - --description='My TF Node' \ + $ gcloud beta compute tpus create my-tpu --zone=us-central1-a \ + --range='10.240.0.0/29' --accelerator-type='v2-8' \ + --network=my-tf-network --description='My TF Node' \ --version='1.1' POSITIONAL ARGUMENTS diff --git a/gcloud/beta/compute/tpus/execution-groups/create b/gcloud/beta/compute/tpus/execution-groups/create index 5ac8f45a7..2e3cf8d48 100644 --- a/gcloud/beta/compute/tpus/execution-groups/create +++ b/gcloud/beta/compute/tpus/execution-groups/create @@ -17,28 +17,31 @@ EXAMPLES To create both TPU and VM, run: $ gcloud beta compute tpus execution-groups create \ - --name=test-execution-group --zone=test-zone - --project=test-project --accelerator-type=v2-8 --tf-version=2.4.1 + --name=test-execution-group --zone=test-zone \ + --project=test-project --accelerator-type=v2-8 \ + --tf-version=2.4.1 To create both TPU and VM with additional flags, run: $ gcloud beta compute tpus execution-groups create \ --name=test-execution-group --zone=test-zone \ - --project=test-project --accelerator-type=v2-8 --tf-version=2.4.1 \ - --network=default --preemptible-vm --disk-size=100 \ - --machine-type=n1-standard-2 --use-dl-images + --project=test-project --accelerator-type=v2-8 \ + --tf-version=2.4.1 --network=default --preemptible-vm \ + --disk-size=100 --machine-type=n1-standard-2 --use-dl-images To create a VM only before creating the TPU, run: $ gcloud beta compute tpus execution-groups create \ --name=test-execution-group-tpu-only --zone=test-zone \ - --project=test-project --accelerator-type=v2-8 --tf-version=2.4.1 --tpu-only + --project=test-project --accelerator-type=v2-8 \ + --tf-version=2.4.1 --tpu-only To create the TPU only after the VM has been created, run: $ gcloud beta compute tpus execution-groups create \ --name=test-execution-group-tpu-only --zone=test-zone \ - --project=test-project --accelerator-type=v2-8 --tf-version=2.4.1 --vm-only + --project=test-project --accelerator-type=v2-8 \ + --tf-version=2.4.1 --vm-only FLAGS --accelerator-type=ACCELERATOR_TYPE; default="v2-8" diff --git a/gcloud/beta/compute/tpus/execution-groups/delete b/gcloud/beta/compute/tpus/execution-groups/delete index ae7df5a49..9ae3b8424 100644 --- a/gcloud/beta/compute/tpus/execution-groups/delete +++ b/gcloud/beta/compute/tpus/execution-groups/delete @@ -16,7 +16,7 @@ EXAMPLES $ gcloud beta compute tpus execution-groups delete \ test-execution-group --zone=test-zone --project=test-project \ - --tpu-only + --tpu-only POSITIONAL ARGUMENTS EXECUTION_GROUP_NAME diff --git a/gcloud/beta/compute/tpus/execution-groups/resume b/gcloud/beta/compute/tpus/execution-groups/resume index d35dee71f..fd07439cf 100644 --- a/gcloud/beta/compute/tpus/execution-groups/resume +++ b/gcloud/beta/compute/tpus/execution-groups/resume @@ -14,7 +14,7 @@ EXAMPLES $ gcloud beta compute tpus execution-groups resume \ test-execution-group --zone=test-zone --project=test-project \ - --accelerator-type=v2-8 --tf-version=2.4.1 + --accelerator-type=v2-8 --tf-version=2.4.1 POSITIONAL ARGUMENTS EXECUTION_GROUP_NAME diff --git a/gcloud/beta/compute/vpn-gateways/update b/gcloud/beta/compute/vpn-gateways/update index 5a37eda98..fd3162750 100644 --- a/gcloud/beta/compute/vpn-gateways/update +++ b/gcloud/beta/compute/vpn-gateways/update @@ -32,8 +32,7 @@ EXAMPLES To update labels for a VPN gateway, run: $ gcloud beta compute vpn-gateways update my-gateway \ - --region=us-central1 \ - --update-labels=k0=value1,k1=value2 + --region=us-central1 --update-labels=k0=value1,k1=value2 POSITIONAL ARGUMENTS NAME diff --git a/gcloud/beta/container/binauthz/attestations/create b/gcloud/beta/container/binauthz/attestations/create index bfd8a79a6..3b76f25b4 100644 --- a/gcloud/beta/container/binauthz/attestations/create +++ b/gcloud/beta/container/binauthz/attestations/create @@ -20,9 +20,9 @@ EXAMPLES resource path "projects/foo/attestors/bar", run: $ gcloud beta container binauthz attestations create \ - --project=my_proj \ - --artifact-url='gcr.io/example-project/example-image@sha256:abcd' \ - --attestor=projects/foo/attestors/bar \ + --project=my_proj \ + --artifact-url='gcr.io/example-project/example-image@sha256:abcd\ + ' --attestor=projects/foo/attestors/bar \ --signature-file=signed_artifact_attestation.pgp.sig \ --public-key-id=AAAA0000000000000000FFFFFFFFFFFFFFFFFFFF diff --git a/gcloud/beta/container/binauthz/attestations/list b/gcloud/beta/container/binauthz/attestations/list index 435ecf890..0ebbf557b 100644 --- a/gcloud/beta/container/binauthz/attestations/list +++ b/gcloud/beta/container/binauthz/attestations/list @@ -20,14 +20,14 @@ EXAMPLES attestor: $ gcloud beta container binauthz attestations list \ - --attestor=projects/foo/attestor/bar + --attestor=projects/foo/attestor/bar List the Occurrence messages for all attestations for the passed artifact-url bound to the passed attestor: $ gcloud beta container binauthz attestations list \ - --attestor=projects/foo/attestors/bar \ - --artifact-url='gcr.io/foo/example-image@sha256:abcd' + --attestor=projects/foo/attestors/bar \ + --artifact-url='gcr.io/foo/example-image@sha256:abcd' REQUIRED FLAGS Attestor resource - The Attestor whose Container Analysis Note will be diff --git a/gcloud/beta/container/binauthz/attestations/sign-and-create b/gcloud/beta/container/binauthz/attestations/sign-and-create index 37df02a42..4e31446de 100644 --- a/gcloud/beta/container/binauthz/attestations/sign-and-create +++ b/gcloud/beta/container/binauthz/attestations/sign-and-create @@ -26,14 +26,11 @@ EXAMPLES run: $ gcloud beta container binauthz attestations sign-and-create \ - --project=my_proj \ - --artifact-url='gcr.io/example-project/example-image@sha256:abcd' \ - --attestor=projects/foo/attestors/bar \ - --keyversion-project=foo \ - --keyversion-location=us-west1 \ - --keyversion-keyring=aring \ - --keyversion-key=akey \ - --keyversion=1 + --project=my_proj \ + --artifact-url='gcr.io/example-project/example-image@sha256:abcd\ + ' --attestor=projects/foo/attestors/bar --keyversion-project=foo \ + --keyversion-location=us-west1 --keyversion-keyring=aring \ + --keyversion-key=akey --keyversion=1 REQUIRED FLAGS --artifact-url=ARTIFACT_URL diff --git a/gcloud/beta/container/binauthz/attestors/create b/gcloud/beta/container/binauthz/attestors/create index e9feda6e9..13417a416 100644 --- a/gcloud/beta/container/binauthz/attestors/create +++ b/gcloud/beta/container/binauthz/attestors/create @@ -10,8 +10,7 @@ SYNOPSIS EXAMPLES To create an Attestor with an existing Note projects/my_proj/notes/my_note: - $ gcloud beta container binauthz attestors create \ - my_new_attestor + $ gcloud beta container binauthz attestors create my_new_attestor \ --attestation-authority-note=my_note \ --attestation-authority-note-project=my_proj \ diff --git a/gcloud/beta/container/binauthz/attestors/public-keys/add b/gcloud/beta/container/binauthz/attestors/public-keys/add index ad8eb8506..502c4aead 100644 --- a/gcloud/beta/container/binauthz/attestors/public-keys/add +++ b/gcloud/beta/container/binauthz/attestors/public-keys/add @@ -19,18 +19,14 @@ EXAMPLES To add a new KMS public key to an existing Attestor my_attestor: $ gcloud beta container binauthz attestors public-keys add \ - --attestor=my_attestor \ - --keyversion-project=foo \ - --keyversion-location=us-west1 \ - --keyversion-keyring=aring \ - --keyversion-key=akey \ - --keyversion=1 + --attestor=my_attestor --keyversion-project=foo \ + --keyversion-location=us-west1 --keyversion-keyring=aring \ + --keyversion-key=akey --keyversion=1 To add a new PGP public key to an existing Attestor my_attestor: $ gcloud beta container binauthz attestors public-keys add \ - --attestor=my_attestor \ - --pgp-public-key-file=my_key.pub + --attestor=my_attestor --pgp-public-key-file=my_key.pub REQUIRED FLAGS Attestor resource - The attestor to which the public key should be added. diff --git a/gcloud/beta/container/binauthz/attestors/public-keys/remove b/gcloud/beta/container/binauthz/attestors/public-keys/remove index 5478a1c5d..1f1eab13e 100644 --- a/gcloud/beta/container/binauthz/attestors/public-keys/remove +++ b/gcloud/beta/container/binauthz/attestors/public-keys/remove @@ -10,8 +10,7 @@ EXAMPLES To remove a public key from the Attestor my_attestor: $ gcloud beta container binauthz attestors public-keys remove \ - 0638AADD940361EA2D7F14C58C124F0E663DA097 \ - --attestor=my_attestor + 0638AADD940361EA2D7F14C58C124F0E663DA097 --attestor=my_attestor POSITIONAL ARGUMENTS PUBLIC_KEY_ID diff --git a/gcloud/beta/container/binauthz/attestors/public-keys/update b/gcloud/beta/container/binauthz/attestors/public-keys/update index 1e4da2e15..daa3e3e72 100644 --- a/gcloud/beta/container/binauthz/attestors/public-keys/update +++ b/gcloud/beta/container/binauthz/attestors/public-keys/update @@ -12,8 +12,7 @@ EXAMPLES $ gcloud beta container binauthz attestors public-keys update \ 0638AADD940361EA2D7F14C58C124F0E663DA097 \ - --attestor=my_attestor \ - --pgp-public-key-file=my_key.pub + --attestor=my_attestor --pgp-public-key-file=my_key.pub POSITIONAL ARGUMENTS PUBLIC_KEY_ID diff --git a/gcloud/beta/container/binauthz/create-signature-payload b/gcloud/beta/container/binauthz/create-signature-payload index 2d66ff55d..d554c30e5 100644 --- a/gcloud/beta/container/binauthz/create-signature-payload +++ b/gcloud/beta/container/binauthz/create-signature-payload @@ -15,7 +15,8 @@ EXAMPLES To output serialized JSON to sign, run: $ gcloud beta container binauthz create-signature-payload \ - --artifact-url="gcr.io/example-project/example-image@sha256:abcd" + --artifact-url="gcr.io/example-project/example-image@sha256:abcd\ + " REQUIRED FLAGS --artifact-url=ARTIFACT_URL diff --git a/gcloud/beta/container/clusters/create b/gcloud/beta/container/clusters/create index ddf0e84c5..1b60255bf 100644 --- a/gcloud/beta/container/clusters/create +++ b/gcloud/beta/container/clusters/create @@ -678,7 +678,7 @@ FLAGS --monitoring=[COMPONENT,...] Set the components that have monitoring enabled. Valid component values - are: SYSTEM, NONE + are: SYSTEM, WORKLOAD (Deprecated), NONE For more information, look at https://cloud.google.com/stackdriver/docs/solutions/gke/installing#available-metrics diff --git a/gcloud/beta/container/clusters/update b/gcloud/beta/container/clusters/update index be4764720..55706c8a8 100644 --- a/gcloud/beta/container/clusters/update +++ b/gcloud/beta/container/clusters/update @@ -941,7 +941,7 @@ REQUIRED FLAGS --monitoring=[COMPONENT,...] Set the components that have monitoring enabled. Valid component - values are: SYSTEM, NONE + values are: SYSTEM, WORKLOAD (Deprecated), NONE For more information, look at https://cloud.google.com/stackdriver/docs/solutions/gke/installing#available-metrics diff --git a/gcloud/beta/container/hub/cloudrun/apply b/gcloud/beta/container/hub/cloudrun/apply index 4df037324..bc9b899bf 100644 --- a/gcloud/beta/container/hub/cloudrun/apply +++ b/gcloud/beta/container/hub/cloudrun/apply @@ -16,7 +16,7 @@ EXAMPLES To apply the CloudRun YAML file, run: $ gcloud beta container hub cloudrun apply \ - --kubeconfig=/path/to/kubeconfig \ + --kubeconfig=/path/to/kubeconfig \ --config=/path/to/cloud-run-cr.yaml REQUIRED FLAGS diff --git a/gcloud/beta/container/hub/config-management/disable b/gcloud/beta/container/hub/config-management/disable index dd9c703fa..210ba067e 100644 --- a/gcloud/beta/container/hub/config-management/disable +++ b/gcloud/beta/container/hub/config-management/disable @@ -7,7 +7,7 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Disable the Config Management Feature in Hub. + (BETA) Disable the Config Management Feature in a fleet. EXAMPLES To disable the Config Management Feature, run: diff --git a/gcloud/beta/container/hub/config-management/enable b/gcloud/beta/container/hub/config-management/enable index 72183280c..209a578f7 100644 --- a/gcloud/beta/container/hub/config-management/enable +++ b/gcloud/beta/container/hub/config-management/enable @@ -6,7 +6,7 @@ SYNOPSIS gcloud beta container hub config-management enable [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Enables the Config Management Feature in Hub. + (BETA) Enables the Config Management Feature in a fleet. EXAMPLES To enable the Config Management Feature, run: diff --git a/gcloud/beta/container/hub/identity-service/describe b/gcloud/beta/container/hub/identity-service/describe index 0f425e3bf..8437e8d52 100644 --- a/gcloud/beta/container/hub/identity-service/describe +++ b/gcloud/beta/container/hub/identity-service/describe @@ -8,7 +8,8 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Prints the status of the Identity Service Feature resource in Hub. + (BETA) Prints the status of the Identity Service Feature resource in a + fleet. EXAMPLES To describe the status of the Identity Service configuration, run: diff --git a/gcloud/beta/container/hub/identity-service/disable b/gcloud/beta/container/hub/identity-service/disable index 8fd8ba9eb..cdcfa23cf 100644 --- a/gcloud/beta/container/hub/identity-service/disable +++ b/gcloud/beta/container/hub/identity-service/disable @@ -7,7 +7,7 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) This command disables the Identity Service Feature in Hub. + (BETA) This command disables the Identity Service Feature in a fleet. EXAMPLES To disable the Identity Service Feature, run: diff --git a/gcloud/beta/container/hub/identity-service/enable b/gcloud/beta/container/hub/identity-service/enable index db8eec119..1ed44cdea 100644 --- a/gcloud/beta/container/hub/identity-service/enable +++ b/gcloud/beta/container/hub/identity-service/enable @@ -6,7 +6,7 @@ SYNOPSIS gcloud beta container hub identity-service enable [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) This command enables the Identity Service Feature in Hub. + (BETA) This command enables the Identity Service Feature in a fleet. EXAMPLES To enable the Identity Service Feature, run: diff --git a/gcloud/beta/container/hub/ingress/describe b/gcloud/beta/container/hub/ingress/describe index a779d87ba..5ed60c5ee 100644 --- a/gcloud/beta/container/hub/ingress/describe +++ b/gcloud/beta/container/hub/ingress/describe @@ -7,7 +7,7 @@ SYNOPSIS DESCRIPTION (BETA) This command describes the status of Multi-cluster Ingress Feature - resource in Hub. + resource in fleet. EXAMPLES To describe the Ingress Feature, run: diff --git a/gcloud/beta/container/hub/ingress/disable b/gcloud/beta/container/hub/ingress/disable index 5b5bb3673..8e55ee892 100644 --- a/gcloud/beta/container/hub/ingress/disable +++ b/gcloud/beta/container/hub/ingress/disable @@ -6,7 +6,7 @@ SYNOPSIS gcloud beta container hub ingress disable [--force] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) This command disables Multi-cluster Ingress Feature in Hub. + (BETA) This command disables Multi-cluster Ingress Feature in a fleet. EXAMPLES To disable the Ingress Feature, run: diff --git a/gcloud/beta/container/hub/ingress/enable b/gcloud/beta/container/hub/ingress/enable index 262797410..e736cc1be 100644 --- a/gcloud/beta/container/hub/ingress/enable +++ b/gcloud/beta/container/hub/ingress/enable @@ -7,7 +7,7 @@ SYNOPSIS [--config-membership=CONFIG_MEMBERSHIP] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) This command enables Multi-cluster Ingress Feature in Hub. + (BETA) This command enables Multi-cluster Ingress Feature in a fleet. EXAMPLES To enable the Ingress Feature, run: diff --git a/gcloud/beta/container/hub/ingress/update b/gcloud/beta/container/hub/ingress/update index d6c248d80..4a6229fef 100644 --- a/gcloud/beta/container/hub/ingress/update +++ b/gcloud/beta/container/hub/ingress/update @@ -7,7 +7,7 @@ SYNOPSIS [--config-membership=CONFIG_MEMBERSHIP] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) This command updates Multi-cluster Ingress Feature in Hub. + (BETA) This command updates Multi-cluster Ingress Feature in a fleet. EXAMPLES To update the Ingress Feature, run: diff --git a/gcloud/beta/container/hub/memberships/register b/gcloud/beta/container/hub/memberships/register index 93ca3fa9f..2d8c4d7f8 100644 --- a/gcloud/beta/container/hub/memberships/register +++ b/gcloud/beta/container/hub/memberships/register @@ -49,72 +49,72 @@ EXAMPLES kubeconfig file, and install the Connect Agent: $ gcloud beta container hub memberships register my-cluster \ - --context=my-cluster-context \ - --kubeconfig=/home/user/custom_kubeconfig \ - --service-account-key-file=/tmp/keyfile.json + --context=my-cluster-context \ + --kubeconfig=/home/user/custom_kubeconfig \ + --service-account-key-file=/tmp/keyfile.json Register a non-GKE or GKE On-Prem cluster referenced from the default kubeconfig file, and install the Connect Agent: $ gcloud beta container hub memberships register my-cluster \ - --context=my-cluster-context \ - --service-account-key-file=/tmp/keyfile.json + --context=my-cluster-context \ + --service-account-key-file=/tmp/keyfile.json Register a non-GKE or GKE On-Prem cluster, and install a specific version of the Connect Agent: $ gcloud beta container hub memberships register my-cluster \ - --context=my-cluster-context \ - --version=gkeconnect_20190802_02_00 \ - --service-account-key-file=/tmp/keyfile.json + --context=my-cluster-context \ + --version=gkeconnect_20190802_02_00 \ + --service-account-key-file=/tmp/keyfile.json Register a non-GKE or GKE On-Prem cluster and output a manifest that can be used to install the Connect Agent: $ gcloud beta container hub memberships register my-cluster \ - --context=my-cluster-context \ - --manifest-output-file=/tmp/manifest.yaml \ - --service-account-key-file=/tmp/keyfile.json + --context=my-cluster-context \ + --manifest-output-file=/tmp/manifest.yaml \ + --service-account-key-file=/tmp/keyfile.json Register a GKE cluster referenced from a GKE URI, and install the Connect Agent: $ gcloud beta container hub memberships register my-cluster \ - --gke-uri=my-cluster-gke-uri \ - --service-account-key-file=/tmp/keyfile.json + --gke-uri=my-cluster-gke-uri \ + --service-account-key-file=/tmp/keyfile.json Register a GKE cluster referenced from a GKE Cluster location and name, and install the Connect Agent: $ gcloud beta container hub memberships register my-cluster \ - --gke-cluster=my-cluster-region-or-zone/my-cluster \ - --service-account-key-file=/tmp/keyfile.json + --gke-cluster=my-cluster-region-or-zone/my-cluster \ + --service-account-key-file=/tmp/keyfile.json Register a GKE cluster, and install a specific version of the Connect Agent: $ gcloud beta container hub memberships register my-cluster \ - --gke-uri=my-cluster-gke-uri \ - --version=gkeconnect_20190802_02_00 \ - --service-account-key-file=/tmp/keyfile.json + --gke-uri=my-cluster-gke-uri \ + --version=gkeconnect_20190802_02_00 \ + --service-account-key-file=/tmp/keyfile.json $ gcloud beta container hub memberships register my-cluster \ - --gke-cluster=my-cluster-region-or-zone/my-cluster \ - --version=gkeconnect_20190802_02_00 \ - --service-account-key-file=/tmp/keyfile.json + --gke-cluster=my-cluster-region-or-zone/my-cluster \ + --version=gkeconnect_20190802_02_00 \ + --service-account-key-file=/tmp/keyfile.json Register a GKE cluster and output a manifest that can be used to install the Connect Agent: $ gcloud beta container hub memberships register my-cluster \ - --gke-uri=my-cluster-gke-uri \ - --manifest-output-file=/tmp/manifest.yaml \ - --service-account-key-file=/tmp/keyfile.json + --gke-uri=my-cluster-gke-uri \ + --manifest-output-file=/tmp/manifest.yaml \ + --service-account-key-file=/tmp/keyfile.json $ gcloud beta container hub memberships register my-cluster \ - --gke-cluster=my-cluster-region-or-zone/my-cluster \ - --manifest-output-file=/tmp/manifest.yaml \ - --service-account-key-file=/tmp/keyfile.json + --gke-cluster=my-cluster-region-or-zone/my-cluster \ + --manifest-output-file=/tmp/manifest.yaml \ + --service-account-key-file=/tmp/keyfile.json POSITIONAL ARGUMENTS CLUSTER_NAME diff --git a/gcloud/beta/container/hub/memberships/unregister b/gcloud/beta/container/hub/memberships/unregister index dcebfcc7f..0df984bae 100644 --- a/gcloud/beta/container/hub/memberships/unregister +++ b/gcloud/beta/container/hub/memberships/unregister @@ -39,8 +39,8 @@ EXAMPLES Unregister a non-GKE cluster referenced from a specific kubeconfig file: $ gcloud beta container hub memberships unregister my-membership \ - --context=my-cluster-context \ - --kubeconfig=/home/user/custom_kubeconfig + --context=my-cluster-context \ + --kubeconfig=/home/user/custom_kubeconfig Unregister a non-GKE cluster referenced from the default kubeconfig file: @@ -50,12 +50,12 @@ EXAMPLES Unregister a GKE cluster referenced from a GKE URI: $ gcloud beta container hub memberships unregister my-membership \ - --gke-uri=my-cluster-gke-uri + --gke-uri=my-cluster-gke-uri Unregister a GKE cluster referenced from a GKE Cluster location and name: $ gcloud beta container hub memberships unregister my-membership \ - --gke-cluster=my-cluster-region-or-zone/my-cluster + --gke-cluster=my-cluster-region-or-zone/my-cluster POSITIONAL ARGUMENTS CLUSTER_NAME diff --git a/gcloud/beta/container/hub/mesh/describe b/gcloud/beta/container/hub/mesh/describe index 3a0d99f91..9a34c283c 100644 --- a/gcloud/beta/container/hub/mesh/describe +++ b/gcloud/beta/container/hub/mesh/describe @@ -6,7 +6,7 @@ SYNOPSIS gcloud beta container hub mesh describe [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Describe the status of Service Mesh Feature resource in Hub. + (BETA) Describe the status of Service Mesh Feature resource in a fleet. EXAMPLES To describe the Service Mesh Feature, run: diff --git a/gcloud/beta/container/hub/mesh/disable b/gcloud/beta/container/hub/mesh/disable index 0628f463a..4aec87fba 100644 --- a/gcloud/beta/container/hub/mesh/disable +++ b/gcloud/beta/container/hub/mesh/disable @@ -5,7 +5,7 @@ SYNOPSIS gcloud beta container hub mesh disable [--force] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Disable the Service Mesh Feature in Hub. + (BETA) Disable the Service Mesh Feature in a fleet. EXAMPLES To disable the Service Mesh Feature, run: diff --git a/gcloud/beta/container/hub/mesh/enable b/gcloud/beta/container/hub/mesh/enable index ae0758c07..ba5a5b29e 100644 --- a/gcloud/beta/container/hub/mesh/enable +++ b/gcloud/beta/container/hub/mesh/enable @@ -5,7 +5,7 @@ SYNOPSIS gcloud beta container hub mesh enable [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Enable the Service Mesh Feature in Hub. + (BETA) Enable the Service Mesh Feature in a fleet. EXAMPLES To enable the Service Mesh Feature, run: diff --git a/gcloud/beta/container/hub/multi-cluster-services/describe b/gcloud/beta/container/hub/multi-cluster-services/describe index 82bf999ee..470258b2c 100644 --- a/gcloud/beta/container/hub/multi-cluster-services/describe +++ b/gcloud/beta/container/hub/multi-cluster-services/describe @@ -8,7 +8,7 @@ SYNOPSIS DESCRIPTION (BETA) This command gets the detailed status of the Multi-cluster Services - Feature in Hub. + Feature in a fleet. EXAMPLES To describe the Multi-cluster Services Feature, run: diff --git a/gcloud/beta/container/hub/multi-cluster-services/disable b/gcloud/beta/container/hub/multi-cluster-services/disable index 6a36da4e9..dde0425e1 100644 --- a/gcloud/beta/container/hub/multi-cluster-services/disable +++ b/gcloud/beta/container/hub/multi-cluster-services/disable @@ -7,7 +7,7 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) This command disables the Multi-cluster Services Feature in Hub. + (BETA) This command disables the Multi-cluster Services Feature in a fleet. EXAMPLES To disable the Multi-cluster Services Feature, run: diff --git a/gcloud/beta/container/hub/multi-cluster-services/enable b/gcloud/beta/container/hub/multi-cluster-services/enable index b5baaffd2..db0f195d5 100644 --- a/gcloud/beta/container/hub/multi-cluster-services/enable +++ b/gcloud/beta/container/hub/multi-cluster-services/enable @@ -7,7 +7,7 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) This command enables the Multi-cluster Services Feature in Hub. + (BETA) This command enables the Multi-cluster Services Feature in a fleet. EXAMPLES To enable the Multi-cluster Services Feature, run: diff --git a/gcloud/beta/container/images/add-tag b/gcloud/beta/container/images/add-tag index 3116d4926..007186482 100644 --- a/gcloud/beta/container/images/add-tag +++ b/gcloud/beta/container/images/add-tag @@ -15,25 +15,23 @@ EXAMPLES Add a tag to another tag: $ gcloud beta container images add-tag \ - gcr.io/myproject/myimage:mytag1 - gcr.io/myproject/myimage:mytag2 + gcr.io/myproject/myimage:mytag1 gcr.io/myproject/myimage:mytag2 Add a tag to a digest $ gcloud beta container images add-tag \ - gcr.io/myproject/myimage@sha256:digest - gcr.io/myproject/myimage:mytag2 + gcr.io/myproject/myimage@sha256:digest \ + gcr.io/myproject/myimage:mytag2 Add a tag to latest - $ gcloud beta container images add-tag gcr.io/myproject/myimage - gcr.io/myproject/myimage:mytag2 + $ gcloud beta container images add-tag gcr.io/myproject/myimage \ + gcr.io/myproject/myimage:mytag2 Promote a tag to latest $ gcloud beta container images add-tag \ - gcr.io/myproject/myimage:mytag1 - gcr.io/myproject/myimage:latest + gcr.io/myproject/myimage:mytag1 gcr.io/myproject/myimage:latest POSITIONAL ARGUMENTS SRC_IMAGE diff --git a/gcloud/beta/container/images/delete b/gcloud/beta/container/images/delete index 7c150cf45..9fc9d1184 100644 --- a/gcloud/beta/container/images/delete +++ b/gcloud/beta/container/images/delete @@ -30,8 +30,8 @@ EXAMPLES digests that lack tags: $ gcloud container images list-tags \ - [HOSTNAME]/[PROJECT-ID]/[IMAGE] \ - --filter='-tags:*' --format="get(digest)" --limit=$BIG_NUMBER + [HOSTNAME]/[PROJECT-ID]/[IMAGE] --filter='-tags:*' \ + --format="get(digest)" --limit=$BIG_NUMBER Then, delete these tagless images without prompting by running: diff --git a/gcloud/beta/container/images/describe b/gcloud/beta/container/images/describe index 84bb299d9..15f5db15f 100644 --- a/gcloud/beta/container/images/describe +++ b/gcloud/beta/container/images/describe @@ -16,18 +16,22 @@ EXAMPLES $ gcloud beta container images describe \ gcr.io/myproject/myimage@digest - OR + + Or: + $ gcloud beta container images describe gcr.io/myproject/myimage:tag Find the digest for a tag: $ gcloud beta container images describe \ gcr.io/myproject/myimage:tag \ - --format="value(image_summary.digest)" - OR + --format="value(image_summary.digest)" + + Or: + $ gcloud beta container images describe \ gcr.io/myproject/myimage:tag \ - --format="value(image_summary.fully_qualified_digest)" + --format="value(image_summary.fully_qualified_digest)" See package vulnerabilities found by the Container Analysis API for the specified image: diff --git a/gcloud/beta/container/node-pools/create b/gcloud/beta/container/node-pools/create index 916d3ace9..7cd4fc551 100644 --- a/gcloud/beta/container/node-pools/create +++ b/gcloud/beta/container/node-pools/create @@ -8,8 +8,8 @@ SYNOPSIS [--boot-disk-kms-key=BOOT_DISK_KMS_KEY] [--cluster=CLUSTER] [--disk-size=DISK_SIZE] [--disk-type=DISK_TYPE] [--enable-autoprovisioning] [--enable-autorepair] - [--no-enable-autoupgrade] [--enable-gvnic] [--enable-image-streaming] - [--image-type=IMAGE_TYPE] + [--no-enable-autoupgrade] [--enable-confidential-nodes] + [--enable-gvnic] [--enable-image-streaming] [--image-type=IMAGE_TYPE] [--machine-type=MACHINE_TYPE, -m MACHINE_TYPE] [--max-pods-per-node=MAX_PODS_PER_NODE] [--max-surge-upgrade=MAX_SURGE_UPGRADE; default=1] @@ -124,6 +124,11 @@ FLAGS Enabled by default, use --no-enable-autoupgrade to disable. + --enable-confidential-nodes + Enable confidential nodes for the node pool. Enabling Confidential + Nodes will create nodes using Confidential VM + https://cloud.google.com/compute/confidential-vm/docs/about-cvm. + --enable-gvnic Enable the use of GVNIC for this cluster. Requires re-creation of nodes using either a node-pool upgrade or node-pool creation. @@ -297,6 +302,7 @@ FLAGS Multiple locations can be specified, separated by commas. For example: $ gcloud beta container node-pools create node-pool-1 \ + --cluster=sample-cluster \ --node-locations=us-central1-a,us-central1-b --node-taints=[NODE_TAINT,...] diff --git a/gcloud/beta/container/node-pools/update b/gcloud/beta/container/node-pools/update index 4e1afb472..a7dcc2dc6 100644 --- a/gcloud/beta/container/node-pools/update +++ b/gcloud/beta/container/node-pools/update @@ -4,9 +4,9 @@ NAME SYNOPSIS gcloud beta container node-pools update NAME - (--enable-gvnic | --enable-image-streaming - | --node-labels=[NODE_LABEL,...] | --node-locations=ZONE,[ZONE,...] - | --node-taints=[NODE_TAINT,...] + (--enable-confidential-nodes | --enable-gvnic + | --enable-image-streaming | --node-labels=[NODE_LABEL,...] + | --node-locations=ZONE,[ZONE,...] | --node-taints=[NODE_TAINT,...] | --system-config-from-file=SYSTEM_CONFIG_FROM_FILE | --tags=[TAG,...] | --workload-metadata=WORKLOAD_METADATA | --enable-autoprovisioning @@ -35,6 +35,10 @@ POSITIONAL ARGUMENTS REQUIRED FLAGS Exactly one of these must be specified: + --enable-confidential-nodes + Recreate all the nodes in the node pool to be confidential VM + https://cloud.google.com/compute/confidential-vm/docs/about-cvm. + --enable-gvnic Enable the use of GVNIC for this cluster. Requires re-creation of nodes using either a node-pool upgrade or node-pool creation. @@ -72,6 +76,7 @@ REQUIRED FLAGS example: $ gcloud beta container node-pools update node-pool-1 \ + --cluster=sample-cluster \ --node-locations=us-central1-a,us-central1-b --node-taints=[NODE_TAINT,...] diff --git a/gcloud/beta/container/subnets/list-usable b/gcloud/beta/container/subnets/list-usable index bedcec4ef..099066619 100644 --- a/gcloud/beta/container/subnets/list-usable +++ b/gcloud/beta/container/subnets/list-usable @@ -21,15 +21,14 @@ DESCRIPTION EXAMPLES List all subnetworks usable for cluster creation in project my-project. - $ gcloud beta container subnets list-usable \ - --project=my-project + $ gcloud beta container subnets list-usable --project=my-project List all subnetworks existing in project my-shared-host-project usable for cluster creation in project my-service-project. $ gcloud beta container subnets list-usable \ - --project=my-service-project \ - --network-project=my-shared-host-project + --project=my-service-project \ + --network-project=my-shared-host-project FLAGS --network-project=NETWORK_PROJECT diff --git a/gcloud/beta/data-catalog/entries/create b/gcloud/beta/data-catalog/entries/create index 4e3c6fcff..e37af1436 100644 --- a/gcloud/beta/data-catalog/entries/create +++ b/gcloud/beta/data-catalog/entries/create @@ -25,7 +25,8 @@ EXAMPLES $ gcloud beta data-catalog entries create entry1 \ --location=us-central1 --entry-group=group1 \ - --gcs-file-patterns="gs://bucket1/*" --display-name="sales data" \ + --gcs-file-patterns="gs://bucket1/*" \ + --display-name="sales data" \ --schema="qtr=STRING,sales=FLOAT,year=STRING" To create an entry for a Google Cloud Storage fileset with a schema from a @@ -33,8 +34,8 @@ EXAMPLES $ gcloud beta data-catalog entries create entry1 \ --location=us-central1 --entry-group=group1 \ - --gcs-file-patterns="gs://bucket1/*" --display-name="sales data" \ - --schema-from-file=/tmp/schema.json + --gcs-file-patterns="gs://bucket1/*" \ + --display-name="sales data" --schema-from-file=/tmp/schema.json POSITIONAL ARGUMENTS Entry resource - Entry to create. The arguments in this group can be used diff --git a/gcloud/beta/data-catalog/entries/update b/gcloud/beta/data-catalog/entries/update index 3a97ca6be..2cd1a5ab0 100644 --- a/gcloud/beta/data-catalog/entries/update +++ b/gcloud/beta/data-catalog/entries/update @@ -19,15 +19,13 @@ DESCRIPTION EXAMPLES To update the schema of a Cloud Pub/Sub entry inline, run: - $ gcloud beta data-catalog entries update entry1 \ - --location=global --entry-group=@pubsub \ - --schema="column1=type1,column2=type2" + $ gcloud beta data-catalog entries update entry1 --location=global \ + --entry-group=@pubsub --schema="column1=type1,column2=type2" To update the schema of a Cloud Pub/Sub entry from a file, run: - $ gcloud beta data-catalog entries update entry1 \ - --location=global --entry-group=@pubsub \ - --schema-from-file="/tmp/schema.json" + $ gcloud beta data-catalog entries update entry1 --location=global \ + --entry-group=@pubsub --schema-from-file="/tmp/schema.json" To lookup the entry of a Cloud Pub/Sub topic by its SQL name and update its schema in one command, run: diff --git a/gcloud/beta/data-catalog/entry-groups/create b/gcloud/beta/data-catalog/entry-groups/create index 2bd77810c..707c6bac6 100644 --- a/gcloud/beta/data-catalog/entry-groups/create +++ b/gcloud/beta/data-catalog/entry-groups/create @@ -14,8 +14,9 @@ EXAMPLES To create an entry group for some data, run: $ gcloud beta data-catalog entry-groups create group1 \ - --location=us-central1 --display-name="analytics data - jan 2011" \ - --description="Entries related to January 2011 analytics data." + --location=us-central1 \ + --display-name="analytics data - jan 2011" \ + --description="Entries related to January 2011 analytics data." POSITIONAL ARGUMENTS Entry group resource - Entry group to create. The arguments in this group diff --git a/gcloud/beta/data-catalog/tag-templates/create b/gcloud/beta/data-catalog/tag-templates/create index ea6cfed94..c9338db1e 100644 --- a/gcloud/beta/data-catalog/tag-templates/create +++ b/gcloud/beta/data-catalog/tag-templates/create @@ -29,7 +29,8 @@ EXAMPLES $ gcloud beta data-catalog tag-templates create TEMPLATE \ --field=id=ID1,display-name=DISPLAY1,type=string \ - --field=id=ID2,display-name=DISPLAY2,type='enum(A|B)',required=TRUE + --field=id=ID2,display-name=DISPLAY2,type='enum(A|B)',\ + required=TRUE POSITIONAL ARGUMENTS Tag template resource - Tag template to create. The arguments in this diff --git a/gcloud/beta/data-fusion/add-iam-policy-binding b/gcloud/beta/data-fusion/add-iam-policy-binding index c25434357..e616816de 100644 --- a/gcloud/beta/data-fusion/add-iam-policy-binding +++ b/gcloud/beta/data-fusion/add-iam-policy-binding @@ -14,14 +14,14 @@ EXAMPLES $ gcloud beta data-fusion add-iam-policy-binding \ add-iam-policy-binding my-instance --location=my-location \ - --member=user:someone@example.com --role=roles/datafusion.admin + --member=user:someone@example.com --role=roles/datafusion.admin To run the same command for a specific namespace on the instance, run: $ gcloud beta data-fusion add-iam-policy-binding \ add-iam-policy-binding my-instance --location=my-location \ - --member=user:someone@example.com --role=roles/datafusion.admin \ - --namespace=my-namespace + --member=user:someone@example.com \ + --role=roles/datafusion.admin --namespace=my-namespace POSITIONAL ARGUMENTS Instance resource - Instance to add IAM binding. The arguments in this diff --git a/gcloud/beta/data-fusion/get-iam-policy b/gcloud/beta/data-fusion/get-iam-policy index 640c2e01e..3dfceb2ff 100644 --- a/gcloud/beta/data-fusion/get-iam-policy +++ b/gcloud/beta/data-fusion/get-iam-policy @@ -18,7 +18,7 @@ EXAMPLES $ gcloud beta data-fusion get-iam-policy my-instance \ --project=my-project --location=my-location \ - --namespace=my-namespace + --namespace=my-namespace POSITIONAL ARGUMENTS Instance resource - Instance to describe. The arguments in this group can diff --git a/gcloud/beta/data-fusion/remove-iam-policy-binding b/gcloud/beta/data-fusion/remove-iam-policy-binding index 5a3254fe4..c60813b19 100644 --- a/gcloud/beta/data-fusion/remove-iam-policy-binding +++ b/gcloud/beta/data-fusion/remove-iam-policy-binding @@ -14,14 +14,14 @@ EXAMPLES $ gcloud beta data-fusion remove-iam-policy-binding \ remove-iam-policy-binding my-instance --location=my-location \ - --member=user:someone@example.com --role=roles/datafusion.admin + --member=user:someone@example.com --role=roles/datafusion.admin To run the same command for a specific namespace on the instance, run: $ gcloud beta data-fusion remove-iam-policy-binding \ remove-iam-policy-binding my-instance --location=my-location \ - --member=user:someone@example.com --role=roles/datafusion.admin \ - --namespace=my-namespace + --member=user:someone@example.com \ + --role=roles/datafusion.admin --namespace=my-namespace POSITIONAL ARGUMENTS Instance resource - Instance to remove IAM binding. The arguments in this diff --git a/gcloud/beta/data-fusion/set-iam-policy b/gcloud/beta/data-fusion/set-iam-policy index f694a5702..a9c747682 100644 --- a/gcloud/beta/data-fusion/set-iam-policy +++ b/gcloud/beta/data-fusion/set-iam-policy @@ -11,12 +11,11 @@ EXAMPLES location in 'my-location', and zone in 'my-zone' run: $ gcloud beta data-fusion set-iam-policy my-instance \ - policy-file.yaml --project=my-project \ - --location=my-location + policy-file.yaml --project=my-project --location=my-location To do the same in a particular namespace, run: $ gcloud beta data-fusion set-iam-policy my-instance \ - policy-file.yaml --project=my-project \ - --location=my-location [--namespace=NAMESPACE] + policy-file.yaml --project=my-project --location=my-location \ + [--namespace=NAMESPACE] POSITIONAL ARGUMENTS Instance resource - Instance to set. The arguments in this group can be diff --git a/gcloud/beta/dataflow/flex-template/build b/gcloud/beta/dataflow/flex-template/build index b067108cb..c6e77c781 100644 --- a/gcloud/beta/dataflow/flex-template/build +++ b/gcloud/beta/dataflow/flex-template/build @@ -29,16 +29,15 @@ EXAMPLES To build and store a the flex template json file, run: $ gcloud beta dataflow flex-template build \ - gs://template-file-gcs-path --image=gcr://image-path \ - --metadata-file=/local/path/to/metadata.json \ - --sdk-language=JAVA + gs://template-file-gcs-path --image=gcr://image-path \ + --metadata-file=/local/path/to/metadata.json --sdk-language=JAVA $ gcloud beta dataflow flex-template build \ - gs://template-file-gcs-path \ - --image-gcr-path=gcr://path-tos-tore-image \ - --jar=path/to/pipeline.jar --jar=path/to/dependency.jar \ - --env=FLEX_TEMPLATE_JAVA_MAIN_CLASS=classpath \ - --flex-template-base-image=JAVA11 \ + gs://template-file-gcs-path \ + --image-gcr-path=gcr://path-tos-tore-image \ + --jar=path/to/pipeline.jar --jar=path/to/dependency.jar \ + --env=FLEX_TEMPLATE_JAVA_MAIN_CLASS=classpath \ + --flex-template-base-image=JAVA11 \ --metadata-file=/local/path/to/metadata.json --sdk-language=JAVA POSITIONAL ARGUMENTS diff --git a/gcloud/beta/datapipelines/pipeline/create b/gcloud/beta/datapipelines/pipeline/create index 39e97e60c..1df5d6d59 100644 --- a/gcloud/beta/datapipelines/pipeline/create +++ b/gcloud/beta/datapipelines/pipeline/create @@ -29,11 +29,11 @@ EXAMPLES us-central1, run: $ gcloud beta datapipelines pipeline create PIPELINE_NAME \ - --project=example --region=us-central1 - --pipeline-type=BATCH - --template-file-gcs-location='gs://path_to_template_file' - --parameters=inputFile="gs://path_to_input_file",output="gs://path_to_output_file" - --schedule="0 * * * *" --temp-location="gs://path_to_temp_location" + --project=example --region=us-central1 --pipeline-type=BATCH \ + --template-file-gcs-location='gs://path_to_template_file' \ + --parameters=inputFile="gs://path_to_input_file",\ + output="gs://path_to_output_file" --schedule="0 * * * *" \ + --temp-location="gs://path_to_temp_location" POSITIONAL ARGUMENTS Pipeline resource - Name for the Data Pipelines Pipeline. The arguments in diff --git a/gcloud/beta/datapipelines/pipeline/update b/gcloud/beta/datapipelines/pipeline/update index cd0ef0f46..b5eb17343 100644 --- a/gcloud/beta/datapipelines/pipeline/update +++ b/gcloud/beta/datapipelines/pipeline/update @@ -29,8 +29,7 @@ EXAMPLES us-central1, run: $ gcloud beta datapipelines pipeline update abc PIPELINE_NAME \ - --project=example --region=us-central1 - --display-name="new_name" + --project=example --region=us-central1 --display-name="new_name" POSITIONAL ARGUMENTS Pipeline resource - Name for the Data Pipelines Pipeline. The arguments in diff --git a/gcloud/beta/dataproc/autoscaling-policies/set-iam-policy b/gcloud/beta/dataproc/autoscaling-policies/set-iam-policy index 4bfc2ca05..756e1bebf 100644 --- a/gcloud/beta/dataproc/autoscaling-policies/set-iam-policy +++ b/gcloud/beta/dataproc/autoscaling-policies/set-iam-policy @@ -17,8 +17,8 @@ EXAMPLES 'example-autoscaling-policy' $ gcloud beta dataproc autoscaling-policies set-iam-policy \ - autoscaling-policies set-iam-policy \ - example-autoscaling-policy policy.json + autoscaling-policies set-iam-policy example-autoscaling-policy \ + policy.json See https://cloud.google.com/iam/docs/managing-policies for details of the policy file format and contents. diff --git a/gcloud/beta/dataproc/batches/submit/pyspark b/gcloud/beta/dataproc/batches/submit/pyspark index 124a547f6..1d9276f0c 100644 --- a/gcloud/beta/dataproc/batches/submit/pyspark +++ b/gcloud/beta/dataproc/batches/submit/pyspark @@ -21,8 +21,8 @@ EXAMPLES To submit a PySpark batch job called "my-batch" that runs "my-pyspark.py", run: - $ gcloud beta dataproc batches submit pyspark pyspark \ - my-pyspark.py --batch=my-batch --deps-bucket=gs://my-bucket \ + $ gcloud beta dataproc batches submit pyspark my-pyspark.py \ + --batch=my-batch --deps-bucket=gs://my-bucket \ --region=us-central1 --py-files='path/to/my/python/script.py' POSITIONAL ARGUMENTS diff --git a/gcloud/beta/dataproc/jobs/submit/hadoop b/gcloud/beta/dataproc/jobs/submit/hadoop index ffd09971e..974eb7bfe 100644 --- a/gcloud/beta/dataproc/jobs/submit/hadoop +++ b/gcloud/beta/dataproc/jobs/submit/hadoop @@ -25,8 +25,8 @@ EXAMPLES To submit a Hadoop job that runs a specific class of a jar, run: $ gcloud beta dataproc jobs submit hadoop --cluster=my_cluster \ - --class=org.my.main.Class \ - --jars=my_jar1.jar,my_jar2.jar -- arg1 arg2 + --class=org.my.main.Class --jars=my_jar1.jar,my_jar2.jar \ + -- arg1 arg2 To submit a Hadoop job that runs a jar that is already on the cluster, run: diff --git a/gcloud/beta/dataproc/jobs/submit/hive b/gcloud/beta/dataproc/jobs/submit/hive index 16ade7521..2ab5a099c 100644 --- a/gcloud/beta/dataproc/jobs/submit/hive +++ b/gcloud/beta/dataproc/jobs/submit/hive @@ -23,9 +23,9 @@ EXAMPLES To submit a Hive job with inline queries, run: - $ gcloud beta dataproc jobs submit hive --cluster=my_cluster - -e="CREATE EXTERNAL TABLE foo(bar int) LOCATION 'gs://my_bucket/'" - -e="SELECT * FROM foo WHERE bar > 2" + $ gcloud beta dataproc jobs submit hive --cluster=my_cluster \ + -e="CREATE EXTERNAL TABLE foo(bar int) LOCATION \ + 'gs://my_bucket/'" -e="SELECT * FROM foo WHERE bar > 2" REQUIRED FLAGS Exactly one of these must be specified: diff --git a/gcloud/beta/dataproc/jobs/submit/pig b/gcloud/beta/dataproc/jobs/submit/pig index ca924fb5d..54cf8eeab 100644 --- a/gcloud/beta/dataproc/jobs/submit/pig +++ b/gcloud/beta/dataproc/jobs/submit/pig @@ -24,11 +24,11 @@ EXAMPLES To submit a Pig job with inline queries, run: - $ gcloud beta dataproc jobs submit pig --cluster=my_cluster - -e="LNS = LOAD 'gs://my_bucket/my_file.txt' AS (line)" - -e="WORDS = FOREACH LNS GENERATE FLATTEN(TOKENIZE(line)) AS word" - -e="GROUPS = GROUP WORDS BY word" - -e="WORD_COUNTS = FOREACH GROUPS GENERATE group, COUNT(WORDS)" + $ gcloud beta dataproc jobs submit pig --cluster=my_cluster \ + -e="LNS = LOAD 'gs://my_bucket/my_file.txt' AS (line)" \ + -e="WORDS = FOREACH LNS GENERATE FLATTEN(TOKENIZE(line)) AS \ + word" -e="GROUPS = GROUP WORDS BY word" \ + -e="WORD_COUNTS = FOREACH GROUPS GENERATE group, COUNT(WORDS)" \ -e="DUMP WORD_COUNTS" REQUIRED FLAGS diff --git a/gcloud/beta/dataproc/jobs/submit/spark b/gcloud/beta/dataproc/jobs/submit/spark index bf0348d5f..dfd6e77cf 100644 --- a/gcloud/beta/dataproc/jobs/submit/spark +++ b/gcloud/beta/dataproc/jobs/submit/spark @@ -31,8 +31,7 @@ EXAMPLES To submit a Spark job that runs a jar that is already on the cluster, run: $ gcloud beta dataproc jobs submit spark --cluster=my_cluster \ - --region=us-central1 \ - --class=org.apache.spark.examples.SparkPi \ + --region=us-central1 --class=org.apache.spark.examples.SparkPi \ --jars=file:///usr/lib/spark/examples/jars/spark-examples.jar \ -- 1000 diff --git a/gcloud/beta/dataproc/jobs/submit/spark-r b/gcloud/beta/dataproc/jobs/submit/spark-r index 8eb4771f3..f65150640 100644 --- a/gcloud/beta/dataproc/jobs/submit/spark-r +++ b/gcloud/beta/dataproc/jobs/submit/spark-r @@ -24,8 +24,7 @@ EXAMPLES To submit a Spark job that runs a script already on the cluster, run: $ gcloud beta dataproc jobs submit spark-r --cluster=my_cluster \ - file:///.../my_script.R \ - -- gs://my_bucket/data.csv + file:///.../my_script.R -- gs://my_bucket/data.csv POSITIONAL ARGUMENTS R_FILE diff --git a/gcloud/beta/dataproc/jobs/submit/spark-sql b/gcloud/beta/dataproc/jobs/submit/spark-sql index 13daecf59..f804c73c6 100644 --- a/gcloud/beta/dataproc/jobs/submit/spark-sql +++ b/gcloud/beta/dataproc/jobs/submit/spark-sql @@ -24,9 +24,9 @@ EXAMPLES To submit a Spark SQL job with inline queries, run: - $ gcloud beta dataproc jobs submit spark-sql --cluster=my_cluster - -e="CREATE EXTERNAL TABLE foo(bar int) LOCATION 'gs://my_bucket/'" - -e="SELECT * FROM foo WHERE bar > 2" + $ gcloud beta dataproc jobs submit spark-sql --cluster=my_cluster \ + -e="CREATE EXTERNAL TABLE foo(bar int) LOCATION \ + 'gs://my_bucket/'" -e="SELECT * FROM foo WHERE bar > 2" REQUIRED FLAGS Exactly one of these must be specified: diff --git a/gcloud/beta/dataproc/jobs/wait b/gcloud/beta/dataproc/jobs/wait index 6be7fc2a5..6d1670219 100644 --- a/gcloud/beta/dataproc/jobs/wait +++ b/gcloud/beta/dataproc/jobs/wait @@ -18,7 +18,7 @@ EXAMPLES run: $ gcloud dataproc jobs list --format "table(reference.jobId)" \ - --limit 1 --log-http + --limit 1 --log-http To view the output of a job as it runs, run: diff --git a/gcloud/beta/dataproc/workflow-templates/add-job/help b/gcloud/beta/dataproc/workflow-templates/add-job/help index e72d042e2..598e44606 100644 --- a/gcloud/beta/dataproc/workflow-templates/add-job/help +++ b/gcloud/beta/dataproc/workflow-templates/add-job/help @@ -10,20 +10,17 @@ EXAMPLES To add a Hadoop MapReduce job, run: $ gcloud beta dataproc workflow-templates add-job hadoop \ - --workflow-template my_template --jar my_jar.jar \ - -- arg1 arg2 + --workflow-template my_template --jar my_jar.jar -- arg1 arg2 To add a Spark Scala or Java job, run: $ gcloud beta dataproc workflow-templates add-job spark \ - --workflow-template my_template --jar my_jar.jar \ - -- arg1 arg2 + --workflow-template my_template --jar my_jar.jar -- arg1 arg2 To add a PySpark job, run: $ gcloud beta dataproc workflow-templates add-job pyspark \ - --workflow-template my_template my_script.py \ - -- arg1 arg2 + --workflow-template my_template my_script.py -- arg1 arg2 To add a Spark SQL job, run: diff --git a/gcloud/beta/dataproc/workflow-templates/help b/gcloud/beta/dataproc/workflow-templates/help index f38c3e754..b768406cb 100644 --- a/gcloud/beta/dataproc/workflow-templates/help +++ b/gcloud/beta/dataproc/workflow-templates/help @@ -48,8 +48,7 @@ EXAMPLES To update cluster selector in a workflow template, run: $ gcloud beta dataproc workflow-templates set-cluster-selector \ - my_template \ - --cluster-labels environment=prod + my_template --cluster-labels environment=prod GCLOUD WIDE FLAGS These flags are available to all commands: --help. diff --git a/gcloud/beta/debug/logpoints/help b/gcloud/beta/debug/logpoints/help index 02b25b66a..b4b19b13c 100644 --- a/gcloud/beta/debug/logpoints/help +++ b/gcloud/beta/debug/logpoints/help @@ -17,7 +17,7 @@ EXAMPLES "product" variable whenever any request executes line 123 of the file product.py: - $ gcloud beta debug logpoints create product.py:123 \ + $ gcloud beta debug logpoints create product.py:123 \ "No description for {product.name}" The log output will appear wherever explicit logging output from your @@ -27,8 +27,8 @@ EXAMPLES If you want to log output only when certain runtime conditions are met, you can add a "--condition" option: - $ gcloud beta debug logpoints create product.py:123 \ - "Suspicious price: {product.name} costs {price}" \ + $ gcloud beta debug logpoints create product.py:123 \ + "Suspicious price: {product.name} costs {price}" \ --condition "price < .50" Logpoints remain active for 24 hours after creation. If you want to disable @@ -41,9 +41,8 @@ EXAMPLES first determine the logpoint ID using the logpoints list command, then delete that specific ID: - $ gcloud beta debug logpoints list - ID LOCATION ... - 567890abcdef1-1234-56789 product.py:123 ... + $ gcloud beta debug logpoints list ID LOCATION ... \ + 567890abcdef1-1234-56789 product.py:123 ... $ gcloud beta debug logpoints delete 567890abcdef1-1234-56789 For App Engine services, logpoint resources include the "logQuery" @@ -51,9 +50,8 @@ EXAMPLES command. You can save this property's value and use it to read logs from the command line: - $ log_query=$(gcloud beta debug logpoints create product.py:123 \ - "No description for {product.name}" \ - --format="value(logQuery)") + $ log_query=$(gcloud beta debug logpoints create product.py:123 \ + "No description for {product.name}" --format="value(logQuery)") $ gcloud logging read "$log_query" FLAGS diff --git a/gcloud/beta/deploy/delivery-pipelines/add-iam-policy-binding b/gcloud/beta/deploy/delivery-pipelines/add-iam-policy-binding index 5cb9466a6..1af234c62 100644 --- a/gcloud/beta/deploy/delivery-pipelines/add-iam-policy-binding +++ b/gcloud/beta/deploy/delivery-pipelines/add-iam-policy-binding @@ -21,10 +21,9 @@ EXAMPLES 'us-central1', run: $ gcloud beta deploy delivery-pipelines add-iam-policy-binding \ - my-pipeline \ - --region='us-central1' \ - --member='user:test-user@gmail.com' \ - --role='roles/clouddeploy.operator' + my-pipeline --region='us-central1' \ + --member='user:test-user@gmail.com' \ + --role='roles/clouddeploy.operator' POSITIONAL ARGUMENTS Delivery pipeline resource - The delivery pipeline for which to add the diff --git a/gcloud/beta/deploy/delivery-pipelines/remove-iam-policy-binding b/gcloud/beta/deploy/delivery-pipelines/remove-iam-policy-binding index cc4cb3a0b..500b1b598 100644 --- a/gcloud/beta/deploy/delivery-pipelines/remove-iam-policy-binding +++ b/gcloud/beta/deploy/delivery-pipelines/remove-iam-policy-binding @@ -21,10 +21,9 @@ EXAMPLES 'my-pipeline' with the region 'us-central1', run: $ gcloud beta deploy delivery-pipelines remove-iam-policy-binding \ - my-pipeline \ - --region='us-central1' \ - --member='user:test-user@gmail.com' \ - --role='roles/clouddeploy.operator' + my-pipeline --region='us-central1' \ + --member='user:test-user@gmail.com' \ + --role='roles/clouddeploy.operator' POSITIONAL ARGUMENTS Delivery pipeline resource - The delivery pipeline for which to remove the diff --git a/gcloud/beta/deploy/targets/add-iam-policy-binding b/gcloud/beta/deploy/targets/add-iam-policy-binding index bdfa0619d..132c893d4 100644 --- a/gcloud/beta/deploy/targets/add-iam-policy-binding +++ b/gcloud/beta/deploy/targets/add-iam-policy-binding @@ -21,9 +21,8 @@ EXAMPLES 'us-central1', run: $ gcloud beta deploy targets add-iam-policy-binding my-target \ - --region='us-central1' \ - --member='user:test-user@gmail.com' \ - --role='roles/clouddeploy.operator' + --region='us-central1' --member='user:test-user@gmail.com' \ + --role='roles/clouddeploy.operator' POSITIONAL ARGUMENTS Target resource - The target for which to add the IAM policy binding. The diff --git a/gcloud/beta/deploy/targets/remove-iam-policy-binding b/gcloud/beta/deploy/targets/remove-iam-policy-binding index a88d07791..e1e0449d1 100644 --- a/gcloud/beta/deploy/targets/remove-iam-policy-binding +++ b/gcloud/beta/deploy/targets/remove-iam-policy-binding @@ -21,9 +21,8 @@ EXAMPLES 'my-target' with the region 'us-central1', run: $ gcloud beta deploy targets remove-iam-policy-binding my-target \ - --region='us-central1' \ - --member='user:test-user@gmail.com' \ - --role='roles/clouddeploy.operator' + --region='us-central1' --member='user:test-user@gmail.com' \ + --role='roles/clouddeploy.operator' POSITIONAL ARGUMENTS Target resource - The target for which to remove the IAM policy binding. diff --git a/gcloud/beta/deployment-manager/deployments/create b/gcloud/beta/deployment-manager/deployments/create index 2d272763e..bd4fa82ed 100644 --- a/gcloud/beta/deployment-manager/deployments/create +++ b/gcloud/beta/deployment-manager/deployments/create @@ -22,14 +22,14 @@ EXAMPLES To create a new deployment from a top-level template file, run: - $ gcloud deployment-manager deployments create my-deployment \ - --template=template.{jinja|py} \ + $ gcloud deployment-manager deployments create my-deployment \ + --template=template.{jinja|py} \ --properties="string-key:'string-value',integer-key:12345" To create a new deployment directly from a composite type, run: - $ gcloud deployment-manager deployments create my-deployment \ - --composite-type=/composite: \ + $ gcloud deployment-manager deployments create my-deployment \ + --composite-type=/composite: \ --properties="string-key:'string-value',integer-key:12345" To preview a deployment without actually creating resources, run: diff --git a/gcloud/beta/dns/dns-keys/list b/gcloud/beta/dns/dns-keys/list index 39911a476..6edb167b8 100644 --- a/gcloud/beta/dns/dns-keys/list +++ b/gcloud/beta/dns/dns-keys/list @@ -16,8 +16,7 @@ EXAMPLES To see the DS records for every key-signing DnsKey in a managed zone, run: $ gcloud beta dns dns-keys list --zone=my_zone 3 \ - --format='value(ds_record())' \ - --filter='type=keySigning' + --format='value(ds_record())' --filter='type=keySigning' REQUIRED FLAGS --zone=ZONE, -z ZONE diff --git a/gcloud/beta/dns/managed-zones/create b/gcloud/beta/dns/managed-zones/create index 67aecc864..c1b7e1ee5 100644 --- a/gcloud/beta/dns/managed-zones/create +++ b/gcloud/beta/dns/managed-zones/create @@ -28,17 +28,14 @@ EXAMPLES To create a managed-zone with DNSSEC, run: $ gcloud beta dns managed-zones create my-zone-2 \ - --description "Signed Zone" - --dns-name myzone.example + --description "Signed Zone" --dns-name myzone.example \ --dnssec-state=on To create a zonal managed-zone scoped to a GKE Cluster in us-east1-a, run: $ gcloud beta dns managed-zones create my-zonal-zone \ - --description "Signed Zone" - --dns-name=cluster.local - --visibiilty=private - --gkeclusters=cluster1 + --description "Signed Zone" --dns-name=cluster.local \ + --visibiilty=private --gkeclusters=cluster1 \ --location=us-east1-a POSITIONAL ARGUMENTS diff --git a/gcloud/beta/dns/policies/create b/gcloud/beta/dns/policies/create index 724bb4d86..9bcd8db62 100644 --- a/gcloud/beta/dns/policies/create +++ b/gcloud/beta/dns/policies/create @@ -16,18 +16,16 @@ EXAMPLES To create a new policy with minimal arguments, run: $ gcloud beta dns policies create mypolicy \ - --description='My new policy test policy 5' \ - --networks='' + --description='My new policy test policy 5' --networks='' To create a new policy with all optional arguments, run: $ gcloud beta dns policies create mypolicy \ - --description='My new policy test policy 5' \ - --networks=network1,network2 \ - --alternative-name-servers=192.168.1.1,192.168.1.2 \ - --private-alternative-name-servers=100.64.0.1 \ - --enable-inbound-forwarding \ - --enable-logging + --description='My new policy test policy 5' \ + --networks=network1,network2 \ + --alternative-name-servers=192.168.1.1,192.168.1.2 \ + --private-alternative-name-servers=100.64.0.1 \ + --enable-inbound-forwarding --enable-logging POSITIONAL ARGUMENTS Policy resource - The policy to create. This represents a Cloud resource. diff --git a/gcloud/beta/dns/record-sets/create b/gcloud/beta/dns/record-sets/create index 6f0474e37..3a0d688cf 100644 --- a/gcloud/beta/dns/record-sets/create +++ b/gcloud/beta/dns/record-sets/create @@ -17,15 +17,14 @@ EXAMPLES [1.2.3.4, 9.8.7.6] and ttl 60 in my_zone run this: $ gcloud beta dns record-sets create foo.bar.com. \ - --rrdatas=1.2.3.4,9.8.7.6 --type=A --ttl=60 - --zone=my_zone + --rrdatas=1.2.3.4,9.8.7.6 --type=A --ttl=60 --zone=my_zone To create a record-set with dnsName foo.bar.com., record type A, rrdata [1.2.3.4, 9.8.7.6] and ttl 60 in my_zone in us-east1-a run this: $ gcloud beta dns record-sets create us-east1-a.bar.com. \ - --rrdatas=1.2.3.4,9.8.7.6 --type=A --ttl=60 - --zone=my_zone --location=us-east1-a + --rrdatas=1.2.3.4,9.8.7.6 --type=A --ttl=60 --zone=my_zone \ + --location=us-east1-a POSITIONAL ARGUMENTS DNS_NAME diff --git a/gcloud/beta/dns/record-sets/export b/gcloud/beta/dns/record-sets/export index b51fe2b24..56b267eb0 100644 --- a/gcloud/beta/dns/record-sets/export +++ b/gcloud/beta/dns/record-sets/export @@ -24,7 +24,7 @@ EXAMPLES Similarly, to import record-sets into a BIND zone formatted zone file, run: $ gcloud dns record-sets import pathto.zonefile --zone-file-format \ - --zone=examplezonename + --zone=examplezonename POSITIONAL ARGUMENTS RECORDS_FILE diff --git a/gcloud/beta/dns/record-sets/transaction/add b/gcloud/beta/dns/record-sets/transaction/add index 182997765..0dfd474df 100644 --- a/gcloud/beta/dns/record-sets/transaction/add +++ b/gcloud/beta/dns/record-sets/transaction/add @@ -19,16 +19,14 @@ EXAMPLES "my.domain.", and a managed zone "MANAGED_ZONE", run: $ gcloud beta dns record-sets transaction add "1.2.3.4" \ - --name=my.domain. --ttl=1234 \ - --type=A --zone=MANAGED_ZONE + --name=my.domain. --ttl=1234 --type=A --zone=MANAGED_ZONE To add a TXT record with multiple data values while specifying time to live as 14400 seconds, run: $ gcloud beta dns record-sets transaction add "Hello world" \ - "Bye world" \ - --name=my.domain. --ttl=14400 \ - --type=TXT --zone=MANAGED_ZONE + "Bye world" --name=my.domain. --ttl=14400 --type=TXT \ + --zone=MANAGED_ZONE POSITIONAL ARGUMENTS RRDATAS [RRDATAS ...] diff --git a/gcloud/beta/dns/record-sets/transaction/remove b/gcloud/beta/dns/record-sets/transaction/remove index 8e2a5b439..29f6efd8e 100644 --- a/gcloud/beta/dns/record-sets/transaction/remove +++ b/gcloud/beta/dns/record-sets/transaction/remove @@ -15,14 +15,14 @@ EXAMPLES To remove an A record, run: $ gcloud beta dns record-sets transaction remove \ - --zone=MANAGED_ZONE --name=my.domain. --ttl=1234 \ - --type=A "1.2.3.4" + --zone=MANAGED_ZONE --name=my.domain. --ttl=1234 --type=A \ + "1.2.3.4" To remove a TXT record with multiple data values, run: $ gcloud beta dns record-sets transaction remove \ - --zone=MANAGED_ZONE --name=my.domain. --ttl=2345 \ - --type=TXT "Hello world" "Bye world" + --zone=MANAGED_ZONE --name=my.domain. --ttl=2345 --type=TXT \ + "Hello world" "Bye world" POSITIONAL ARGUMENTS RRDATAS [RRDATAS ...] diff --git a/gcloud/beta/dns/record-sets/update b/gcloud/beta/dns/record-sets/update index 700edc5d6..4a99bcdef 100644 --- a/gcloud/beta/dns/record-sets/update +++ b/gcloud/beta/dns/record-sets/update @@ -17,16 +17,15 @@ EXAMPLES rrdata [1.2.3.4, 9.8.7.6] and ttl 60 in my_zone, run: $ gcloud beta dns record-sets update foo.bar.com. \ - --rrdatas=1.2.3.4,9.8.7.6 --type=A --ttl=60 - --zone=my_zone + --rrdatas=1.2.3.4,9.8.7.6 --type=A --ttl=60 --zone=my_zone To update a record-set with dnsName foo.bar.com., record type A to have rrdata [1.2.3.4, 9.8.7.6] and ttl 60 in my_zone that locates in us-east1-a, run: $ gcloud beta dns record-sets update foo.bar.com. \ - --rrdatas=1.2.3.4,9.8.7.6 --type=A --ttl=60 - --zone=my_zone --location=us-east1-a + --rrdatas=1.2.3.4,9.8.7.6 --type=A --ttl=60 --zone=my_zone \ + --location=us-east1-a POSITIONAL ARGUMENTS DNS_NAME diff --git a/gcloud/beta/dns/response-policies/create b/gcloud/beta/dns/response-policies/create index f4ac48add..16534b6b8 100644 --- a/gcloud/beta/dns/response-policies/create +++ b/gcloud/beta/dns/response-policies/create @@ -15,21 +15,19 @@ EXAMPLES To create a new response policy with minimal arguments, run: $ gcloud beta dns response-policies create myresponsepolicy \ - --description='My new response policy.' - --networks='' + --description='My new response policy.' --networks='' To create a new response policy with all optional arguments, run: $ gcloud beta dns response-policies create myresponsepolicy \ - --description='My new response policy.' - --networks=network1,network2 + --description='My new response policy.' \ + --networks=network1,network2 To create a new zonal response policy scoped to a GKE cluster in us-central1-a, run (alpha/beta): $ gcloud beta dns response-policies create beta myresponsepolicy \ --description='My new response - policy.' - --gkeclusters=cluster1 --location=us-central1-a + policy.' --gkeclusters=cluster1 --location=us-central1-a POSITIONAL ARGUMENTS Response policy resource - The response policy to create. This represents diff --git a/gcloud/beta/dns/response-policies/rules/create b/gcloud/beta/dns/response-policies/rules/create index 1db04a3c6..078080fd6 100644 --- a/gcloud/beta/dns/response-policies/rules/create +++ b/gcloud/beta/dns/response-policies/rules/create @@ -13,23 +13,24 @@ EXAMPLES To create a new response policy rule with local data rrsets, run: $ gcloud beta dns response-policies rules create \ - myresponsepolicyrule --response-policy="myresponsepolicy" - --dns-name="www.zone.com." - --local-data=name=www.zone.com.,type=CNAME,ttl=21600,rrdatas=zone.com. + myresponsepolicyrule --response-policy="myresponsepolicy" \ + --dns-name="www.zone.com." \ + --local-data=name=www.zone.com.,type=CNAME,ttl=21600,\ + rrdatas=zone.com. To create a new response policy rule with behavior, run: $ gcloud beta dns response-policies rules create \ - myresponsepolicyrule --response-policy="myresponsepolicy" - --dns-name="www.zone.com." --behavior=bypassResponsePolicy + myresponsepolicyrule --response-policy="myresponsepolicy" \ + --dns-name="www.zone.com." --behavior=bypassResponsePolicy To create a new response policy rule with behavior in a zonal response policy in us-east1-a, run: $ gcloud beta dns response-policies rules create \ - myresponsepolicyrule --response-policy="myresponsepolicy" - --dns-name="www.zone.com." --behavior=bypassResponsePolicy - --location=us-east1-a + myresponsepolicyrule --response-policy="myresponsepolicy" \ + --dns-name="www.zone.com." --behavior=bypassResponsePolicy \ + --location=us-east1-a POSITIONAL ARGUMENTS Response policy rule resource - The response policy rule to create. The diff --git a/gcloud/beta/dns/response-policies/rules/help b/gcloud/beta/dns/response-policies/rules/help index dd0329689..72e013c1c 100644 --- a/gcloud/beta/dns/response-policies/rules/help +++ b/gcloud/beta/dns/response-policies/rules/help @@ -9,27 +9,28 @@ EXAMPLES To create a new response policy rule with local data rrsets, run: $ gcloud beta dns response-policies rules myresponsepolicyrule \ - --response-policy="myresponsepolicy" - --dns-name="www.zone.com." - --local-data=name=www.zone.com.,type=CNAME,ttl=21600,rrdatas=zone.com. + --response-policy="myresponsepolicy" \ + --dns-name="www.zone.com." \ + --local-data=name=www.zone.com.,type=CNAME,ttl=21600,\ + rrdatas=zone.com. To create a new response policy rule with behavior, run: $ gcloud beta dns response-policies rules myresponsepolicyrule \ - --response-policy="myresponsepolicy" - --dns-name="www.zone.com." --behavior=bypassResponsePolicy + --response-policy="myresponsepolicy" \ + --dns-name="www.zone.com." --behavior=bypassResponsePolicy To update a new response policy rule with local data rrsets, run: $ gcloud beta dns response-policies rules myresponsepolicyrule \ - --response-policy="myresponsepolicy" - --local-data=name=www.zone.com.,type=A,ttl=21600,rrdatas=1.2.3.4 + --response-policy="myresponsepolicy" \ + --local-data=name=www.zone.com.,type=A,ttl=21600,rrdatas=1.2.3.4 To update a new response policy rule with behavior, run: $ gcloud beta dns response-policies rules myresponsepolicyrule \ - --response-policy="myresponsepolicy" - --behavior=bypassResponsePolicy + --response-policy="myresponsepolicy" \ + --behavior=bypassResponsePolicy GCLOUD WIDE FLAGS These flags are available to all commands: --help. diff --git a/gcloud/beta/dns/response-policies/rules/update b/gcloud/beta/dns/response-policies/rules/update index 95f730d71..2c75aecf6 100644 --- a/gcloud/beta/dns/response-policies/rules/update +++ b/gcloud/beta/dns/response-policies/rules/update @@ -16,20 +16,20 @@ EXAMPLES To update a new response policy rule with DNS name, run: $ gcloud beta dns response-policies rules update \ - myresponsepolicyrule --response-policy="myresponsepolicy" - --dns-name="www.newzone.com." # pylint: disable=line-too-long + myresponsepolicyrule --response-policy="myresponsepolicy" \ + --dns-name="www.newzone.com." # pylint: disable=line-too-long To update a new response policy rule with local data rrsets, run: $ gcloud beta dns response-policies rules update \ - myresponsepolicyrule --response-policy="myresponsepolicy" - --local-data=name=www.zone.com.,type=A,ttl=21600,rrdatas=1.2.3.4 + myresponsepolicyrule --response-policy="myresponsepolicy" \ + --local-data=name=www.zone.com.,type=A,ttl=21600,rrdatas=1.2.3.4 To update a new response policy rule with behavior, run: $ gcloud beta dns response-policies rules update \ - myresponsepolicyrule --response-policy="myresponsepolicy" - --behavior=bypassResponsePolicy + myresponsepolicyrule --response-policy="myresponsepolicy" \ + --behavior=bypassResponsePolicy POSITIONAL ARGUMENTS Response policy rule resource - The response policy rule to update. The diff --git a/gcloud/beta/dns/response-policies/update b/gcloud/beta/dns/response-policies/update index 903befce9..422ba5645 100644 --- a/gcloud/beta/dns/response-policies/update +++ b/gcloud/beta/dns/response-policies/update @@ -15,21 +15,20 @@ EXAMPLES To update a response policy with minimal arguments, run: $ gcloud beta dns response-policies update myresponsepolicy \ - --description='My updated response policy.' - --networks='' + --description='My updated response policy.' --networks='' To update a response policy with all optional arguments, run: $ gcloud beta dns response-policies update myresponsepolicy \ - --description='My updated response policy.' - --networks=network1,network2 + --description='My updated response policy.' \ + --networks=network1,network2 To update a new zonal response policy scoped to a GKE cluster in us-central1-a, run: $ gcloud beta dns response-policies update myresponsepolicy \ - --description='My new response policy.' - --gkeclusters=cluster1 --location=us-central1-a + --description='My new response policy.' --gkeclusters=cluster1 \ + --location=us-central1-a POSITIONAL ARGUMENTS Response policy resource - The response policy to update. This represents diff --git a/gcloud/beta/endpoints/services/add-iam-policy-binding b/gcloud/beta/endpoints/services/add-iam-policy-binding index eecffcaef..eea165387 100644 --- a/gcloud/beta/endpoints/services/add-iam-policy-binding +++ b/gcloud/beta/endpoints/services/add-iam-policy-binding @@ -27,8 +27,8 @@ EXAMPLES 'my-service', run: $ gcloud beta endpoints services add-iam-policy-binding my-service \ - --member='serviceAccount:my-iam-account@my-project.iam.gserviceaccount.com' \ - --role='roles/servicemanagement.serviceConsumer' + --member='serviceAccount:my-iam-account@my-project.iam.gservicea\ + ccount.com' --role='roles/servicemanagement.serviceConsumer' See https://cloud.google.com/iam/docs/managing-policies for details of policy role and member types. diff --git a/gcloud/beta/essential-contacts/compute b/gcloud/beta/essential-contacts/compute index 60d0b826b..38ceb191f 100644 --- a/gcloud/beta/essential-contacts/compute +++ b/gcloud/beta/essential-contacts/compute @@ -26,8 +26,7 @@ EXAMPLES for the folder with id 123, run: $ gcloud beta essential-contacts compute \ - --notification-categories=product-updates,billing - --folder=123 + --notification-categories=product-updates,billing --folder=123 To compute contacts subscribed to the legal category for the organization with id 456, run: diff --git a/gcloud/beta/essential-contacts/create b/gcloud/beta/essential-contacts/create index c475f2b6a..2dd13203c 100644 --- a/gcloud/beta/essential-contacts/create +++ b/gcloud/beta/essential-contacts/create @@ -11,22 +11,23 @@ EXAMPLES To create a contact in the current project, run: $ gcloud beta essential-contacts create \ - --email=contact-email@example.com - --notification-categories=technical,product-updates --language=en-US + --email=contact-email@example.com \ + --notification-categories=technical,product-updates \ + --language=en-US To create a contact in the folder with id 456, run: $ gcloud beta essential-contacts create \ - --email=contact-email@example.com - --notification-categories=technical,product-updates --language=en-US - --folder=456 + --email=contact-email@example.com \ + --notification-categories=technical,product-updates \ + --language=en-US --folder=456 To create a contact in the organization with id 456, run: $ gcloud beta essential-contacts create \ - --email=contact-email@example.com - --notification-categories=technical,product-updates --language=en-US - --organization=456 + --email=contact-email@example.com \ + --notification-categories=technical,product-updates \ + --language=en-US --organization=456 REQUIRED FLAGS --email=EMAIL diff --git a/gcloud/beta/essential-contacts/update b/gcloud/beta/essential-contacts/update index 4f3cad628..9a44bafbc 100644 --- a/gcloud/beta/essential-contacts/update +++ b/gcloud/beta/essential-contacts/update @@ -24,7 +24,7 @@ EXAMPLES for the contact with id 123 in the organization with id 456, run: $ gcloud beta essential-contacts update 123 \ - --notification-categories=legal --language=en-US + --notification-categories=legal --language=en-US \ --organization=456 POSITIONAL ARGUMENTS diff --git a/gcloud/beta/events/triggers/create b/gcloud/beta/events/triggers/create index 854d3ab94..5e1df68fe 100644 --- a/gcloud/beta/events/triggers/create +++ b/gcloud/beta/events/triggers/create @@ -20,8 +20,8 @@ EXAMPLES To create a trigger for a Cloud Pub/Sub event type: $ gcloud beta events triggers create TRIGGER \ - --type=google.cloud.pubsub.topic.v1.messagePublished - --parameters="topic=my-topic" --target-service=my-service + --type=google.cloud.pubsub.topic.v1.messagePublished \ + --parameters="topic=my-topic" --target-service=my-service POSITIONAL ARGUMENTS Trigger resource - Name of the trigger to create The arguments in this diff --git a/gcloud/beta/filestore/instances/restore b/gcloud/beta/filestore/instances/restore index d1c1f15e0..900dc0984 100644 --- a/gcloud/beta/filestore/instances/restore +++ b/gcloud/beta/filestore/instances/restore @@ -17,10 +17,8 @@ EXAMPLES 'my-backup' in the region europe-west3. $ gcloud beta filestore instances restore my-instance \ - --zone=europe-west3-a \ - --file-share=vol1 \ - --source-backup=my-backup \ - --source-backup-region=europe-west3 + --zone=europe-west3-a --file-share=vol1 \ + --source-backup=my-backup --source-backup-region=europe-west3 POSITIONAL ARGUMENTS Instance resource - Arguments and flags that specify the Filestore diff --git a/gcloud/beta/filestore/instances/update b/gcloud/beta/filestore/instances/update index 6526b1be4..731ad818f 100644 --- a/gcloud/beta/filestore/instances/update +++ b/gcloud/beta/filestore/instances/update @@ -53,7 +53,7 @@ EXAMPLES capacity to CAPACITY. $ gcloud beta filestore instances update NAME --project=PROJECT_ID \ - --zone=ZONE --file-share=name=VOLUME_NAME,capacity=CAPACITY + --zone=ZONE --file-share=name=VOLUME_NAME,capacity=CAPACITY POSITIONAL ARGUMENTS Instance resource - The instance to update. The arguments in this group diff --git a/gcloud/beta/firestore/indexes/fields/list b/gcloud/beta/firestore/indexes/fields/list index be5b36453..0253a3a33 100644 --- a/gcloud/beta/firestore/indexes/fields/list +++ b/gcloud/beta/firestore/indexes/fields/list @@ -26,9 +26,10 @@ EXAMPLES The following command lists the indexes of all fields with custom index settings: - $ gcloud beta firestore indexes fields list --format="table[box](\ - name,indexConfig.indexes:format='table[title=INDEXES,box](\ - fields.order.flatten(),fields.arrayConfig.flatten(),queryScope,state)')" + $ gcloud beta firestore indexes fields list \ + --format="table[box](name,indexConfig.indexes:format='table[titl\ + e=INDEXES,box](fields.order.flatten(),fields.arrayConfig.flatten(),q\ + ueryScope,state)')" FLAGS Collection group resource - Collection group of the index. diff --git a/gcloud/beta/firestore/indexes/fields/update b/gcloud/beta/firestore/indexes/fields/update index b68c2b444..33362d28a 100644 --- a/gcloud/beta/firestore/indexes/fields/update +++ b/gcloud/beta/firestore/indexes/fields/update @@ -20,16 +20,14 @@ EXAMPLES Events collection group, in which all indexes are disabled: $ gcloud beta firestore indexes fields update timestamp \ - --collection-group=Events - --disable-indexes + --collection-group=Events --disable-indexes The following command creates an exemption for the timestamp field in the Events collection group, in which the list of indexes is explicitly set to [ASCENDING, DESCENDING]: $ gcloud beta firestore indexes fields update timestamp \ - --collection-group=Events \ - --index=order=ASCENDING \ + --collection-group=Events --index=order=ASCENDING \ --index=order=DESCENDING The following command clears the exemption on the timestamp field in the diff --git a/gcloud/beta/functions/deploy b/gcloud/beta/functions/deploy index cac7d96c1..7f4015e6f 100644 --- a/gcloud/beta/functions/deploy +++ b/gcloud/beta/functions/deploy @@ -486,28 +486,27 @@ FLAGS We recommend referencing the latest version when using secret volumes so that the secret's value changes are reflected immediately. - Only `--update-secrets` and `--remove-secrets` can be used together. If - both are specified, then `--remove-secrets` will be applied first. + Only --update-secrets and --remove-secrets can be used together. If both + are specified, then --remove-secrets will be applied first. - --remove-secrets=[SECRET_ENV_VAR,/secret_path,/mount_path:/secret_file_path,...] - List of secret environment variable names and secret paths to - remove. + --remove-secrets=[SECRET_ENV_VAR,/secret_path,/mount_path:/secret_file_path,...] + List of secret environment variable names and secret paths to + remove. - Existing secrets configuration of secret environment variable - names and secret paths not specified in this list will be - preserved. + Existing secrets configuration of secret environment variable names + and secret paths not specified in this list will be preserved. - To remove a secret environment variable, use the name of the - environment variable SECRET_ENV_VAR. + To remove a secret environment variable, use the name of the + environment variable SECRET_ENV_VAR. - To remove a file within a secret volume or the volume itself, use - the secret path as the key (either /secret_path or - /mount_path:/secret_file_path). + To remove a file within a secret volume or the volume itself, use + the secret path as the key (either /secret_path or + /mount_path:/secret_file_path). - --update-secrets=[SECRET_ENV_VAR=SECRET_VALUE_REF,/secret_path=SECRET_VALUE_REF,/mount_path:/secret_file_path=SECRET_VALUE_REF,...] - List of secret environment variables and secret volumes to - update. Existing secrets configuration not specified in this list - will be preserved. + --update-secrets=[SECRET_ENV_VAR=SECRET_VALUE_REF,/secret_path=SECRET_VALUE_REF,/mount_path:/secret_file_path=SECRET_VALUE_REF,...] + List of secret environment variables and secret volumes to update. + Existing secrets configuration not specified in this list will be + preserved. At most one of these can be specified: diff --git a/gcloud/beta/game/servers/clusters/create b/gcloud/beta/game/servers/clusters/create index f5a6a43ca..070c19a55 100644 --- a/gcloud/beta/game/servers/clusters/create +++ b/gcloud/beta/game/servers/clusters/create @@ -17,16 +17,18 @@ EXAMPLES $ gcloud beta game servers clusters create my-cluster \ --project=my-project --realm=my-realm --location=my-location \ - --gke-cluster=projects/my-project/locations/my-location/clusters/my-gke-cluster \ - --namespace=default --labels=a=x,b=y --no-dry-run + --gke-cluster=projects/my-project/locations/my-location/\ + clusters/my-gke-cluster --namespace=default --labels=a=x,b=y \ + --no-dry-run To preview Game Server Cluster creation for 'my-cluster' in project 'my-project', realm 'my-realm', and location in 'my-location' run: $ gcloud beta game servers clusters create my-cluster \ --project=my-project --realm=my-realm --location=my-location \ - --gke-cluster=projects/my-project/locations/my-location/clusters/my-gke-cluster \ - --namespace=default --labels=a=x,b=y --dry-run + --gke-cluster=projects/my-project/locations/my-location/\ + clusters/my-gke-cluster --namespace=default --labels=a=x,b=y \ + --dry-run POSITIONAL ARGUMENTS Game server cluster resource - Cloud Game Server Cluster to create. The diff --git a/gcloud/beta/game/servers/clusters/update b/gcloud/beta/game/servers/clusters/update index 42bbf3f66..24460e2f4 100644 --- a/gcloud/beta/game/servers/clusters/update +++ b/gcloud/beta/game/servers/clusters/update @@ -17,14 +17,14 @@ EXAMPLES $ gcloud beta game servers clusters update my-cluster \ --project=my-project --realm=my-realm --location=my-location \ - --update-labels="key1=val1" --no-dry-run + --update-labels="key1=val1" --no-dry-run To preview Game Server Cluster label update for 'my-cluster' in project 'my-project', realm 'my-realm', and location in 'my-location' run: $ gcloud beta game servers clusters update my-cluster \ --project=my-project --realm=my-realm --location=my-location \ - --update-labels="key1=val1" --dry-run + --update-labels="key1=val1" --dry-run POSITIONAL ARGUMENTS Game server cluster resource - Cloud Game Server Cluster to update. The diff --git a/gcloud/beta/game/servers/configs/create b/gcloud/beta/game/servers/configs/create index ac5bda8a7..4b20e5c65 100644 --- a/gcloud/beta/game/servers/configs/create +++ b/gcloud/beta/game/servers/configs/create @@ -18,8 +18,8 @@ EXAMPLES $ gcloud beta game servers configs create my-config \ --project=my-project --deployment=my-deployment \ - --location=global \ - --deployment=my-deployment --description=description --labels=a=x,b=y \ + --location=global --deployment=my-deployment \ + --description=description --labels=a=x,b=y \ --fleet-configs-file=fleet_configs.json POSITIONAL ARGUMENTS diff --git a/gcloud/beta/game/servers/deployments/create b/gcloud/beta/game/servers/deployments/create index a889f51f5..6292f7110 100644 --- a/gcloud/beta/game/servers/deployments/create +++ b/gcloud/beta/game/servers/deployments/create @@ -17,8 +17,7 @@ EXAMPLES $ gcloud beta game servers deployments create my-deployment \ --project=my-project --location=global \ - --description=description \ - --labels=a=x,b=y + --description=description --labels=a=x,b=y POSITIONAL ARGUMENTS Deployment resource - Cloud Game Server Deployment to create. The diff --git a/gcloud/beta/iam/list-grantable-roles b/gcloud/beta/iam/list-grantable-roles index 846ee966e..5ba01f5cc 100644 --- a/gcloud/beta/iam/list-grantable-roles +++ b/gcloud/beta/iam/list-grantable-roles @@ -26,7 +26,8 @@ EXAMPLES List grantable roles for a resource identified via URI: $ gcloud beta iam list-grantable-roles \ - https://www.googleapis.com/compute/v1/projects/example-project/zones/us-central1-f/instances/example-instance + https://www.googleapis.com/compute/v1/projects/example-project/\ + zones/us-central1-f/instances/example-instance POSITIONAL ARGUMENTS RESOURCE diff --git a/gcloud/beta/iam/policies/create b/gcloud/beta/iam/policies/create new file mode 100644 index 000000000..996d3cff6 --- /dev/null +++ b/gcloud/beta/iam/policies/create @@ -0,0 +1,49 @@ +NAME + gcloud beta iam policies create - create a policy on the given attachment + point with the given name + +SYNOPSIS + gcloud beta iam policies create POLICY_ID + --attachment-point=ATTACHMENT_POINT --kind=KIND + --policy-file=POLICY_FILE [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Create a policy on the given attachment point with the given name. + +EXAMPLES + The following command creates the IAM policy defined at the resource + project 123 of kind denypolicies and id my-deny-policy from the file + policy.json: + + $ gcloud beta iam policies create my-deny-policy \ + --attachment-point=cloudresourcemanager.googleapis.com/\ + projects/123 --kind=denypolicies --policy-file=policy.json + +POSITIONAL ARGUMENTS + POLICY_ID + Id of the policy. + +REQUIRED FLAGS + --attachment-point=ATTACHMENT_POINT + Resource to which the policy is attached. + + --kind=KIND + Kind of the policy. + + --policy-file=POLICY_FILE + Contents 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. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha iam policies create + diff --git a/gcloud/beta/iam/policies/delete b/gcloud/beta/iam/policies/delete new file mode 100644 index 000000000..65d4ed5f8 --- /dev/null +++ b/gcloud/beta/iam/policies/delete @@ -0,0 +1,52 @@ +NAME + gcloud beta iam policies delete - delete a policy on the given attachment + point with the given name + +SYNOPSIS + gcloud beta iam policies delete POLICY_ID + --attachment-point=ATTACHMENT_POINT --kind=KIND [--etag=ETAG] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Delete a policy on the given attachment point with the given name. + +EXAMPLES + The following command deletes the IAM policy defined at the resource + project 123 of kind denypolicies and id my-deny-policy, with etag abc: + + $ gcloud beta iam policies delete my-deny-policy \ + --attachment-point=cloudresourcemanager.googleapis.com/\ + projects/123 --kind=denypolicies --etag=abc + + If etag isn't provided, the command will try to get the etag using the + calling user permissions. + +POSITIONAL ARGUMENTS + POLICY_ID + Id of the policy. + +REQUIRED FLAGS + --attachment-point=ATTACHMENT_POINT + Resource to which the policy is attached. + + --kind=KIND + Kind of the policy. + +OPTIONAL FLAGS + --etag=ETAG + Etag of the existing 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 beta and might change without notice. This + variant is also available: + + $ gcloud alpha iam policies delete + diff --git a/gcloud/beta/iam/policies/get b/gcloud/beta/iam/policies/get new file mode 100644 index 000000000..3ee786e0c --- /dev/null +++ b/gcloud/beta/iam/policies/get @@ -0,0 +1,44 @@ +NAME + gcloud beta iam policies get - get a policy on the given attachment point + with the given name + +SYNOPSIS + gcloud beta iam policies get POLICY_ID --attachment-point=ATTACHMENT_POINT + --kind=KIND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Get a policy on the given attachment point with the given name. + +EXAMPLES + The following command gets the IAM policy defined at the resource project + 123 of kind denypolicies and id my-deny-policy: + + $ gcloud beta iam policies get my-deny-policy \ + --attachment-point=cloudresourcemanager.googleapis.com/\ + projects/123 --kind=denypolicies + +POSITIONAL ARGUMENTS + POLICY_ID + Id of the policy. + +REQUIRED FLAGS + --attachment-point=ATTACHMENT_POINT + Resource to which the policy is attached. + + --kind=KIND + Kind 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. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha iam policies get + diff --git a/gcloud/beta/iam/policies/help b/gcloud/beta/iam/policies/help index a09289259..e0f3fddd8 100644 --- a/gcloud/beta/iam/policies/help +++ b/gcloud/beta/iam/policies/help @@ -12,6 +12,27 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. +COMMANDS + COMMAND is one of the following: + + create + (BETA) Create a policy on the given attachment point with the given + name. + + delete + (BETA) Delete a policy on the given attachment point with the given + name. + + get + (BETA) Get a policy on the given attachment point with the given name. + + list + (BETA) List the policies on the given attachment point. + + update + (BETA) Update the policy on the given attachment point with the given + name. + NOTES This command is currently in beta and might change without notice. This variant is also available: diff --git a/gcloud/beta/iam/policies/list b/gcloud/beta/iam/policies/list new file mode 100644 index 000000000..62057d076 --- /dev/null +++ b/gcloud/beta/iam/policies/list @@ -0,0 +1,72 @@ +NAME + gcloud beta iam policies list - list the policies on the given attachment + point + +SYNOPSIS + gcloud beta iam policies list --attachment-point=ATTACHMENT_POINT + --kind=KIND [--page_token=PAGE_TOKEN] [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) List the policies on the given attachment point. + +EXAMPLES + The following command lists the IAM policy defined at the resource project + 123 of kind denypolicies: + + $ gcloud beta iam policies list \ + --attachment-point=cloudresourcemanager.googleapis.com/\ + projects/123 --kind=denypolicies + +REQUIRED FLAGS + --attachment-point=ATTACHMENT_POINT + Resource to which the policy is attached. + + --kind=KIND + Kind of the policy. + +FLAGS + --page_token=PAGE_TOKEN + Page token received from a previous call. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha iam policies list + diff --git a/gcloud/beta/iam/policies/update b/gcloud/beta/iam/policies/update new file mode 100644 index 000000000..53c56f12c --- /dev/null +++ b/gcloud/beta/iam/policies/update @@ -0,0 +1,56 @@ +NAME + gcloud beta iam policies update - update the policy on the given attachment + point with the given name + +SYNOPSIS + gcloud beta iam policies update POLICY_ID + --attachment-point=ATTACHMENT_POINT --kind=KIND + --policy-file=POLICY_FILE [--etag=ETAG] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Update the policy on the given attachment point with the given name. + +EXAMPLES + The following command updates the IAM policy defined at the resource + project 123 of kind denypolicies and id my-deny-policy, with etag abc: + + $ gcloud beta iam policies update my-deny-policy \ + --attachment-point=cloudresourcemanager.googleapis.com/\ + projects/123 --kind=denypolicies --policy-file=policy.json \ + --etag=abc + + If etag isn't provided, the command will try to get the etag using the + calling user permissions. + +POSITIONAL ARGUMENTS + POLICY_ID + Id of the policy. + +REQUIRED FLAGS + --attachment-point=ATTACHMENT_POINT + Resource to which the policy is attached. + + --kind=KIND + Kind of the policy. + + --policy-file=POLICY_FILE + Contents of the policy. + +OPTIONAL FLAGS + --etag=ETAG + Etag of the existing 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 beta and might change without notice. This + variant is also available: + + $ gcloud alpha iam policies update + diff --git a/gcloud/beta/iam/workload-identity-pools/create b/gcloud/beta/iam/workload-identity-pools/create index 71c56311a..1ea3e3776 100644 --- a/gcloud/beta/iam/workload-identity-pools/create +++ b/gcloud/beta/iam/workload-identity-pools/create @@ -17,11 +17,9 @@ EXAMPLES all required and optional parameters are provided. $ gcloud beta iam workload-identity-pools create \ - my-workload-identity-pool \ - --location="global" \ + my-workload-identity-pool --location="global" \ --display-name="My workload pool" \ - --description="My workload pool description" \ - --disabled + --description="My workload pool description" --disabled POSITIONAL ARGUMENTS Workload identity pool resource - The workload identity pool to create. diff --git a/gcloud/beta/iam/workload-identity-pools/providers/create-aws b/gcloud/beta/iam/workload-identity-pools/providers/create-aws index a3f10e56d..5943572df 100644 --- a/gcloud/beta/iam/workload-identity-pools/providers/create-aws +++ b/gcloud/beta/iam/workload-identity-pools/providers/create-aws @@ -20,15 +20,12 @@ EXAMPLES Explicit values for all required and optional parameters are provided. $ gcloud beta iam workload-identity-pools providers create-aws \ - my-workload-identity-pool-provider \ - --location="global" \ + my-workload-identity-pool-provider --location="global" \ --workload-identity-pool="my-workload-identity-pool" \ --display-name="My workload pool provider" \ --description="My workload pool provider description" \ - --disabled \ - --attribute-mapping="google.subject=assertion.arn" \ - --attribute-condition="true" \ - --account-id=1234567890 + --disabled --attribute-mapping="google.subject=assertion.arn" \ + --attribute-condition="true" --account-id=1234567890 POSITIONAL ARGUMENTS Workload identity pool provider resource - The workload identity pool diff --git a/gcloud/beta/iam/workload-identity-pools/providers/create-oidc b/gcloud/beta/iam/workload-identity-pools/providers/create-oidc index 745ab17bd..8cb578c20 100644 --- a/gcloud/beta/iam/workload-identity-pools/providers/create-oidc +++ b/gcloud/beta/iam/workload-identity-pools/providers/create-oidc @@ -20,16 +20,15 @@ EXAMPLES Explicit values for all required and optional parameters are provided. $ gcloud beta iam workload-identity-pools providers create-oidc \ - my-workload-identity-pool-provider \ - --location="global" \ + my-workload-identity-pool-provider --location="global" \ --workload-identity-pool="my-workload-identity-pool" \ --display-name="My workload pool provider" \ --description="My workload pool provider description" \ - --disabled \ - --attribute-mapping="google.subject=assertion.sub" \ + --disabled --attribute-mapping="google.subject=assertion.sub" \ --attribute-condition="true" \ --issuer-uri="https://test-idp.com" \ - --allowed-audiences=https://test-audience-1.com,https://test-audience-2.com + --allowed-audiences=https://test-audience-1.com,https://\ + test-audience-2.com POSITIONAL ARGUMENTS Workload identity pool provider resource - The workload identity pool diff --git a/gcloud/beta/iam/workload-identity-pools/providers/delete b/gcloud/beta/iam/workload-identity-pools/providers/delete index cfc165b3c..b9cbaa61b 100644 --- a/gcloud/beta/iam/workload-identity-pools/providers/delete +++ b/gcloud/beta/iam/workload-identity-pools/providers/delete @@ -17,8 +17,8 @@ EXAMPLES $ gcloud beta iam workload-identity-pools providers delete \ my-workload-identity-pool-provider \ - --workload-identity-pool="my-workload-identity-pool" \ - --location="global" + --workload-identity-pool="my-workload-identity-pool" \ + --location="global" POSITIONAL ARGUMENTS Workload identity pool provider resource - The workload identity pool diff --git a/gcloud/beta/iam/workload-identity-pools/providers/describe b/gcloud/beta/iam/workload-identity-pools/providers/describe index 7b1de39ac..6c5cc8a3a 100644 --- a/gcloud/beta/iam/workload-identity-pools/providers/describe +++ b/gcloud/beta/iam/workload-identity-pools/providers/describe @@ -16,9 +16,9 @@ EXAMPLES the ID my-workload-identity-pool-provider: $ gcloud beta iam workload-identity-pools providers describe \ - my-workload-identity-pool-provider \ - --workload-identity-pool="my-workload-identity-pool" \ - --location="global" + my-workload-identity-pool-provider \ + --workload-identity-pool="my-workload-identity-pool" \ + --location="global" POSITIONAL ARGUMENTS Workload identity pool provider resource - The workload identity pool diff --git a/gcloud/beta/iam/workload-identity-pools/providers/list b/gcloud/beta/iam/workload-identity-pools/providers/list index 613ea2350..c1317e471 100644 --- a/gcloud/beta/iam/workload-identity-pools/providers/list +++ b/gcloud/beta/iam/workload-identity-pools/providers/list @@ -15,10 +15,9 @@ EXAMPLES The following command lists all workload identity pool providers in the workload identity pool, including soft-deleted providers: - $ gcloud beta iam workload-identity-pools providers list \ - --workload-identity-pool="my-workload-identity-pool" \ - --location="global" \ - --show-deleted + $ gcloud beta iam workload-identity-pools providers list \ + --workload-identity-pool="my-workload-identity-pool" \ + --location="global" --show-deleted REQUIRED FLAGS Workload identity pool resource - The location to list workload identity diff --git a/gcloud/beta/iam/workload-identity-pools/providers/operations/describe b/gcloud/beta/iam/workload-identity-pools/providers/operations/describe index b60c59be6..63248cd18 100644 --- a/gcloud/beta/iam/workload-identity-pools/providers/operations/describe +++ b/gcloud/beta/iam/workload-identity-pools/providers/operations/describe @@ -18,8 +18,7 @@ EXAMPLES $ gcloud beta iam workload-identity-pools providers operations \ describe my-operation \ --workload-identity-pool="my-workload-identity-pool" \ - --provider="my-provider" \ - --location="global" + --provider="my-provider" --location="global" POSITIONAL ARGUMENTS Workload identity pool provider operation resource - The workload identity diff --git a/gcloud/beta/iam/workload-identity-pools/providers/undelete b/gcloud/beta/iam/workload-identity-pools/providers/undelete index 07078a51f..d5e634574 100644 --- a/gcloud/beta/iam/workload-identity-pools/providers/undelete +++ b/gcloud/beta/iam/workload-identity-pools/providers/undelete @@ -17,8 +17,8 @@ EXAMPLES $ gcloud beta iam workload-identity-pools providers undelete \ my-workload-identity-pool-provider \ - --workload-identity-pool="my-workload-identity-pool" \ - --location="global" + --workload-identity-pool="my-workload-identity-pool" \ + --location="global" POSITIONAL ARGUMENTS Workload identity pool provider resource - The workload identity pool diff --git a/gcloud/beta/iam/workload-identity-pools/providers/update-aws b/gcloud/beta/iam/workload-identity-pools/providers/update-aws index a7efe1ae4..3879aaa44 100644 --- a/gcloud/beta/iam/workload-identity-pools/providers/update-aws +++ b/gcloud/beta/iam/workload-identity-pools/providers/update-aws @@ -24,10 +24,8 @@ EXAMPLES --workload-identity-pool="my-workload-identity-pool" \ --display-name="My workload pool provider" \ --description="My workload pool provider description" \ - --disabled \ - --attribute-mapping="google.subject=assertion.arn" \ - --attribute-condition="true" \ - --account-id=1234567890 + --disabled --attribute-mapping="google.subject=assertion.arn" \ + --attribute-condition="true" --account-id=1234567890 POSITIONAL ARGUMENTS Workload identity pool provider resource - The workload identity pool diff --git a/gcloud/beta/iam/workload-identity-pools/providers/update-oidc b/gcloud/beta/iam/workload-identity-pools/providers/update-oidc index 9f5346fd8..8c9556e00 100644 --- a/gcloud/beta/iam/workload-identity-pools/providers/update-oidc +++ b/gcloud/beta/iam/workload-identity-pools/providers/update-oidc @@ -21,16 +21,15 @@ EXAMPLES and optional parameters are provided: $ gcloud beta iam workload-identity-pools providers update-oidc \ - my-workload-identity-pool-provider \ - --location="global" \ + my-workload-identity-pool-provider --location="global" \ --workload-identity-pool="my-workload-identity-pool" \ --display-name="My workload pool provider" \ --description="My workload pool provider description" \ - --disabled \ - --attribute-mapping="google.subject=assertion.sub" \ + --disabled --attribute-mapping="google.subject=assertion.sub" \ --attribute-condition="true" \ - --issuer-uri="https://test-idp.com" - --allowed-audiences=https://test-audience-1.com,https://test-audience-2.com + --issuer-uri="https://test-idp.com" \ + --allowed-audiences=https://test-audience-1.com,https://\ + test-audience-2.com POSITIONAL ARGUMENTS Workload identity pool provider resource - The workload identity pool diff --git a/gcloud/beta/iam/workload-identity-pools/update b/gcloud/beta/iam/workload-identity-pools/update index 80a502eac..fc4a6332f 100644 --- a/gcloud/beta/iam/workload-identity-pools/update +++ b/gcloud/beta/iam/workload-identity-pools/update @@ -16,11 +16,9 @@ EXAMPLES my-workload-identity-pool: $ gcloud beta iam workload-identity-pools update \ - my-workload-identity-pool \ - --location="global" + my-workload-identity-pool --location="global" \ --display-name="My workload pool" \ - --description="My workload pool description" \ - --disabled + --description="My workload pool description" --disabled POSITIONAL ARGUMENTS Workload identity pool resource - The workload identity pool to update. diff --git a/gcloud/beta/iap/oauth-brands/create b/gcloud/beta/iap/oauth-brands/create index d0265264a..340bc739c 100644 --- a/gcloud/beta/iap/oauth-brands/create +++ b/gcloud/beta/iap/oauth-brands/create @@ -27,7 +27,7 @@ EXAMPLES To create a Cloud OAuth brand for the project PROJECT_ID, run: - $ gcloud beta iap oauth-brands create \ + $ gcloud beta iap oauth-brands create \ --application_title=APPLICATION_TITLE \ --support_email=SUPPORT_EMAIL --project=PROJECT_ID diff --git a/gcloud/beta/iap/oauth-brands/list b/gcloud/beta/iap/oauth-brands/list index f9584ee30..a6f5829f6 100644 --- a/gcloud/beta/iap/oauth-brands/list +++ b/gcloud/beta/iap/oauth-brands/list @@ -16,7 +16,7 @@ EXAMPLES To list all Cloud OAuth brands in the project PROJECT_ID, run: - $ gcloud beta iap oauth-brands list --project=PROJECT_ID + $ gcloud beta iap oauth-brands list --project=PROJECT_ID LIST COMMAND FLAGS --filter=EXPRESSION diff --git a/gcloud/beta/iap/settings/get b/gcloud/beta/iap/settings/get index fe2c4fa56..b01e37310 100644 --- a/gcloud/beta/iap/settings/get +++ b/gcloud/beta/iap/settings/get @@ -42,7 +42,7 @@ EXAMPLES run: $ gcloud beta iap settings get --project=PROJECT_ID \ - --resource-type=app-engine --service=SERVICE_ID + --resource-type=app-engine --service=SERVICE_ID \ --version=VERSION_ID To get the IAP setting for all backend services within a project, run: diff --git a/gcloud/beta/iap/settings/set b/gcloud/beta/iap/settings/set index 8ab2b9ccb..906aabec2 100644 --- a/gcloud/beta/iap/settings/set +++ b/gcloud/beta/iap/settings/set @@ -43,7 +43,7 @@ EXAMPLES run: $ gcloud beta iap settings set SETTING_FILE --project=PROJECT_ID \ - --resource-type=app-engine --service=SERVICE_ID + --resource-type=app-engine --service=SERVICE_ID \ --version=VERSION_ID To set the IAP setting for all backend services within a project, run: diff --git a/gcloud/beta/iap/web/add-iam-policy-binding b/gcloud/beta/iap/web/add-iam-policy-binding index 62dcee8f7..d3c2f8614 100644 --- a/gcloud/beta/iap/web/add-iam-policy-binding +++ b/gcloud/beta/iap/web/add-iam-policy-binding @@ -24,16 +24,14 @@ EXAMPLES $ gcloud beta iap web add-iam-policy-binding \ --resource-type=IAP_IAM_RESOURCE \ - --member='user:test-user@gmail.com' - --role='roles/editor' + --member='user:test-user@gmail.com' --role='roles/editor' To add an IAM policy binding for the role of 'roles/editor' for all authenticated users on IAP IAM resource IAP_IAM_RESOURCE, run: $ gcloud beta iap web add-iam-policy-binding \ --resource-type=IAP_IAM_RESOURCE \ - --member='allAuthenticatedUsers' - --role='roles/editor' + --member='allAuthenticatedUsers' --role='roles/editor' To add an IAM policy binding which expires at the end of the year 2018 for the role of 'roles/browser' and the user 'test-user@gmail.com' on IAP IAM @@ -41,8 +39,8 @@ EXAMPLES $ gcloud beta iap web add-iam-policy-binding \ --resource-type=IAP_IAM_RESOURCE \ - --member='user:test-user@gmail.com' - --role='roles/browser' --condition='expression=request.time < + --member='user:test-user@gmail.com' --role='roles/browser' \ + --condition='expression=request.time < timestamp("2019-01-01T00:00:00Z"),title=expires_end_of_2018, description=Expires at midnight on 2018-12-31' diff --git a/gcloud/beta/iap/web/enable b/gcloud/beta/iap/web/enable index 0ff618691..a2908addd 100644 --- a/gcloud/beta/iap/web/enable +++ b/gcloud/beta/iap/web/enable @@ -17,13 +17,13 @@ DESCRIPTION EXAMPLES To enable IAP on an App Engine application, run: - $ gcloud beta iap web enable --resource-type=app-engine + $ gcloud beta iap web enable --resource-type=app-engine \ --oauth2-client-id=CLIENT_ID --oauth2-client-secret=SECRET To enable IAP on a backend service, run: - $ gcloud beta iap web enable --resource-type=backend-services - --oauth2-client-id=CLIENT_ID --oauth2-client-secret=SECRET + $ gcloud beta iap web enable --resource-type=backend-services \ + --oauth2-client-id=CLIENT_ID --oauth2-client-secret=SECRET \ --service=SERVICE_ID FLAGS diff --git a/gcloud/beta/iap/web/get-iam-policy b/gcloud/beta/iap/web/get-iam-policy index 83910f8db..34142caa3 100644 --- a/gcloud/beta/iap/web/get-iam-policy +++ b/gcloud/beta/iap/web/get-iam-policy @@ -41,8 +41,7 @@ EXAMPLES within an App Engine service version, run: $ gcloud beta iap web get-iam-policy --resource-type=app-engine \ - --service=SERVICE_ID - --version=VERSION + --service=SERVICE_ID --version=VERSION To get the IAM policy for the web accesses to the IAP protected resources within all backend services, run: diff --git a/gcloud/beta/iap/web/remove-iam-policy-binding b/gcloud/beta/iap/web/remove-iam-policy-binding index e51fa3bb1..62552ace2 100644 --- a/gcloud/beta/iap/web/remove-iam-policy-binding +++ b/gcloud/beta/iap/web/remove-iam-policy-binding @@ -25,16 +25,14 @@ EXAMPLES $ gcloud beta iap web remove-iam-policy-binding \ --resource-type=IAP_IAM_RESOURCE \ - --member='user:test-user@gmail.com' - --role='roles/editor' + --member='user:test-user@gmail.com' --role='roles/editor' To remove an IAM policy binding for the role of 'roles/editor' from all authenticated users on IAP IAM resource IAP_IAM_RESOURCE,run: $ gcloud beta iap web remove-iam-policy-binding \ --resource-type=IAP_IAM_RESOURCE \ - --member='allAuthenticatedUsers' - --role='roles/editor' + --member='allAuthenticatedUsers' --role='roles/editor' To remove an IAM policy binding with a condition of expression='request.time < timestamp("2019-01-01T00:00:00Z")', @@ -44,8 +42,8 @@ EXAMPLES $ gcloud beta iap web remove-iam-policy-binding \ --resource-type=IAP_IAM_RESOURCE \ - --member='user:test-user@gmail.com' - --role='roles/browser' --condition='expression=request.time < + --member='user:test-user@gmail.com' --role='roles/browser' \ + --condition='expression=request.time < timestamp("2019-01-01T00:00:00Z"),title=expires_end_of_2018, description=Expires at midnight on 2018-12-31' @@ -55,8 +53,7 @@ EXAMPLES $ gcloud beta iap web remove-iam-policy-binding \ --resource-type=IAP_IAM_RESOURCE \ - --member='user:test-user@gmail.com' - --role='roles/browser' --all + --member='user:test-user@gmail.com' --role='roles/browser' --all See https://cloud.google.com/iam/docs/managing-policies for details of policy role and member types. diff --git a/gcloud/beta/iap/web/set-iam-policy b/gcloud/beta/iap/web/set-iam-policy index 0d7b98bfe..3b7121ad5 100644 --- a/gcloud/beta/iap/web/set-iam-policy +++ b/gcloud/beta/iap/web/set-iam-policy @@ -38,15 +38,14 @@ EXAMPLES within an App Engine service, run: $ gcloud beta iap web set-iam-policy POLICY_FILE \ - --resource-type=app-engine - --service=SERVICE_ID + --resource-type=app-engine --service=SERVICE_ID To set the IAM policy for the web accesses to the IAP protected resources within an App Engine service version, run: $ gcloud beta iap web set-iam-policy POLICY_FILE \ - --resource-type=app-engine - --service=SERVICE_ID --version=VERSION + --resource-type=app-engine --service=SERVICE_ID \ + --version=VERSION To set the IAM policy for the web accesses to the IAP protected resources within all backend services, run: @@ -58,8 +57,7 @@ EXAMPLES within a backend service, run: $ gcloud beta iap web set-iam-policy POLICY_FILE \ - --resource-type=backend-services - --service=SERVICE_ID + --resource-type=backend-services --service=SERVICE_ID POSITIONAL ARGUMENTS POLICY_FILE diff --git a/gcloud/beta/identity/groups/create b/gcloud/beta/identity/groups/create index cf3b9d5ae..04af5f7ad 100644 --- a/gcloud/beta/identity/groups/create +++ b/gcloud/beta/identity/groups/create @@ -23,23 +23,20 @@ EXAMPLES descripton: $ gcloud beta identity groups create eng-discuss@example.com \ - --organization="example.com" \ - --display-name="Engineer Discuss" \ + --organization="example.com" --display-name="Engineer Discuss" \ --description="Group for engineering discussions" To create a new security group: - $ gcloud beta identity groups create security-group@example.com \ - --organization="example.com" \ - --group-type="security" \ - --display-name="Security Group" \ + $ gcloud beta identity groups create security-group@example.com \ + --organization="example.com" --group-type="security" \ + --display-name="Security Group" \ --description="Description of Security Group" To create a new POSIX group: $ gcloud beta identity groups create eng-discuss@example.com \ - --organization="example.com" \ - --posix-group=name=eng,gid=1005 + --organization="example.com" --posix-group=name=eng,gid=1005 POSITIONAL ARGUMENTS EMAIL diff --git a/gcloud/beta/identity/groups/memberships/add b/gcloud/beta/identity/groups/memberships/add index 85cb29d4f..a572cf299 100644 --- a/gcloud/beta/identity/groups/memberships/add +++ b/gcloud/beta/identity/groups/memberships/add @@ -15,7 +15,7 @@ EXAMPLES To create a new membership in a group: $ gcloud beta identity groups memberships add \ - --group-email="eng-discuss@foo.com" \ + --group-email="eng-discuss@foo.com" \ --member-email="user@foo.com" REQUIRED FLAGS diff --git a/gcloud/beta/identity/groups/memberships/modify-membership-roles b/gcloud/beta/identity/groups/memberships/modify-membership-roles index b203fc99a..b69620372 100644 --- a/gcloud/beta/identity/groups/memberships/modify-membership-roles +++ b/gcloud/beta/identity/groups/memberships/modify-membership-roles @@ -17,9 +17,8 @@ EXAMPLES To add a new membership role to an existing group-member pair. $ gcloud beta identity groups memberships modify-membership-roles \ - --group-email="eng-discuss@foo.com" \ - --member-email="user@foo.com" \ - --add-roles=OWNER + --group-email="eng-discuss@foo.com" \ + --member-email="user@foo.com" --add-roles=OWNER REQUIRED FLAGS --group-email=GROUP_EMAIL diff --git a/gcloud/beta/identity/groups/search b/gcloud/beta/identity/groups/search index e34d4a6fc..5ff388c98 100644 --- a/gcloud/beta/identity/groups/search +++ b/gcloud/beta/identity/groups/search @@ -14,10 +14,9 @@ DESCRIPTION EXAMPLES To Search groups: - $ gcloud beta identity groups search --organization="5149234212" \ - --labels="cloudidentity.googleapis.com/groups.discussion_forum" \ - --page-size=3 \ - --page-token="ala9glealanal908" + $ gcloud beta identity groups search --organization="5149234212" \ + --labels="cloudidentity.googleapis.com/groups.discussion_forum" \ + --page-size=3 --page-token="ala9glealanal908" REQUIRED FLAGS --labels=LABELS diff --git a/gcloud/beta/identity/groups/update b/gcloud/beta/identity/groups/update index 8410e3d3e..2882f98e2 100644 --- a/gcloud/beta/identity/groups/update +++ b/gcloud/beta/identity/groups/update @@ -16,8 +16,8 @@ DESCRIPTION EXAMPLES To update a group: - $ gcloud beta identity groups update eng-discuss@foo.com \ - --display-name="New Engineer Discuss" \ + $ gcloud beta identity groups update eng-discuss@foo.com \ + --display-name="New Engineer Discuss" \ --description="Group for engineering discussions" To create a POSIX group from an existing Google Group: diff --git a/gcloud/beta/kms/asymmetric-decrypt b/gcloud/beta/kms/asymmetric-decrypt index 64c5245dd..ad8e815d5 100644 --- a/gcloud/beta/kms/asymmetric-decrypt +++ b/gcloud/beta/kms/asymmetric-decrypt @@ -22,13 +22,10 @@ EXAMPLES it using the asymmetric CryptoKey dont-panic Version 3 and write the plaintext to '/tmp/my/secret.file.dec'. - $ gcloud beta kms asymmetric-decrypt \ - --location=us-central1 \ - --keyring=hitchhiker \ - --key=dont-panic \ - --version=3 \ - --ciphertext-file=/tmp/my/secret.file.enc \ - --plaintext-file=/tmp/my/secret.file.dec + $ gcloud beta kms asymmetric-decrypt --location=us-central1 \ + --keyring=hitchhiker --key=dont-panic --version=3 \ + --ciphertext-file=/tmp/my/secret.file.enc \ + --plaintext-file=/tmp/my/secret.file.dec REQUIRED FLAGS --ciphertext-file=CIPHERTEXT_FILE diff --git a/gcloud/beta/kms/asymmetric-sign b/gcloud/beta/kms/asymmetric-sign index 37f9b8c40..03f0b7b01 100644 --- a/gcloud/beta/kms/asymmetric-sign +++ b/gcloud/beta/kms/asymmetric-sign @@ -25,14 +25,10 @@ EXAMPLES CryptoKey dont-panic Version 3, and save the signature in base64 format to '/tmp/my/signature'. - $ gcloud beta kms asymmetric-sign \ - --location=us-central1 \ - --keyring=hitchhiker \ - --key=dont-panic \ - --version=3 \ - --digest-algorithm=sha256 \ - --input-file=/tmp/my/file.to.sign \ - --signature-file=/tmp/my/signature + $ gcloud beta kms asymmetric-sign --location=us-central1 \ + --keyring=hitchhiker --key=dont-panic --version=3 \ + --digest-algorithm=sha256 --input-file=/tmp/my/file.to.sign \ + --signature-file=/tmp/my/signature REQUIRED FLAGS --input-file=INPUT_FILE diff --git a/gcloud/beta/kms/decrypt b/gcloud/beta/kms/decrypt index a88c5ccae..f0d9d582f 100644 --- a/gcloud/beta/kms/decrypt +++ b/gcloud/beta/kms/decrypt @@ -37,24 +37,18 @@ EXAMPLES fellowship and location global and write the plaintext to 'path/to/plaintext.dec', run: - $ gcloud beta kms decrypt \ - --key=frodo \ - --keyring=fellowship \ - --location=global \ - --ciphertext-file=path/to/input/ciphertext \ + $ gcloud beta kms decrypt --key=frodo --keyring=fellowship \ + --location=global --ciphertext-file=path/to/input/ciphertext \ --plaintext-file=path/to/output/plaintext.dec To decrypt the file 'path/to/ciphertext' using the key frodo and the additional authenticated data that was used to encrypt the ciphertext, and write the decrypted plaintext to stdout, run: - $ gcloud beta kms decrypt \ - --key=frodo \ - --keyring=fellowship \ + $ gcloud beta kms decrypt --key=frodo --keyring=fellowship \ --location=global \ --additional-authenticated-data-file=path/to/aad \ - --ciphertext-file=path/to/input/ciphertext \ - --plaintext-file='-' + --ciphertext-file=path/to/input/ciphertext --plaintext-file='-' REQUIRED FLAGS --ciphertext-file=CIPHERTEXT_FILE diff --git a/gcloud/beta/kms/ekm-connections/add-iam-policy-binding b/gcloud/beta/kms/ekm-connections/add-iam-policy-binding index 4aef95305..718ce8ca7 100644 --- a/gcloud/beta/kms/ekm-connections/add-iam-policy-binding +++ b/gcloud/beta/kms/ekm-connections/add-iam-policy-binding @@ -133,8 +133,10 @@ API REFERENCE can be found at: https://cloud.google.com/kms/ 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 kms ekm-connections add-iam-policy-binding $ gcloud alpha kms ekm-connections add-iam-policy-binding diff --git a/gcloud/beta/kms/ekm-connections/create b/gcloud/beta/kms/ekm-connections/create index a978befa1..542a06ffc 100644 --- a/gcloud/beta/kms/ekm-connections/create +++ b/gcloud/beta/kms/ekm-connections/create @@ -16,10 +16,8 @@ EXAMPLES location us-central1: $ gcloud beta kms ekm-connections create laplace \ - --location=us-central1 \ - --service-directory-service="foo" \ - --endpoint-filter="foo > bar" \ - --hostname="hostname.foo" \ + --location=us-central1 --service-directory-service="foo" \ + --endpoint-filter="foo > bar" --hostname="hostname.foo" \ --server-certificates-files=foo.pem,bar.pem POSITIONAL ARGUMENTS @@ -75,8 +73,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud kms ekm-connections create $ gcloud alpha kms ekm-connections create diff --git a/gcloud/beta/kms/ekm-connections/describe b/gcloud/beta/kms/ekm-connections/describe index 8f13fd05d..d48a1ba10 100644 --- a/gcloud/beta/kms/ekm-connections/describe +++ b/gcloud/beta/kms/ekm-connections/describe @@ -51,8 +51,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 kms ekm-connections describe $ gcloud alpha kms ekm-connections describe diff --git a/gcloud/beta/kms/ekm-connections/get-iam-policy b/gcloud/beta/kms/ekm-connections/get-iam-policy index 1da65e8c2..6475c082b 100644 --- a/gcloud/beta/kms/ekm-connections/get-iam-policy +++ b/gcloud/beta/kms/ekm-connections/get-iam-policy @@ -87,8 +87,10 @@ API REFERENCE can be found at: https://cloud.google.com/kms/ 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 kms ekm-connections get-iam-policy $ gcloud alpha kms ekm-connections get-iam-policy diff --git a/gcloud/beta/kms/ekm-connections/help b/gcloud/beta/kms/ekm-connections/help index c682d6e64..52b374f01 100644 --- a/gcloud/beta/kms/ekm-connections/help +++ b/gcloud/beta/kms/ekm-connections/help @@ -41,8 +41,10 @@ COMMANDS (BETA) Update an ekmconnection. 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 kms ekm-connections $ gcloud alpha kms ekm-connections diff --git a/gcloud/beta/kms/ekm-connections/list b/gcloud/beta/kms/ekm-connections/list index 073027339..6ffd37d09 100644 --- a/gcloud/beta/kms/ekm-connections/list +++ b/gcloud/beta/kms/ekm-connections/list @@ -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 kms ekm-connections list $ gcloud alpha kms ekm-connections list diff --git a/gcloud/beta/kms/ekm-connections/remove-iam-policy-binding b/gcloud/beta/kms/ekm-connections/remove-iam-policy-binding index c1d6264fb..f5a9fa158 100644 --- a/gcloud/beta/kms/ekm-connections/remove-iam-policy-binding +++ b/gcloud/beta/kms/ekm-connections/remove-iam-policy-binding @@ -150,8 +150,10 @@ API REFERENCE can be found at: https://cloud.google.com/kms/ 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 kms ekm-connections remove-iam-policy-binding $ gcloud alpha kms ekm-connections remove-iam-policy-binding diff --git a/gcloud/beta/kms/ekm-connections/set-iam-policy b/gcloud/beta/kms/ekm-connections/set-iam-policy index e1d8f6d26..7faf929bb 100644 --- a/gcloud/beta/kms/ekm-connections/set-iam-policy +++ b/gcloud/beta/kms/ekm-connections/set-iam-policy @@ -72,8 +72,10 @@ API REFERENCE can be found at: https://cloud.google.com/kms/ 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 kms ekm-connections set-iam-policy $ gcloud alpha kms ekm-connections set-iam-policy diff --git a/gcloud/beta/kms/ekm-connections/update b/gcloud/beta/kms/ekm-connections/update index c4363f82c..36e7b3671 100644 --- a/gcloud/beta/kms/ekm-connections/update +++ b/gcloud/beta/kms/ekm-connections/update @@ -19,18 +19,15 @@ EXAMPLES resolver's hostname within location us-east1: $ gcloud beta kms ekm-connections update laplace \ - --location=us-east1 \ - --hostname=newhostname.foo \ + --location=us-east1 --hostname=newhostname.foo \ The following command updates an ekm-connection named laplace service resolver's service_directory_service, endpoint_filter, hostname, and server_certificates within location us-east1: $ gcloud beta kms ekm-connections update laplace \ - --location=us-east1 \ - --service-directory-service="foo" \ - --endpoint-filter="foo > bar" \ - --hostname="newhostname.foo" \ + --location=us-east1 --service-directory-service="foo" \ + --endpoint-filter="foo > bar" --hostname="newhostname.foo" \ --server-certificates-files=foo.pem,bar.pem POSITIONAL ARGUMENTS @@ -85,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 kms ekm-connections update $ gcloud alpha kms ekm-connections update diff --git a/gcloud/beta/kms/encrypt b/gcloud/beta/kms/encrypt index 9f8f48d5e..cd53f33c5 100644 --- a/gcloud/beta/kms/encrypt +++ b/gcloud/beta/kms/encrypt @@ -33,11 +33,8 @@ EXAMPLES using the CryptoKey frodo with the KeyRing fellowship and Location global, and write the ciphertext to 'path/to/ciphertext'. - $ gcloud beta kms encrypt \ - --key=frodo \ - --keyring=fellowship \ - --location=global \ - --plaintext-file=path/to/input/plaintext \ + $ gcloud beta kms encrypt --key=frodo --keyring=fellowship \ + --location=global --plaintext-file=path/to/input/plaintext \ --ciphertext-file=path/to/output/ciphertext REQUIRED FLAGS diff --git a/gcloud/beta/kms/import-jobs/create b/gcloud/beta/kms/import-jobs/create index 202913464..b49fb710f 100644 --- a/gcloud/beta/kms/import-jobs/create +++ b/gcloud/beta/kms/import-jobs/create @@ -13,8 +13,9 @@ EXAMPLES The following command creates a new import job named 'strider' within the 'fellowship' keyring, and 'us-central1' location: - $ gcloud beta kms import-jobs create strider --location=us-central1 \ - --keyring=fellowship --import-method=rsa-oaep-3072-sha1-aes-256 \ + $ gcloud beta kms import-jobs create strider \ + --location=us-central1 --keyring=fellowship \ + --import-method=rsa-oaep-3072-sha1-aes-256 \ --protection-level=hsm POSITIONAL ARGUMENTS diff --git a/gcloud/beta/kms/keys/create b/gcloud/beta/kms/keys/create index 36ad80a6d..396a58386 100644 --- a/gcloud/beta/kms/keys/create +++ b/gcloud/beta/kms/keys/create @@ -57,75 +57,59 @@ EXAMPLES The following command creates a key named frodo with protection level software within the keyring fellowship and location us-east1: - $ gcloud beta kms keys create frodo \ - --location=us-east1 \ - --keyring=fellowship \ - --purpose=encryption + $ gcloud beta kms keys create frodo --location=us-east1 \ + --keyring=fellowship --purpose=encryption The following command creates a key named strider with protection level software within the keyring rangers and location global with a specified rotation schedule: - $ gcloud beta kms keys create strider \ - --location=global --keyring=rangers \ - --purpose=encryption \ - --rotation-period=30d \ + $ gcloud beta kms keys create strider --location=global \ + --keyring=rangers --purpose=encryption --rotation-period=30d \ --next-rotation-time=2017-10-12T12:34:56.1234Z The following command creates a key named foo with protection level software within the keyring fellowship and location us-east1 with two specified labels: - $ gcloud beta kms keys create foo \ - --location=us-east1 \ - --keyring=fellowship \ - --purpose=encryption \ + $ gcloud beta kms keys create foo --location=us-east1 \ + --keyring=fellowship --purpose=encryption \ --labels=env=prod,team=kms The following command creates an asymmetric key named samwise with protection level software and default algorithm ec-sign-p256-sha256 within the keyring fellowship and location us-east1: - $ gcloud beta kms keys create samwise \ - --location=us-east1 \ - --keyring=fellowship \ - --purpose=asymmetric-signing \ + $ gcloud beta kms keys create samwise --location=us-east1 \ + --keyring=fellowship --purpose=asymmetric-signing \ --default-algorithm=ec-sign-p256-sha256 The following command creates a key named gimli with protection level hsm and default algorithm google-symmetric-encryption within the keyring fellowship and location us-east1: - $ gcloud beta kms keys create gimli \ - --location=us-east1 \ - --keyring=fellowship \ - --purpose=encryption \ - --protection-level=hsm + $ gcloud beta kms keys create gimli --location=us-east1 \ + --keyring=fellowship --purpose=encryption --protection-level=hsm The following command creates a key named legolas with protection level external and default algorithm external-symmetric-encryption within the keyring fellowship and location us-central1: - $ gcloud beta kms keys create legolas \ - --location=us-central1 \ - --keyring=fellowship \ - --purpose=encryption \ + $ gcloud beta kms keys create legolas --location=us-central1 \ + --keyring=fellowship --purpose=encryption \ --default-algorithm=external-symmetric-encryption \ - --protection-level=external - --skip-initial-version-creation + --protection-level=external --skip-initial-version-creation The following command creates a key named bilbo with protection level external-vpc and default algorithm external-symmetric-encryption and an EkmConnection of eagles within the keyring fellowship and location us-central1: - $ gcloud beta kms keys create bilbo \ - --location=us-central1 \ - --keyring=fellowship \ - --purpose=encryption \ + $ gcloud beta kms keys create bilbo --location=us-central1 \ + --keyring=fellowship --purpose=encryption \ --default-algorithm=external-symmetric-encryption \ - --protection-level=external-vpc - --skip-initial-version-creation + --protection-level=external-vpc \ + --skip-initial-version-creation \ --crypto-key-backend="projects/$(gcloud config get project)/ locations/us-central1/ekmConnections/eagles" diff --git a/gcloud/beta/kms/keys/remove-rotation-schedule b/gcloud/beta/kms/keys/remove-rotation-schedule index da63f012d..32e62cb0d 100644 --- a/gcloud/beta/kms/keys/remove-rotation-schedule +++ b/gcloud/beta/kms/keys/remove-rotation-schedule @@ -14,8 +14,7 @@ EXAMPLES within the keyring fellowship and location global: $ gcloud beta kms keys remove-rotation-schedule frodo \ - --location=global \ - --keyring=fellowship + --location=global --keyring=fellowship POSITIONAL ARGUMENTS KEY diff --git a/gcloud/beta/kms/keys/set-rotation-schedule b/gcloud/beta/kms/keys/set-rotation-schedule index a8c757cfc..68dde46bb 100644 --- a/gcloud/beta/kms/keys/set-rotation-schedule +++ b/gcloud/beta/kms/keys/set-rotation-schedule @@ -25,9 +25,7 @@ EXAMPLES time: $ gcloud beta kms keys set-rotation-schedule frodo \ - --location=global \ - --keyring=fellowship \ - --rotation-period=30d \ + --location=global --keyring=fellowship --rotation-period=30d \ --next-rotation-time=2017-10-12T12:34:56.1234Z POSITIONAL ARGUMENTS diff --git a/gcloud/beta/kms/keys/update b/gcloud/beta/kms/keys/update index e8a43c2e6..95e3349c1 100644 --- a/gcloud/beta/kms/keys/update +++ b/gcloud/beta/kms/keys/update @@ -36,52 +36,41 @@ EXAMPLES within the keyring fellowship and location global starting at the specified time: - $ gcloud beta kms keys update frodo \ - --location=global \ - --keyring=fellowship \ - --rotation-period=30d \ + $ gcloud beta kms keys update frodo --location=global \ + --keyring=fellowship --rotation-period=30d \ --next-rotation-time=2017-10-12T12:34:56.1234Z The following command removes the rotation schedule for the key named frodo within the keyring fellowship and location global: - $ gcloud beta kms keys update frodo \ - --location=global \ - --keyring=fellowship \ - --remove-rotation-schedule + $ gcloud beta kms keys update frodo --location=global \ + --keyring=fellowship --remove-rotation-schedule The following command updates the labels value for the key named frodo within the keyring fellowship and location global. If the label key does not exist at the time, it will be added: - $ gcloud beta kms keys update frodo \ - --location=global \ - --keyring=fellowship \ - --update-labels=k1=v1 + $ gcloud beta kms keys update frodo --location=global \ + --keyring=fellowship --update-labels=k1=v1 The following command removes labels k1 and k2 from the key named frodo within the keyring fellowship and location global: - $ gcloud beta kms keys update frodo \ - --location=global \ - --keyring=fellowship \ - --remove-labels=k1,k2 + $ gcloud beta kms keys update frodo --location=global \ + --keyring=fellowship --remove-labels=k1,k2 The following command updates the primary version for the key named frodo within the keyring fellowship and location global: - $ gcloud beta kms keys update frodo \ - --location=global \ - --keyring=fellowship \ - --primary-version=1 + $ gcloud beta kms keys update frodo --location=global \ + --keyring=fellowship --primary-version=1 The following command updates the default algorithm for the key named frodo within the keyring fellowship and location global, assuming the key originally has purpose 'asymmetric-encryption' and algorithm 'rsa-decrypt-oaep-2048-sha256': - $ gcloud beta kms keys update frodo \ - --location=global \ + $ gcloud beta kms keys update frodo --location=global \ --keyring=fellowship \ --default-algorithm=rsa-decrypt-oaep-4096-sha256 diff --git a/gcloud/beta/kms/keys/versions/create b/gcloud/beta/kms/keys/versions/create index 802957824..a9eb96436 100644 --- a/gcloud/beta/kms/keys/versions/create +++ b/gcloud/beta/kms/keys/versions/create @@ -15,8 +15,7 @@ EXAMPLES fellowship keyring, and global location and sets it as the primary version: $ gcloud beta kms keys versions create --location=global \ - --keyring=fellowship \ - --key=frodo --primary + --keyring=fellowship --key=frodo --primary The following command creates a new version within the legolas key, fellowship keyring, us-central1 location, @@ -24,8 +23,7 @@ EXAMPLES and sets it as the key's primary version: $ gcloud beta kms keys versions create --location=us-central1 \ - --keyring=fellowship \ - --key=legolas \ + --keyring=fellowship --key=legolas \ --external-key-uri=https://example.kms/v0/some/key/path \ --primary @@ -35,10 +33,8 @@ EXAMPLES version: $ gcloud beta kms keys versions create --location=us-central1 \ - --keyring=fellowship \ - --key=bilbo \ - --ekm-connection-key-path=v0/some/key/path \ - --primary + --keyring=fellowship --key=bilbo \ + --ekm-connection-key-path=v0/some/key/path --primary FLAGS --ekm-connection-key-path=EKM_CONNECTION_KEY_PATH diff --git a/gcloud/beta/kms/keys/versions/get-public-key b/gcloud/beta/kms/keys/versions/get-public-key index fc58d6142..79e5376a7 100644 --- a/gcloud/beta/kms/keys/versions/get-public-key +++ b/gcloud/beta/kms/keys/versions/get-public-key @@ -18,11 +18,9 @@ EXAMPLES The following command saves the public key for CryptoKey frodo Version 2 to '/tmp/my/pem.file': - $ gcloud beta kms keys versions get-public-key 2 \ - --key=frodo \ - --keyring=fellowship \ - --location=us-east1 \ - --output-file=/tmp/my/pem.file + $ gcloud beta kms keys versions get-public-key 2 --key=frodo \ + --keyring=fellowship --location=us-east1 \ + --output-file=/tmp/my/pem.file POSITIONAL ARGUMENTS VERSION diff --git a/gcloud/beta/kms/keys/versions/import b/gcloud/beta/kms/keys/versions/import index c6b785545..ab0e00cce 100644 --- a/gcloud/beta/kms/keys/versions/import +++ b/gcloud/beta/kms/keys/versions/import @@ -23,11 +23,9 @@ EXAMPLES the provided key material. $ gcloud beta kms keys versions import --location=global \ - --keyring=fellowship \ - --key=frodo \ - --import-job=strider \ - --rsa-aes-wrapped-key-file=path/to/target/key \ - --algorithm=google-symmetric-encryption + --keyring=fellowship --key=frodo --import-job=strider \ + --rsa-aes-wrapped-key-file=path/to/target/key \ + --algorithm=google-symmetric-encryption REQUIRED FLAGS --algorithm=ALGORITHM diff --git a/gcloud/beta/kms/keys/versions/list b/gcloud/beta/kms/keys/versions/list index 823ecd2be..8afde6228 100644 --- a/gcloud/beta/kms/keys/versions/list +++ b/gcloud/beta/kms/keys/versions/list @@ -15,8 +15,7 @@ EXAMPLES fellowship, and location global: $ gcloud beta kms keys versions list --location=global \ - --keyring=fellowship \ - --key=frodo + --keyring=fellowship --key=frodo FLAGS --key=KEY diff --git a/gcloud/beta/kms/keys/versions/update b/gcloud/beta/kms/keys/versions/update index b717855be..bb01ca1b3 100644 --- a/gcloud/beta/kms/keys/versions/update +++ b/gcloud/beta/kms/keys/versions/update @@ -19,33 +19,27 @@ EXAMPLES fellowship and location us-east1: $ gcloud beta kms keys versions update 8 --location=us-east1 \ - --keyring=fellowship \ - --key=frodo \ - --state=enabled + --keyring=fellowship --key=frodo --state=enabled The following command disables the key version 8 of key frodo within keyring fellowship and location us-east1: $ gcloud beta kms keys versions update 8 --location=us-east1 \ - --keyring=fellowship \ - --key=frodo \ - --state=disabled + --keyring=fellowship --key=frodo --state=disabled The following command updates the external key URI of version 8 of key frodo within keyring fellowship and location us-east1: $ gcloud beta kms keys versions update 8 --location=us-east1 \ - --keyring=fellowship \ - --key=frodo \ - --external-key-uri=https://example.kms/v0/some/key/path + --keyring=fellowship --key=frodo \ + --external-key-uri=https://example.kms/v0/some/key/path The following command updates the ekm connection key path of version 8 of key bilbo within keyring fellowship and location us-east1: $ gcloud beta kms keys versions update 8 --location=us-east1 \ - --keyring=fellowship \ - --key=bilbo \ - --ekm-connection-key-path=v0/some/key/path + --keyring=fellowship --key=bilbo \ + --ekm-connection-key-path=v0/some/key/path POSITIONAL ARGUMENTS VERSION diff --git a/gcloud/beta/kms/mac-sign b/gcloud/beta/kms/mac-sign index 21a93a9ec..003e30020 100644 --- a/gcloud/beta/kms/mac-sign +++ b/gcloud/beta/kms/mac-sign @@ -22,13 +22,10 @@ EXAMPLES it using the symmetric MAC CryptoKey dont-panic Version 3, and save the signature in base64 format to '/tmp/my/signature'. - $ gcloud beta kms mac-sign \ - --location=us-central1 \ - --keyring=hitchhiker \ - --key=dont-panic \ - --version=3 \ - --input-file=/tmp/my/file.to.sign \ - --signature-file=/tmp/my/signature + $ gcloud beta kms mac-sign --location=us-central1 \ + --keyring=hitchhiker --key=dont-panic --version=3 \ + --input-file=/tmp/my/file.to.sign \ + --signature-file=/tmp/my/signature REQUIRED FLAGS --input-file=INPUT_FILE diff --git a/gcloud/beta/kms/mac-verify b/gcloud/beta/kms/mac-verify index c95b556cf..40ac28abc 100644 --- a/gcloud/beta/kms/mac-verify +++ b/gcloud/beta/kms/mac-verify @@ -22,13 +22,10 @@ EXAMPLES file used previously to generate the MAC tag ('/tmp/my/original.data.file'). - $ gcloud beta kms mac-verify \ - --location=us-central1 \ - --keyring=hitchhiker \ - --key=dont-panic \ - --version=3 \ - --input-file=/tmp/my/original.data.file \ - --signature-file=/tmp/my/file.to.verify + $ gcloud beta kms mac-verify --location=us-central1 \ + --keyring=hitchhiker --key=dont-panic --version=3 \ + --input-file=/tmp/my/original.data.file \ + --signature-file=/tmp/my/file.to.verify REQUIRED FLAGS --input-file=INPUT_FILE diff --git a/gcloud/beta/lifesciences/pipelines/run b/gcloud/beta/lifesciences/pipelines/run index e409b0bb3..852a83642 100644 --- a/gcloud/beta/lifesciences/pipelines/run +++ b/gcloud/beta/lifesciences/pipelines/run @@ -142,8 +142,9 @@ OTHER FLAGS 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 to run the pipeline. If unspecified, defaults - to the Compute Engine service account for your project. + 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 diff --git a/gcloud/beta/logging/sinks/create b/gcloud/beta/logging/sinks/create index 2dd73bb10..6894fb782 100644 --- a/gcloud/beta/logging/sinks/create +++ b/gcloud/beta/logging/sinks/create @@ -38,8 +38,9 @@ DESCRIPTION EXAMPLES To route all Google Compute Engine logs to BigQuery, run: - $ gcloud beta logging sinks create my-bq-sink - bigquery.googleapis.com/projects/my-project/datasets/my_dataset --log-filter='resource.type="gce_instance"' + $ gcloud beta logging sinks create my-bq-sink \ + bigquery.googleapis.com/projects/my-project/datasets/\ + my_dataset --log-filter='resource.type="gce_instance"' To route "syslog" from App Engine Flexible to a Cloud Storage bucket, run: @@ -50,13 +51,15 @@ EXAMPLES To route Google App Engine logs with ERROR severity, run: - $ gcloud beta logging sinks create my-error-logs - bigquery.googleapis.com/projects/my-project/datasets/my_dataset --log-filter='resource.type="gae_app" AND severity=ERROR' + $ gcloud beta logging sinks create my-error-logs \ + bigquery.googleapis.com/projects/my-project/datasets/\ + my_dataset --log-filter='resource.type="gae_app" AND severity=ERROR' To route all logs to a log bucket in a different project, run: - $ gcloud beta logging sinks create my-sink - logging.googleapis.com/projects/my-central-project/locations/global/buckets/my-central-bucket + $ gcloud beta logging sinks create my-sink \ + logging.googleapis.com/projects/my-central-project/locations/\ + global/buckets/my-central-bucket POSITIONAL ARGUMENTS SINK_NAME diff --git a/gcloud/beta/logging/views/update b/gcloud/beta/logging/views/update index 25683eff8..277d294d1 100644 --- a/gcloud/beta/logging/views/update +++ b/gcloud/beta/logging/views/update @@ -16,8 +16,7 @@ EXAMPLES To update a view in your project, run: $ gcloud beta logging views update my-view --bucket=my-bucket \ - --location=global - --description=my-new-description + --location=global --description=my-new-description POSITIONAL ARGUMENTS VIEW_ID diff --git a/gcloud/beta/memcache/instances/create b/gcloud/beta/memcache/instances/create index f99226436..a69eaee05 100644 --- a/gcloud/beta/memcache/instances/create +++ b/gcloud/beta/memcache/instances/create @@ -23,8 +23,8 @@ EXAMPLES 'us-central1' with 3 nodes, each with 2 CPUs and 2GB of memory, run: $ gcloud beta memcache instances create my-memcache-instance \ - --region=us-central1 \ - --node-count=3 --node-cpu=2 --node-memory=2GB + --region=us-central1 --node-count=3 --node-cpu=2 \ + --node-memory=2GB POSITIONAL ARGUMENTS Instance resource - Arguments and flags that specify the Memcached diff --git a/gcloud/beta/metastore/services/import/gcs b/gcloud/beta/metastore/services/import/gcs index 4c95a7138..75d885aea 100644 --- a/gcloud/beta/metastore/services/import/gcs +++ b/gcloud/beta/metastore/services/import/gcs @@ -24,7 +24,7 @@ EXAMPLES $ gcloud beta metastore services import gcs my-service \ --import-id=my-import --description='testing description' \ - --dump-type=mysql --database-dump=gs://database-dump + --dump-type=mysql --database-dump=gs://database-dump POSITIONAL ARGUMENTS Service resource - Arguments and flags that specify the Dataproc Metastore diff --git a/gcloud/beta/metastore/services/imports/create b/gcloud/beta/metastore/services/imports/create index a71d3f268..890d24582 100644 --- a/gcloud/beta/metastore/services/imports/create +++ b/gcloud/beta/metastore/services/imports/create @@ -23,7 +23,7 @@ EXAMPLES $ gcloud beta metastore services imports create my-import \ --service=my-service --description='testing description' \ - --database-type=mysql --database-dump=gs://database-dump + --database-type=mysql --database-dump=gs://database-dump POSITIONAL ARGUMENTS Import resource - Arguments and flags that specify the metadata import you diff --git a/gcloud/beta/ml-engine/explain b/gcloud/beta/ml-engine/explain index ddcf400cd..4d349843e 100644 --- a/gcloud/beta/ml-engine/explain +++ b/gcloud/beta/ml-engine/explain @@ -18,7 +18,7 @@ EXAMPLES 'version' and with the name 'model-name', run: $ gcloud beta ml-engine explain explain --model=model-name \ - --version=version --json-instances=instances.json + --version=version --json-instances=instances.json REQUIRED FLAGS --model=MODEL diff --git a/gcloud/beta/ml-engine/models/delete b/gcloud/beta/ml-engine/models/delete index b74af0582..c8739a603 100644 --- a/gcloud/beta/ml-engine/models/delete +++ b/gcloud/beta/ml-engine/models/delete @@ -9,8 +9,8 @@ EXAMPLES To delete all models matching the regular expression vision[0-9]+, run: $ gcloud beta ml-engine models list --uri \ - --filter 'name ~ vision[0-9]+' | - xargs -n 1 gcloud beta ml-engine models delete + --filter 'name ~ vision[0-9]+' | xargs -n 1 gcloud beta \ + ml-engine models delete POSITIONAL ARGUMENTS MODEL diff --git a/gcloud/beta/ml/language/classify-text b/gcloud/beta/ml/language/classify-text index 11e1dcefc..7cfa9958f 100644 --- a/gcloud/beta/ml/language/classify-text +++ b/gcloud/beta/ml/language/classify-text @@ -32,7 +32,7 @@ EXAMPLES $ gcloud beta ml language classify-text \ --content-file='gs://bucket_name/mycontent.html' \ - --content-type=HTML --language=ja-JP + --content-type=HTML --language=ja-JP REQUIRED FLAGS Exactly one of these must be specified: diff --git a/gcloud/beta/ml/speech/recognize b/gcloud/beta/ml/speech/recognize index 60a253922..fb473c62a 100644 --- a/gcloud/beta/ml/speech/recognize +++ b/gcloud/beta/ml/speech/recognize @@ -36,8 +36,8 @@ EXAMPLES custom sampling rate and encoding that uses hints and filters profanity: $ gcloud beta ml speech recognize 'gs://bucket/myaudio' \ - --language-code=es-ES --sample-rate=2200 --hints=Bueno \ - --encoding=OGG_OPUS --filter-profanity + --language-code=es-ES --sample-rate=2200 --hints=Bueno \ + --encoding=OGG_OPUS --filter-profanity POSITIONAL ARGUMENTS AUDIO @@ -111,6 +111,12 @@ OPTIONAL FLAGS audio that is not one of the specific audio models. For example, long-form audio. Ideally the audio is high-fidelity, recorded at a 16khz or greater sampling rate. + medical_conversation + Best for audio that originated from a conversation between a + medical provider and patient. + medical_dictation + Best for audio that originated from dictation notes by a medical + provider. phone_call audio that originated from a phone call (typically recorded at an 8khz sampling rate). diff --git a/gcloud/beta/ml/speech/recognize-long-running b/gcloud/beta/ml/speech/recognize-long-running index de0cf5bb7..34d4c4127 100644 --- a/gcloud/beta/ml/speech/recognize-long-running +++ b/gcloud/beta/ml/speech/recognize-long-running @@ -120,6 +120,12 @@ OPTIONAL FLAGS audio that is not one of the specific audio models. For example, long-form audio. Ideally the audio is high-fidelity, recorded at a 16khz or greater sampling rate. + medical_conversation + Best for audio that originated from a conversation between a + medical provider and patient. + medical_dictation + Best for audio that originated from dictation notes by a medical + provider. phone_call audio that originated from a phone call (typically recorded at an 8khz sampling rate). diff --git a/gcloud/beta/ml/vision/detect-text-pdf b/gcloud/beta/ml/vision/detect-text-pdf index 9221d3046..7e98c0119 100644 --- a/gcloud/beta/ml/vision/detect-text-pdf +++ b/gcloud/beta/ml/vision/detect-text-pdf @@ -19,8 +19,8 @@ EXAMPLES To detect text for input PDF file 'gs://my_bucket/input_file' and store output in 'gs://my_bucket/out_put_prefix': - $ gcloud beta ml vision detect-text-pdf gs://my_bucket/input_file - gs://my_bucket/out_put_prefix + $ gcloud beta ml vision detect-text-pdf gs://my_bucket/input_file \ + gs://my_bucket/out_put_prefix POSITIONAL ARGUMENTS INPUT_FILE diff --git a/gcloud/beta/ml/vision/detect-text-tiff b/gcloud/beta/ml/vision/detect-text-tiff index e16eef601..06e1a50ad 100644 --- a/gcloud/beta/ml/vision/detect-text-tiff +++ b/gcloud/beta/ml/vision/detect-text-tiff @@ -19,8 +19,8 @@ EXAMPLES To detect text for input TIFF file gs://my_bucket/input_file and store output in gs://my_bucket/out_put_prefix: - $ gcloud beta ml vision detect-text-tiff gs://my_bucket/input_file - gs://my_bucket/out_put_prefix + $ gcloud beta ml vision detect-text-tiff gs://my_bucket/input_file \ + gs://my_bucket/out_put_prefix POSITIONAL ARGUMENTS INPUT_FILE diff --git a/gcloud/beta/monitoring/channels/create b/gcloud/beta/monitoring/channels/create index 0119adf47..905ee32eb 100644 --- a/gcloud/beta/monitoring/channels/create +++ b/gcloud/beta/monitoring/channels/create @@ -34,18 +34,16 @@ EXAMPLES existing channels. It is also a best practice to supply at least two channels of different types for a given person. - $ gcloud beta monitoring channels create \ - --display-name="Foo Team Lead (Primary)" \ - --description="Primary contact method for the Foo team lead" \ - --type=email \ - --user-labels=team=foo,role=lead,ord=1 \ + $ gcloud beta monitoring channels create \ + --display-name="Foo Team Lead (Primary)" \ + --description="Primary contact method for the Foo team lead" \ + --type=email --user-labels=team=foo,role=lead,ord=1 \ --channel-labels=email_address=user@somedomain.tld - $ gcloud beta monitoring channels create \ - --display-name="Foo Team Lead (Secondary)" \ + $ gcloud beta monitoring channels create \ + --display-name="Foo Team Lead (Secondary)" \ --description="Secondary contact method for the Foo team lead" \ - --type=sms \ - --user-labels=team=foo,role=lead,ord=2 \ + --type=sms --user-labels=team=foo,role=lead,ord=2 \ --channel-labels=number=123-456-7890 FLAGS diff --git a/gcloud/beta/monitoring/channels/list b/gcloud/beta/monitoring/channels/list index efc2d4376..851492783 100644 --- a/gcloud/beta/monitoring/channels/list +++ b/gcloud/beta/monitoring/channels/list @@ -21,10 +21,9 @@ EXAMPLES The following command lists all of the email addresses alphabetically: - $ gcloud beta monitoring channels list \ - --filter='type="email"' \ - --sort-by=labels.email_address \ - --format="value(labels.email_address)" + $ gcloud beta monitoring channels list --filter='type="email"' \ + --sort-by=labels.email_address \ + --format="value(labels.email_address)" FLAGS --type=TYPE diff --git a/gcloud/beta/monitoring/channels/update b/gcloud/beta/monitoring/channels/update index 07af33dac..54b6f942a 100644 --- a/gcloud/beta/monitoring/channels/update +++ b/gcloud/beta/monitoring/channels/update @@ -36,7 +36,7 @@ EXAMPLES point from its original email address to "newaddress@newdomain.tld": $ gcloud beta monitoring channels update \ - "projects/12345/notificationChannels/67890" \ + "projects/12345/notificationChannels/67890" \ --update-channel-labels=email_address=newaddress@newdomain.tld POSITIONAL ARGUMENTS diff --git a/gcloud/beta/network-management/connectivity-tests/create b/gcloud/beta/network-management/connectivity-tests/create index d7d431f28..887c7fe55 100644 --- a/gcloud/beta/network-management/connectivity-tests/create +++ b/gcloud/beta/network-management/connectivity-tests/create @@ -29,8 +29,10 @@ EXAMPLES network. $ gcloud beta network-management connectivity-tests create my-test \ - --source-instance=projects/my-project/zones/us-west-1/instances/my-instance - --destination-ip-address=10.142.0.2 --destination-network=projects/my-project/global/networks/peering-network + --source-instance=projects/my-project/zones/us-west-1/\ + instances/my-instance --destination-ip-address=10.142.0.2 \ + --destination-network=projects/my-project/global/networks/\ + peering-network POSITIONAL ARGUMENTS Connectivity test resource - Name of the connectivity test you want to @@ -137,8 +139,7 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the networkmanagement/v1beta1 API. The full documentation - for this API can be found at: - http://g3doc/cloud/network/topology/boq/goa/nicbilling/server/README + for this API can be found at: https://cloud.google.com/ NOTES This command is currently in beta and might change without notice. This diff --git a/gcloud/beta/network-management/connectivity-tests/delete b/gcloud/beta/network-management/connectivity-tests/delete index 747c934f1..daf8c95cc 100644 --- a/gcloud/beta/network-management/connectivity-tests/delete +++ b/gcloud/beta/network-management/connectivity-tests/delete @@ -46,8 +46,7 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the networkmanagement/v1beta1 API. The full documentation - for this API can be found at: - http://g3doc/cloud/network/topology/boq/goa/nicbilling/server/README + for this API can be found at: https://cloud.google.com/ NOTES This command is currently in beta and might change without notice. This diff --git a/gcloud/beta/network-management/connectivity-tests/describe b/gcloud/beta/network-management/connectivity-tests/describe index 65d43a8b0..6a2735943 100644 --- a/gcloud/beta/network-management/connectivity-tests/describe +++ b/gcloud/beta/network-management/connectivity-tests/describe @@ -41,8 +41,7 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the networkmanagement/v1beta1 API. The full documentation - for this API can be found at: - http://g3doc/cloud/network/topology/boq/goa/nicbilling/server/README + for this API can be found at: https://cloud.google.com/ NOTES This command is currently in beta and might change without notice. This diff --git a/gcloud/beta/network-management/connectivity-tests/list b/gcloud/beta/network-management/connectivity-tests/list index 944afd97f..2ce197e53 100644 --- a/gcloud/beta/network-management/connectivity-tests/list +++ b/gcloud/beta/network-management/connectivity-tests/list @@ -54,8 +54,7 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the networkmanagement/v1beta1 API. The full documentation - for this API can be found at: - http://g3doc/cloud/network/topology/boq/goa/nicbilling/server/README + for this API can be found at: https://cloud.google.com/ NOTES This command is currently in beta and might change without notice. This diff --git a/gcloud/beta/network-management/connectivity-tests/rerun b/gcloud/beta/network-management/connectivity-tests/rerun index ffc2419b2..d74088915 100644 --- a/gcloud/beta/network-management/connectivity-tests/rerun +++ b/gcloud/beta/network-management/connectivity-tests/rerun @@ -46,8 +46,7 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the networkmanagement/v1beta1 API. The full documentation - for this API can be found at: - http://g3doc/cloud/network/topology/boq/goa/nicbilling/server/README + for this API can be found at: https://cloud.google.com/ NOTES This command is currently in beta and might change without notice. This diff --git a/gcloud/beta/network-management/connectivity-tests/update b/gcloud/beta/network-management/connectivity-tests/update index 8667672bd..aee967ff7 100644 --- a/gcloud/beta/network-management/connectivity-tests/update +++ b/gcloud/beta/network-management/connectivity-tests/update @@ -36,7 +36,8 @@ EXAMPLES modifying the description and destination IP address. $ gcloud beta network-management connectivity-tests update my-test \ - --description='update dst addr' --destination-ip-address='10.142.0.3' + --description='update dst addr' \ + --destination-ip-address='10.142.0.3' POSITIONAL ARGUMENTS Connectivity test resource - Name of the connectivity test you want to @@ -179,8 +180,7 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the networkmanagement/v1beta1 API. The full documentation - for this API can be found at: - http://g3doc/cloud/network/topology/boq/goa/nicbilling/server/README + for this API can be found at: https://cloud.google.com/ NOTES This command is currently in beta and might change without notice. This diff --git a/gcloud/beta/network-management/operations/describe b/gcloud/beta/network-management/operations/describe index b66aa2d1e..5a2b6d698 100644 --- a/gcloud/beta/network-management/operations/describe +++ b/gcloud/beta/network-management/operations/describe @@ -42,8 +42,7 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the networkmanagement/v1 API. The full documentation for - this API can be found at: - http://g3doc/cloud/network/topology/boq/goa/nicbilling/server/README + this API can be found at: https://cloud.google.com/ NOTES This command is currently in beta and might change without notice. This diff --git a/gcloud/beta/network-management/operations/list b/gcloud/beta/network-management/operations/list index 13b3b4c4c..36c653b2b 100644 --- a/gcloud/beta/network-management/operations/list +++ b/gcloud/beta/network-management/operations/list @@ -54,8 +54,7 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the networkmanagement/v1 API. The full documentation for - this API can be found at: - http://g3doc/cloud/network/topology/boq/goa/nicbilling/server/README + this API can be found at: https://cloud.google.com/ NOTES This command is currently in beta and might change without notice. This diff --git a/gcloud/beta/policy-troubleshoot/iam b/gcloud/beta/policy-troubleshoot/iam index caea22bc0..7142d729a 100644 --- a/gcloud/beta/policy-troubleshoot/iam +++ b/gcloud/beta/policy-troubleshoot/iam @@ -15,8 +15,8 @@ EXAMPLES $ gcloud beta policy-troubleshoot iam \ //cloudresourcemanager.googleapis.com/projects/project-id \ - --principal-email=my-iam-account@somedomain.com \ - --permission=resourcemanager.projects.get + --principal-email=my-iam-account@somedomain.com \ + --permission=resourcemanager.projects.get See https://cloud.google.com/iam/docs/policies for more information about IAM policies. diff --git a/gcloud/beta/privateca/certificates/create b/gcloud/beta/privateca/certificates/create index 160bb1926..0ce3b9aee 100644 --- a/gcloud/beta/privateca/certificates/create +++ b/gcloud/beta/privateca/certificates/create @@ -18,20 +18,15 @@ EXAMPLES To create a certificate using a CSR: $ gcloud beta privateca certificates create frontend-server-tls \ - --issuer=server-tls-1 --issuer-location=us \ - --csr=./csr.pem \ - --cert-output-file=./cert.pem \ - --validity=P30D + --issuer=server-tls-1 --issuer-location=us --csr=./csr.pem \ + --cert-output-file=./cert.pem --validity=P30D To create a certificate using a client-generated key: $ gcloud beta privateca certificates create frontend-server-tls \ - --issuer=server-tls-1 --issuer-location=us \ - --generate-key \ - --key-output-file=./key \ - --cert-output-file=./cert.pem \ - --dns-san=www.joonix.net \ - --reusable-config=server-tls + --issuer=server-tls-1 --issuer-location=us --generate-key \ + --key-output-file=./key --cert-output-file=./cert.pem \ + --dns-san=www.joonix.net --reusable-config=server-tls POSITIONAL ARGUMENTS CERTIFICATE resource - The name of the certificate to issue. If the diff --git a/gcloud/beta/privateca/certificates/describe b/gcloud/beta/privateca/certificates/describe index b81cb9c24..5a4ac1a14 100644 --- a/gcloud/beta/privateca/certificates/describe +++ b/gcloud/beta/privateca/certificates/describe @@ -14,14 +14,14 @@ EXAMPLES To get metadata for the 'frontend-server-tls' certificate: $ gcloud beta privateca certificates describe frontend-server-tls \ - --issuer=server-tls-1 --issuer-location=us-west1 + --issuer=server-tls-1 --issuer-location=us-west1 To download the PEM-encoded certificate for the 'frontend-server-tls' certificate to a file called 'frontend-server-tls.crt': $ gcloud beta privateca certificates describe frontend-server-tls \ - --issuer=server-tls-1 --issuer-location=us-west1 \ - --format="value(pem_cert)" > ./frontend-server-tls.crt + --issuer=server-tls-1 --issuer-location=us-west1 \ + --format="value(pem_cert)" > ./frontend-server-tls.crt POSITIONAL ARGUMENTS CERTIFICATE resource - The certificate for which to obtain metadata. The diff --git a/gcloud/beta/privateca/certificates/revoke b/gcloud/beta/privateca/certificates/revoke index f6734edae..46478c2b2 100644 --- a/gcloud/beta/privateca/certificates/revoke +++ b/gcloud/beta/privateca/certificates/revoke @@ -15,17 +15,16 @@ EXAMPLES To revoke the 'frontend-server-tls' certificate due to key compromise: $ gcloud beta privateca certificates revoke \ - --certificate=frontend-server-tls \ - --issuer=server-tls-1 --issuer-location=us-west1 \ - --reason=key_compromise + --certificate=frontend-server-tls --issuer=server-tls-1 \ + --issuer-location=us-west1 --reason=key_compromise To revoke the a certificate with the serial number '7dc1d9186372de2e1f4824abb1c4c9e5e43cbb40' due to a newer one being issued: $ gcloud beta privateca certificates revoke \ - --serial-number=7dc1d9186372de2e1f4824abb1c4c9e5e43cbb40 \ - --issuer=server-tls-1 --issuer-location=us-west1 \ - --reason=superseded + --serial-number=7dc1d9186372de2e1f4824abb1c4c9e5e43cbb40 \ + --issuer=server-tls-1 --issuer-location=us-west1 \ + --reason=superseded REQUIRED FLAGS The certificate identifier. diff --git a/gcloud/beta/privateca/certificates/update b/gcloud/beta/privateca/certificates/update index c74fd761c..7491dadbd 100644 --- a/gcloud/beta/privateca/certificates/update +++ b/gcloud/beta/privateca/certificates/update @@ -11,8 +11,8 @@ EXAMPLES To update labels on a certificate: $ gcloud beta privateca certificates update frontend-server-tls \ - --issuer=server-tls-1 --issuer-location=us \ - --update-labels=in_use=true + --issuer=server-tls-1 --issuer-location=us \ + --update-labels=in_use=true POSITIONAL ARGUMENTS CERTIFICATE resource - The certificate to update. The arguments in this diff --git a/gcloud/beta/privateca/roots/add-iam-policy-binding b/gcloud/beta/privateca/roots/add-iam-policy-binding index a62b2bf74..e4a1b383d 100644 --- a/gcloud/beta/privateca/roots/add-iam-policy-binding +++ b/gcloud/beta/privateca/roots/add-iam-policy-binding @@ -20,9 +20,8 @@ EXAMPLES the CA 'prod-root' with the location 'us-west1', run: $ gcloud beta privateca roots add-iam-policy-binding prod-root \ - --location='us-west1' \ - --member='user:test-user@gmail.com' \ - --role='roles/privateca.certificateManager' + --location='us-west1' --member='user:test-user@gmail.com' \ + --role='roles/privateca.certificateManager' POSITIONAL ARGUMENTS Certificate Authority resource - The certificate authority for which to diff --git a/gcloud/beta/privateca/roots/create b/gcloud/beta/privateca/roots/create index 28638bb9e..1eab89ecc 100644 --- a/gcloud/beta/privateca/roots/create +++ b/gcloud/beta/privateca/roots/create @@ -25,35 +25,34 @@ EXAMPLES To create a root CA that supports one layer of subordinates: $ gcloud beta privateca roots create prod-root \ - --kms-key-version="projects/joonix-pki/locations/us-west1/keyRings/kr1/cryptoKeys/k1/cryptoKeyVersions/1" - \ - --subject="CN=Joonix Production Root CA, O=Google" \ - --max-chain-length=1 + --kms-key-version="projects/joonix-pki/locations/us-west1/keyRin\ + gs/kr1/cryptoKeys/k1/cryptoKeyVersions/1" \ + --subject="CN=Joonix Production Root CA, O=Google" \ + --max-chain-length=1 To create a root CA and restrict what it can issue: $ gcloud beta privateca roots create prod-root \ - --kms-key-version="projects/joonix-pki/locations/us-west1/keyRings/kr1/cryptoKeys/k1/cryptoKeyVersions/1" - \ - --subject="CN=Joonix Production Root CA, O=Google" \ - --issuance-policy=policy.yaml + --kms-key-version="projects/joonix-pki/locations/us-west1/keyRin\ + gs/kr1/cryptoKeys/k1/cryptoKeyVersions/1" \ + --subject="CN=Joonix Production Root CA, O=Google" \ + --issuance-policy=policy.yaml To create a root CA that doesn't publicly publish CA certificate and CRLs: $ gcloud beta privateca roots create root-2 \ - --kms-key-version="projects/joonix-pki/locations/us-west1/keyRings/kr1/cryptoKeys/k1/cryptoKeyVersions/1" - \ - --subject="CN=Joonix Production Root CA, O=Google" \ - --issuance-policy=policy.yaml \ - --no-publish-ca-cert \ - --no-publish-crl + --kms-key-version="projects/joonix-pki/locations/us-west1/keyRin\ + gs/kr1/cryptoKeys/k1/cryptoKeyVersions/1" \ + --subject="CN=Joonix Production Root CA, O=Google" \ + --issuance-policy=policy.yaml --no-publish-ca-cert \ + --no-publish-crl To create a root CA that is based on an existing CA: $ gcloud beta privateca roots create prod-root \ - --kms-key-version="projects/joonix-pki/locations/us-west1/keyRings/kr1/cryptoKeys/k1/cryptoKeyVersions/1" - \ - --from-ca=source-root --from-ca-location=us-central1 + --kms-key-version="projects/joonix-pki/locations/us-west1/keyRin\ + gs/kr1/cryptoKeys/k1/cryptoKeyVersions/1" --from-ca=source-root \ + --from-ca-location=us-central1 POSITIONAL ARGUMENTS Certificate Authority resource - The name of the root CA to create. The diff --git a/gcloud/beta/privateca/roots/describe b/gcloud/beta/privateca/roots/describe index a03d02ea0..b8934d710 100644 --- a/gcloud/beta/privateca/roots/describe +++ b/gcloud/beta/privateca/roots/describe @@ -12,15 +12,13 @@ DESCRIPTION EXAMPLES To get metadata for the root CA 'prod-root' in location 'us-west1': - $ gcloud beta privateca roots describe server-tls-1 \ - --location=us + $ gcloud beta privateca roots describe server-tls-1 --location=us To download the PEM-encoded CA certificate for the 'prod-root' CA in location 'us-west1' to a file called 'prod-root.crt': $ gcloud beta privateca roots describe prod-root \ - --location=us-west1 \ - --format="value(pem_cert)" > ./prod-root.crt + --location=us-west1 --format="value(pem_cert)" > ./prod-root.crt POSITIONAL ARGUMENTS Certificate Authority resource - The certificate authority for which to diff --git a/gcloud/beta/privateca/roots/remove-iam-policy-binding b/gcloud/beta/privateca/roots/remove-iam-policy-binding index 37fe57adf..9e095f2b7 100644 --- a/gcloud/beta/privateca/roots/remove-iam-policy-binding +++ b/gcloud/beta/privateca/roots/remove-iam-policy-binding @@ -20,9 +20,8 @@ EXAMPLES the CA 'prod-root' with the location 'us-west1', run: $ gcloud beta privateca roots remove-iam-policy-binding prod-root \ - --location='us-west1' \ - --member='user:test-user@gmail.com' \ - --role='roles/privateca.certificateManager' + --location='us-west1' --member='user:test-user@gmail.com' \ + --role='roles/privateca.certificateManager' POSITIONAL ARGUMENTS Certificate Authority resource - The certificate authority for which to diff --git a/gcloud/beta/privateca/roots/update b/gcloud/beta/privateca/roots/update index 3a8ffbd1a..7b2057687 100644 --- a/gcloud/beta/privateca/roots/update +++ b/gcloud/beta/privateca/roots/update @@ -12,15 +12,13 @@ SYNOPSIS EXAMPLES To update labels on a root CA: - $ gcloud beta privateca roots update prod-root \ - --location=us-west1 \ - --update-labels=foo=bar + $ gcloud beta privateca roots update prod-root --location=us-west1 \ + --update-labels=foo=bar To disable publishing CRLs for a root CA: - $ gcloud beta privateca roots update prod-root \ - --location=us-west1 \ - --no-publish-crl + $ gcloud beta privateca roots update prod-root --location=us-west1 \ + --no-publish-crl POSITIONAL ARGUMENTS CERTIFICATE AUTHORITY resource - The certificate authority to update. The diff --git a/gcloud/beta/privateca/subordinates/activate b/gcloud/beta/privateca/subordinates/activate index b978cf995..8d591da73 100644 --- a/gcloud/beta/privateca/subordinates/activate +++ b/gcloud/beta/privateca/subordinates/activate @@ -12,8 +12,7 @@ EXAMPLES using a PEM certificate chain in 'chain.crt': $ gcloud beta privateca subordinates activate server-tls-1 \ - --location=us \ - --pem-chain=./chain.crt + --location=us --pem-chain=./chain.crt POSITIONAL ARGUMENTS CERTIFICATE AUTHORITY resource - The certificate authority to activate. diff --git a/gcloud/beta/privateca/subordinates/add-iam-policy-binding b/gcloud/beta/privateca/subordinates/add-iam-policy-binding index b31b02eb1..805860d48 100644 --- a/gcloud/beta/privateca/subordinates/add-iam-policy-binding +++ b/gcloud/beta/privateca/subordinates/add-iam-policy-binding @@ -20,10 +20,9 @@ EXAMPLES the CA 'server-tls-1' with the location 'us-west1', run: $ gcloud beta privateca subordinates add-iam-policy-binding \ - server-tls-1 \ - --location='us-west1' \ - --member='user:test-user@gmail.com' \ - --role='roles/privateca.certificateManager' + server-tls-1 --location='us-west1' \ + --member='user:test-user@gmail.com' \ + --role='roles/privateca.certificateManager' POSITIONAL ARGUMENTS Certificate Authority resource - The certificate authority for which to diff --git a/gcloud/beta/privateca/subordinates/create b/gcloud/beta/privateca/subordinates/create index 326e99dea..8c77e52be 100644 --- a/gcloud/beta/privateca/subordinates/create +++ b/gcloud/beta/privateca/subordinates/create @@ -29,26 +29,28 @@ EXAMPLES CA: $ gcloud beta privateca subordinates create server-tls-1 \ - --subject="CN=Joonix TLS CA, O=Google" \ - --issuer=prod-root --issuer-location=us-west1 \ - --kms-key-version="projects/joonix-pki/locations/us-west1/keyRings/kr1/cryptoKeys/key2/cryptoKeyVersions/1" + --subject="CN=Joonix TLS CA, O=Google" --issuer=prod-root \ + --issuer-location=us-west1 \ + --kms-key-version="projects/joonix-pki/locations/us-west1/keyRin\ + gs/kr1/cryptoKeys/key2/cryptoKeyVersions/1" To create a subordinate CA named 'server-tls-1' whose issuer is located elsewhere: $ gcloud beta privateca subordinates create server-tls-1 \ - --subject="CN=Joonix TLS CA, O=Google" \ - --create-csr \ - --csr-output-file="./csr.pem" \ - --kms-key-version="projects/joonix-pki/locations/us-west1/keyRings/kr1/cryptoKeys/key2/cryptoKeyVersions/1" + --subject="CN=Joonix TLS CA, O=Google" --create-csr \ + --csr-output-file="./csr.pem" \ + --kms-key-version="projects/joonix-pki/locations/us-west1/keyRin\ + gs/kr1/cryptoKeys/key2/cryptoKeyVersions/1" To create a subordinate CA named 'server-tls-1' chaining up to a root CA named 'prod-root' based on an existing CA: $ gcloud beta privateca subordinates create server-tls-1 \ - --issuer=prod-root --issuer-location=us-west1 \ - --from-ca=source-ca --from-ca-location=us-central1 \ - --kms-key-version="projects/joonix-pki/locations/us-west1/keyRings/kr1/cryptoKeys/key2/cryptoKeyVersions/1" + --issuer=prod-root --issuer-location=us-west1 \ + --from-ca=source-ca --from-ca-location=us-central1 \ + --kms-key-version="projects/joonix-pki/locations/us-west1/keyRin\ + gs/kr1/cryptoKeys/key2/cryptoKeyVersions/1" POSITIONAL ARGUMENTS Certificate Authority resource - The name of the subordinate CA to create. diff --git a/gcloud/beta/privateca/subordinates/describe b/gcloud/beta/privateca/subordinates/describe index 6c27576f4..52bef97d7 100644 --- a/gcloud/beta/privateca/subordinates/describe +++ b/gcloud/beta/privateca/subordinates/describe @@ -14,14 +14,14 @@ EXAMPLES 'us-west1': $ gcloud beta privateca subordinates describe server-tls-1 \ - --location=us-west1 + --location=us-west1 To download the PEM-encoded CA certificate for the 'server-tls-1' CA in location 'us-west1' to a file called 'server-tls-1.crt': $ gcloud beta privateca subordinates describe server-tls-1 \ - --location=us-west1 \ - --format="value(pem_cert)" > ./server-tls-1.crt + --location=us-west1 --format="value(pem_cert)" > \ + ./server-tls-1.crt POSITIONAL ARGUMENTS Certificate Authority resource - The certificate authority for which to diff --git a/gcloud/beta/privateca/subordinates/remove-iam-policy-binding b/gcloud/beta/privateca/subordinates/remove-iam-policy-binding index 6f9830d03..a8c00c658 100644 --- a/gcloud/beta/privateca/subordinates/remove-iam-policy-binding +++ b/gcloud/beta/privateca/subordinates/remove-iam-policy-binding @@ -20,10 +20,9 @@ EXAMPLES the CA 'server-tls-1' with the location 'us-west1', run: $ gcloud beta privateca subordinates remove-iam-policy-binding \ - server-tls-1 \ - --location='us-west1' \ - --member='user:test-user@gmail.com' \ - --role='roles/privateca.certificateManager' + server-tls-1 --location='us-west1' \ + --member='user:test-user@gmail.com' \ + --role='roles/privateca.certificateManager' POSITIONAL ARGUMENTS Certificate Authority resource - The certificate authority for which to diff --git a/gcloud/beta/privateca/subordinates/update b/gcloud/beta/privateca/subordinates/update index 6b2c3a4d0..0b401eda0 100644 --- a/gcloud/beta/privateca/subordinates/update +++ b/gcloud/beta/privateca/subordinates/update @@ -14,14 +14,12 @@ EXAMPLES To update labels on a subordinate CA: $ gcloud beta privateca subordinates update server-tls-1 \ - --location=us-west1 \ - --update-labels=foo=bar + --location=us-west1 --update-labels=foo=bar To disable publishing CRLs for a subordinate CA: $ gcloud beta privateca subordinates update server-tls-1 \ - --location=us-west1 \ - --no-publish-crl + --location=us-west1 --no-publish-crl POSITIONAL ARGUMENTS CERTIFICATE AUTHORITY resource - The certificate authority to update. The diff --git a/gcloud/beta/pubsub/lite-reservations/create b/gcloud/beta/pubsub/lite-reservations/create index e366d194e..6a6a551d3 100644 --- a/gcloud/beta/pubsub/lite-reservations/create +++ b/gcloud/beta/pubsub/lite-reservations/create @@ -13,8 +13,7 @@ EXAMPLES To create a Pub/Sub lite-reservation, run: $ gcloud beta pubsub lite-reservations create myreservation \ - --location=us-central1 \ - --throughput-capacity=2 + --location=us-central1 --throughput-capacity=2 POSITIONAL ARGUMENTS RESERVATION diff --git a/gcloud/beta/pubsub/lite-reservations/delete b/gcloud/beta/pubsub/lite-reservations/delete index 67b379d2b..0a1dd4a0a 100644 --- a/gcloud/beta/pubsub/lite-reservations/delete +++ b/gcloud/beta/pubsub/lite-reservations/delete @@ -13,7 +13,7 @@ EXAMPLES To delete a Pub/Sub Lite reservation, run: $ gcloud beta pubsub lite-reservations delete myreservation \ - --location=us-central1 + --location=us-central1 POSITIONAL ARGUMENTS Reservation resource - Reservation to delete. The arguments in this group diff --git a/gcloud/beta/pubsub/lite-reservations/describe b/gcloud/beta/pubsub/lite-reservations/describe index addf1bfb0..d2c089057 100644 --- a/gcloud/beta/pubsub/lite-reservations/describe +++ b/gcloud/beta/pubsub/lite-reservations/describe @@ -13,7 +13,7 @@ EXAMPLES To describe a Pub/Sub Lite reservation, run: $ gcloud beta pubsub lite-reservations describe myreservation \ - --location=us-central1 + --location=us-central1 POSITIONAL ARGUMENTS Reservation resource - Reservation to describe. The arguments in this diff --git a/gcloud/beta/pubsub/lite-reservations/list b/gcloud/beta/pubsub/lite-reservations/list index 42b5e4abb..0b237aa5c 100644 --- a/gcloud/beta/pubsub/lite-reservations/list +++ b/gcloud/beta/pubsub/lite-reservations/list @@ -13,7 +13,7 @@ EXAMPLES To list Pub/Sub Lite reservations, run: $ gcloud beta pubsub lite-reservations list --location=us-central1 \ - --limit=5 + --limit=5 REQUIRED FLAGS Location resource - Location to list reservations for. This represents a diff --git a/gcloud/beta/pubsub/lite-reservations/list-topics b/gcloud/beta/pubsub/lite-reservations/list-topics index 96ea74bd2..3acecfe83 100644 --- a/gcloud/beta/pubsub/lite-reservations/list-topics +++ b/gcloud/beta/pubsub/lite-reservations/list-topics @@ -15,7 +15,7 @@ EXAMPLES To list Pub/Sub Lite topics for a given Lite reservation, run: $ gcloud beta pubsub lite-reservations list-topics myreservation \ - --location=us-central1 + --location=us-central1 POSITIONAL ARGUMENTS Reservation resource - Reservation to list topics for. The arguments in diff --git a/gcloud/beta/pubsub/lite-reservations/update b/gcloud/beta/pubsub/lite-reservations/update index e8f5617e9..f6a9f2e0b 100644 --- a/gcloud/beta/pubsub/lite-reservations/update +++ b/gcloud/beta/pubsub/lite-reservations/update @@ -14,8 +14,7 @@ EXAMPLES To update a Pub/Sub Lite reservation, run: $ gcloud beta pubsub lite-reservations update myreservation \ - --location=us-central1 \ - --throughput-capacity=2 + --location=us-central1 --throughput-capacity=2 POSITIONAL ARGUMENTS Reservation resource - Reservation to update. The arguments in this group diff --git a/gcloud/beta/pubsub/lite-subscriptions/ack-up-to b/gcloud/beta/pubsub/lite-subscriptions/ack-up-to index 31d1c74c6..76e1d389c 100644 --- a/gcloud/beta/pubsub/lite-subscriptions/ack-up-to +++ b/gcloud/beta/pubsub/lite-subscriptions/ack-up-to @@ -16,9 +16,7 @@ EXAMPLES To acknowledge messages on a Pub/Sub Lite subscription, run: $ gcloud beta pubsub lite-subscriptions ack-up-to mysubscription \ - --location=us-central1-a \ - --partition=0 \ - --offset=10 + --location=us-central1-a --partition=0 --offset=10 POSITIONAL ARGUMENTS Subscription resource - Subscription on which to acknowledge messages. The diff --git a/gcloud/beta/pubsub/lite-subscriptions/create b/gcloud/beta/pubsub/lite-subscriptions/create index f4e5fae9a..246abe351 100644 --- a/gcloud/beta/pubsub/lite-subscriptions/create +++ b/gcloud/beta/pubsub/lite-subscriptions/create @@ -16,16 +16,14 @@ EXAMPLES To create a Pub/Sub Lite subscription, run: $ gcloud beta pubsub lite-subscriptions create mysubscription \ - --location=us-central1-a \ - --topic=mytopic + --location=us-central1-a --topic=mytopic To create a Pub/Sub Lite subscription at the offset of the oldest retained message, run: $ gcloud beta pubsub lite-subscriptions create mysubscription \ - --location=us-central1-a \ - --topic=mytopic \ - --starting-offset=beginning + --location=us-central1-a --topic=mytopic \ + --starting-offset=beginning POSITIONAL ARGUMENTS SUBSCRIPTION diff --git a/gcloud/beta/pubsub/lite-subscriptions/delete b/gcloud/beta/pubsub/lite-subscriptions/delete index 7c4bb5f92..9becf2194 100644 --- a/gcloud/beta/pubsub/lite-subscriptions/delete +++ b/gcloud/beta/pubsub/lite-subscriptions/delete @@ -13,7 +13,7 @@ EXAMPLES To delete a Pub/Sub Lite subscription, run: $ gcloud beta pubsub lite-subscriptions delete mysubscription \ - --location=us-central1-a + --location=us-central1-a POSITIONAL ARGUMENTS Subscription resource - Subscription to delete. The arguments in this diff --git a/gcloud/beta/pubsub/lite-subscriptions/describe b/gcloud/beta/pubsub/lite-subscriptions/describe index 785fe4921..e97dc457d 100644 --- a/gcloud/beta/pubsub/lite-subscriptions/describe +++ b/gcloud/beta/pubsub/lite-subscriptions/describe @@ -13,7 +13,7 @@ EXAMPLES To describe a Pub/Sub Lite subscription, run: $ gcloud beta pubsub lite-subscriptions describe mysubscription \ - --location=us-central1-a + --location=us-central1-a POSITIONAL ARGUMENTS Subscription resource - Subscription to describe. The arguments in this diff --git a/gcloud/beta/pubsub/lite-subscriptions/list b/gcloud/beta/pubsub/lite-subscriptions/list index 15856b387..c3834ec49 100644 --- a/gcloud/beta/pubsub/lite-subscriptions/list +++ b/gcloud/beta/pubsub/lite-subscriptions/list @@ -14,8 +14,7 @@ EXAMPLES To list Pub/Sub Lite subscriptions, run: $ gcloud beta pubsub lite-subscriptions list \ - --location=us-central1-a \ - --limit=5 + --location=us-central1-a --limit=5 FLAGS Location resource - ID of the location or fully qualified identifier for diff --git a/gcloud/beta/pubsub/lite-subscriptions/seek b/gcloud/beta/pubsub/lite-subscriptions/seek index 61e06fd18..f411ffa05 100644 --- a/gcloud/beta/pubsub/lite-subscriptions/seek +++ b/gcloud/beta/pubsub/lite-subscriptions/seek @@ -24,16 +24,14 @@ EXAMPLES backlog, run: $ gcloud beta pubsub lite-subscriptions seek mysubscription \ - --location=us-central1-a \ - --starting-offset=beginning + --location=us-central1-a --starting-offset=beginning To seek a Pub/Sub Lite subscription to a publish time without waiting for the operation to complete, run: $ gcloud beta pubsub lite-subscriptions seek mysubscription \ - --location=us-central1-a \ - --publish-time="2021-01-01T12:00:00Z" - --async + --location=us-central1-a --publish-time="2021-01-01T12:00:00Z" \ + --async POSITIONAL ARGUMENTS Subscription resource - Subscription to seek. The arguments in this group diff --git a/gcloud/beta/pubsub/lite-subscriptions/update b/gcloud/beta/pubsub/lite-subscriptions/update index 32aadbf44..af9690240 100644 --- a/gcloud/beta/pubsub/lite-subscriptions/update +++ b/gcloud/beta/pubsub/lite-subscriptions/update @@ -14,8 +14,8 @@ EXAMPLES To update a Cloud Pub/Sub lite-subscription, run: $ gcloud beta pubsub lite-subscriptions update mysubscription \ - --location=us-central1-a \ - --delivery-requirement=DELIVER_IMMEDIATELY + --location=us-central1-a \ + --delivery-requirement=DELIVER_IMMEDIATELY POSITIONAL ARGUMENTS Subscription resource - Subscription to update. The arguments in this diff --git a/gcloud/beta/pubsub/lite-topics/create b/gcloud/beta/pubsub/lite-topics/create index cd75b7b69..c322bb65e 100644 --- a/gcloud/beta/pubsub/lite-topics/create +++ b/gcloud/beta/pubsub/lite-topics/create @@ -17,10 +17,8 @@ EXAMPLES To create a Pub/Sub lite-topic, run: $ gcloud beta pubsub lite-topics create mytopic \ - --location=us-central1-a \ - --partitions=1 \ - --per-partition-bytes=30GiB \ - --message-retention-period=2w + --location=us-central1-a --partitions=1 \ + --per-partition-bytes=30GiB --message-retention-period=2w POSITIONAL ARGUMENTS TOPIC diff --git a/gcloud/beta/pubsub/lite-topics/delete b/gcloud/beta/pubsub/lite-topics/delete index fbe96264e..73a1491a3 100644 --- a/gcloud/beta/pubsub/lite-topics/delete +++ b/gcloud/beta/pubsub/lite-topics/delete @@ -12,7 +12,7 @@ EXAMPLES To delete a Pub/Sub Lite topic, run: $ gcloud beta pubsub lite-topics delete mytopic \ - --location=us-central1-a + --location=us-central1-a POSITIONAL ARGUMENTS Topic resource - Topic to delete. The arguments in this group can be used diff --git a/gcloud/beta/pubsub/lite-topics/describe b/gcloud/beta/pubsub/lite-topics/describe index 7c63e0831..3af31a52f 100644 --- a/gcloud/beta/pubsub/lite-topics/describe +++ b/gcloud/beta/pubsub/lite-topics/describe @@ -12,7 +12,7 @@ EXAMPLES To describe a Pub/Sub Lite topic, run: $ gcloud beta pubsub lite-topics describe mytopic \ - --location=us-central1-a + --location=us-central1-a POSITIONAL ARGUMENTS Topic resource - Topic to describe. The arguments in this group can be diff --git a/gcloud/beta/pubsub/lite-topics/list b/gcloud/beta/pubsub/lite-topics/list index 9439fe7a2..187ca2ea0 100644 --- a/gcloud/beta/pubsub/lite-topics/list +++ b/gcloud/beta/pubsub/lite-topics/list @@ -13,7 +13,7 @@ EXAMPLES To list Pub/Sub Lite topics, run: $ gcloud beta pubsub lite-topics list --location=us-central1-a \ - --limit=5 + --limit=5 FLAGS Location resource - Zone to list topics for. This represents a Cloud diff --git a/gcloud/beta/pubsub/lite-topics/list-subscriptions b/gcloud/beta/pubsub/lite-topics/list-subscriptions index d230765dc..b56213e61 100644 --- a/gcloud/beta/pubsub/lite-topics/list-subscriptions +++ b/gcloud/beta/pubsub/lite-topics/list-subscriptions @@ -14,7 +14,7 @@ EXAMPLES To list Pub/Sub Lite subscriptions for a given Lite topic, run: $ gcloud beta pubsub lite-topics list-subscriptions mytopic \ - --location=us-central1-a + --location=us-central1-a POSITIONAL ARGUMENTS Topic resource - Topic to list subscriptions for. The arguments in this diff --git a/gcloud/beta/pubsub/lite-topics/update b/gcloud/beta/pubsub/lite-topics/update index fa853157f..5de0b3982 100644 --- a/gcloud/beta/pubsub/lite-topics/update +++ b/gcloud/beta/pubsub/lite-topics/update @@ -17,8 +17,7 @@ EXAMPLES To update a Pub/Sub Lite topic, run: $ gcloud beta pubsub lite-topics update mytopic \ - --location=us-central1-a \ - --per-partition-publish-mib=10 + --location=us-central1-a --per-partition-publish-mib=10 POSITIONAL ARGUMENTS Topic resource - Topic to update. The arguments in this group can be used diff --git a/gcloud/beta/pubsub/subscriptions/add-iam-policy-binding b/gcloud/beta/pubsub/subscriptions/add-iam-policy-binding index 95d5a4505..b536e8c1e 100644 --- a/gcloud/beta/pubsub/subscriptions/add-iam-policy-binding +++ b/gcloud/beta/pubsub/subscriptions/add-iam-policy-binding @@ -23,8 +23,8 @@ EXAMPLES $ gcloud beta pubsub subscriptions add-iam-policy-binding \ my-subscription \ - --member='serviceAccount:my-iam-account@my-project.iam.gserviceaccount.com' \ - --role='roles/editor' + --member='serviceAccount:my-iam-account@my-project.iam.gservicea\ + ccount.com' --role='roles/editor' See https://cloud.google.com/iam/docs/managing-policies for details of policy role and member types. diff --git a/gcloud/beta/pubsub/subscriptions/create b/gcloud/beta/pubsub/subscriptions/create index be3818b4c..91e486f62 100644 --- a/gcloud/beta/pubsub/subscriptions/create +++ b/gcloud/beta/pubsub/subscriptions/create @@ -5,9 +5,9 @@ NAME SYNOPSIS gcloud beta pubsub subscriptions create SUBSCRIPTION [SUBSCRIPTION ...] (--topic=TOPIC : --topic-project=TOPIC_PROJECT) - [--ack-deadline=ACK_DEADLINE] [--enable-message-ordering] - [--expiration-period=EXPIRATION_PERIOD] [--labels=[KEY=VALUE,...]] - [--message-filter=MESSAGE_FILTER] + [--ack-deadline=ACK_DEADLINE] [--enable-exactly-once-delivery] + [--enable-message-ordering] [--expiration-period=EXPIRATION_PERIOD] + [--labels=[KEY=VALUE,...]] [--message-filter=MESSAGE_FILTER] [--message-retention-duration=MESSAGE_RETENTION_DURATION] [--push-auth-service-account=SERVICE_ACCOUNT_EMAIL] [--push-auth-token-audience=OPTIONAL_AUDIENCE_OVERRIDE] @@ -70,6 +70,14 @@ OPTIONAL FLAGS The number of seconds the system will wait for a subscriber to acknowledge receiving a message before re-attempting delivery. + --enable-exactly-once-delivery + Whether or not to enble exactly once delivery on the subscription. If + true, Pub/Sub provides the following guarantees for the delivery of a + message with a given value of message_id on this subscription: The + message sent to a subscriber is guaranteed not to be resent before the + message's acknowledgement deadline expires. An acknowledged message + will not be resent to a subscriber. + --enable-message-ordering Whether to receive messages with the same ordering key in order. If set, messages with the same ordering key are sent to subscribers in the diff --git a/gcloud/beta/pubsub/subscriptions/update b/gcloud/beta/pubsub/subscriptions/update index 5af460a17..d1a34ff01 100644 --- a/gcloud/beta/pubsub/subscriptions/update +++ b/gcloud/beta/pubsub/subscriptions/update @@ -4,7 +4,8 @@ NAME SYNOPSIS gcloud beta pubsub subscriptions update SUBSCRIPTION - [--ack-deadline=ACK_DEADLINE] [--expiration-period=EXPIRATION_PERIOD] + [--ack-deadline=ACK_DEADLINE] [--enable-exactly-once-delivery] + [--expiration-period=EXPIRATION_PERIOD] [--message-retention-duration=MESSAGE_RETENTION_DURATION] [--push-auth-service-account=SERVICE_ACCOUNT_EMAIL] [--push-auth-token-audience=OPTIONAL_AUDIENCE_OVERRIDE] @@ -43,6 +44,14 @@ FLAGS The number of seconds the system will wait for a subscriber to acknowledge receiving a message before re-attempting delivery. + --enable-exactly-once-delivery + Whether or not to enble exactly once delivery on the subscription. If + true, Pub/Sub provides the following guarantees for the delivery of a + message with a given value of message_id on this subscription: The + message sent to a subscriber is guaranteed not to be resent before the + message's acknowledgement deadline expires. An acknowledged message + will not be resent to a subscriber. + --expiration-period=EXPIRATION_PERIOD The subscription will expire if it is inactive for the given period. Valid values are strings of the form INTEGER[UNIT], where UNIT is one diff --git a/gcloud/beta/recommender/insight-type-config/update b/gcloud/beta/recommender/insight-type-config/update index 7d3eaf797..27bc77bf1 100644 --- a/gcloud/beta/recommender/insight-type-config/update +++ b/gcloud/beta/recommender/insight-type-config/update @@ -17,8 +17,8 @@ EXAMPLES To update an insight type configuration, run: $ gcloud beta recommender insight-type-config update \ - ${INSIGHT_TYPE} --project=${PROJECT} --location=${LOCATION} - --etag=\"123\" --config-file=config.yaml + ${INSIGHT_TYPE} --project=${PROJECT} --location=${LOCATION} \ + --etag=\"123\" --config-file=config.yaml POSITIONAL ARGUMENTS INSIGHT_TYPE diff --git a/gcloud/beta/recommender/recommendations/describe b/gcloud/beta/recommender/recommendations/describe index 79f566e67..2747bbdaa 100644 --- a/gcloud/beta/recommender/recommendations/describe +++ b/gcloud/beta/recommender/recommendations/describe @@ -17,8 +17,8 @@ EXAMPLES To describe a recommendation: $ gcloud beta recommender recommendations describe \ - RECOMMENDATION_ID --project=${PROJECT} --location=${LOCATION} - --recommender=${RECOMMENDER} + RECOMMENDATION_ID --project=${PROJECT} --location=${LOCATION} \ + --recommender=${RECOMMENDER} POSITIONAL ARGUMENTS RECOMMENDATION diff --git a/gcloud/beta/recommender/recommendations/list b/gcloud/beta/recommender/recommendations/list index bb77e0cd7..ae8e99149 100644 --- a/gcloud/beta/recommender/recommendations/list +++ b/gcloud/beta/recommender/recommendations/list @@ -11,7 +11,7 @@ SYNOPSIS [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) This command will list all recommendations for a give + (BETA) This command will list all recommendations for a given cloud_entity_id, location and recommender. Supported recommenders can be found here: https://cloud.google.com/recommender/docs/recommenders. Currently the following cloud_entity_types are supported: project, diff --git a/gcloud/beta/recommender/recommendations/mark-claimed b/gcloud/beta/recommender/recommendations/mark-claimed index 79225a3bf..d8f65e8a4 100644 --- a/gcloud/beta/recommender/recommendations/mark-claimed +++ b/gcloud/beta/recommender/recommendations/mark-claimed @@ -20,9 +20,9 @@ EXAMPLES To mark a recommendation as CLAIMED: $ gcloud beta recommender recommendations mark-claimed \ - RECOMMENDATION --project=project-name --location=global - --recommender=google.compute.instance.MachineTypeRecommender --etag=abc123 - --state-metadata=key1=value1,key2=value2 + RECOMMENDATION --project=project-name --location=global \ + --recommender=google.compute.instance.MachineTypeRecommender \ + --etag=abc123 --state-metadata=key1=value1,key2=value2 POSITIONAL ARGUMENTS RECOMMENDATION diff --git a/gcloud/beta/recommender/recommender-config/update b/gcloud/beta/recommender/recommender-config/update index e47e91392..4a8f7303c 100644 --- a/gcloud/beta/recommender/recommender-config/update +++ b/gcloud/beta/recommender/recommender-config/update @@ -17,8 +17,8 @@ EXAMPLES To update a recommender configuration, run: $ gcloud beta recommender recommender-config update ${RECOMMENDER} \ - --project=${PROJECT} --location=${LOCATION} - --etag=\"123\" --config-file=config.yaml + --project=${PROJECT} --location=${LOCATION} --etag=\"123\" \ + --config-file=config.yaml POSITIONAL ARGUMENTS RECOMMENDER diff --git a/gcloud/beta/scc/findings/list b/gcloud/beta/scc/findings/list index c289338c9..68f99b8cf 100644 --- a/gcloud/beta/scc/findings/list +++ b/gcloud/beta/scc/findings/list @@ -35,7 +35,7 @@ EXAMPLES Only list category and resource_name of all ACTIVE findings under organization 123456 and source 5678: - $ gcloud beta scc findings list 123456 --source=5678 \ + $ gcloud beta scc findings list 123456 --source=5678 \ --filter="state=\"ACTIVE\"" \ --field-mask="finding.category,finding.resource_name" diff --git a/gcloud/beta/scheduler/jobs/create/app-engine b/gcloud/beta/scheduler/jobs/create/app-engine index 4d280fb63..07a6bc38e 100644 --- a/gcloud/beta/scheduler/jobs/create/app-engine +++ b/gcloud/beta/scheduler/jobs/create/app-engine @@ -26,8 +26,7 @@ EXAMPLES '/cron-handler' path in you App Engine app every 3 hours: $ gcloud beta scheduler jobs create app-engine my-job \ - --schedule="0 */3 * * *" - --relative-url="/cron-handler" + --schedule="0 */3 * * *" --relative-url="/cron-handler" POSITIONAL ARGUMENTS Job resource - Job to create. The arguments in this group can be used to diff --git a/gcloud/beta/scheduler/jobs/create/http b/gcloud/beta/scheduler/jobs/create/http index 357657305..357701930 100644 --- a/gcloud/beta/scheduler/jobs/create/http +++ b/gcloud/beta/scheduler/jobs/create/http @@ -28,8 +28,8 @@ EXAMPLES 'http://example.com/path' every 3 hours: $ gcloud beta scheduler jobs create http my-job \ - --schedule="0 */3 * * *" - --uri="http://example.com/path" --http-method=GET + --schedule="0 */3 * * *" --uri="http://example.com/path" \ + --http-method=GET POSITIONAL ARGUMENTS Job resource - Job to create. The arguments in this group can be used to diff --git a/gcloud/beta/scheduler/jobs/create/pubsub b/gcloud/beta/scheduler/jobs/create/pubsub index c4901113e..83e3019c1 100644 --- a/gcloud/beta/scheduler/jobs/create/pubsub +++ b/gcloud/beta/scheduler/jobs/create/pubsub @@ -22,8 +22,8 @@ EXAMPLES 'Hello' to the Pub/Sub topic 'cron-topic' every 3 hours: $ gcloud beta scheduler jobs create pubsub my-job \ - --schedule="0 */3 * * *" - --topic=cron-topic --message-body="Hello" + --schedule="0 */3 * * *" --topic=cron-topic \ + --message-body="Hello" POSITIONAL ARGUMENTS Job resource - Job to create. The arguments in this group can be used to diff --git a/gcloud/beta/secrets/create b/gcloud/beta/secrets/create index 7ffcb388b..5f0fbfb9f 100644 --- a/gcloud/beta/secrets/create +++ b/gcloud/beta/secrets/create @@ -32,24 +32,23 @@ EXAMPLES Create a new secret named 'my-secret' in 'us-central1' with data from a file: - $ gcloud beta secrets create my-secret --data-file=/tmp/secret - --replication-policy=user-managed \ - --locations=us-central1 + $ gcloud beta secrets create my-secret --data-file=/tmp/secret \ + --replication-policy=user-managed --locations=us-central1 Create a new secret named 'my-secret' in 'us-central1' and 'us-east1' with the value "s3cr3t": $ printf "s3cr3t" | gcloud beta secrets create my-secret \ - --data-file=- - --replication-policy=user-managed --locations=us-central1,us-east1 + --data-file=- --replication-policy=user-managed \ + --locations=us-central1,us-east1 Create a new secret named 'my-secret' in 'us-central1' and 'us-east1' with the value "s3cr3t" in PowerShell (Note: PowerShell will add a newline to the resulting secret): $ Write-Output "s3cr3t" | gcloud beta secrets create my-secret \ - --data-file=- - --replication-policy=user-managed --locations=us-central1,us-east1 + --data-file=- --replication-policy=user-managed \ + --locations=us-central1,us-east1 Create an expiring secret with an automatic replication policy using a ttl: @@ -70,8 +69,8 @@ EXAMPLES Create a secret with an automatic replication policy and a rotation period: $ gcloud beta secrets create my-secret \ - --next-rotation-time="2030-01-01T15:30:00-05:00" - --rotation-period="7200s" + --next-rotation-time="2030-01-01T15:30:00-05:00" \ + --rotation-period="7200s" POSITIONAL ARGUMENTS Secret resource - The secret to create. This represents a Cloud resource. diff --git a/gcloud/beta/secrets/update b/gcloud/beta/secrets/update index 69451c433..447fcf7c0 100644 --- a/gcloud/beta/secrets/update +++ b/gcloud/beta/secrets/update @@ -48,8 +48,8 @@ EXAMPLES Update a secret to have a next-rotation-time and rotation-period: $ gcloud beta secrets update my-secret \ - --next-rotation-time="2030-01-01T15:30:00-05:00" - --rotation-period="7200s" + --next-rotation-time="2030-01-01T15:30:00-05:00" \ + --rotation-period="7200s" Update a secret to remove the next-rotation-time: diff --git a/gcloud/beta/services/peered-dns-domains/create b/gcloud/beta/services/peered-dns-domains/create index a99f8c573..2f133b23d 100644 --- a/gcloud/beta/services/peered-dns-domains/create +++ b/gcloud/beta/services/peered-dns-domains/create @@ -21,15 +21,14 @@ EXAMPLES my-network in the current project, run: $ gcloud beta services peered-dns-domains create example-com \ - --network=my-network \ - --service=peering-service --dns-suffix=example.com. + --network=my-network --service=peering-service \ + --dns-suffix=example.com. To run the same command asynchronously (non-blocking), run: $ gcloud beta services peered-dns-domains create example-com \ - --network=my-network \ - --service=peering-service --dns-suffix=example.com. \ - --async + --network=my-network --service=peering-service \ + --dns-suffix=example.com. --async POSITIONAL ARGUMENTS NAME diff --git a/gcloud/beta/services/peered-dns-domains/delete b/gcloud/beta/services/peered-dns-domains/delete index f3383929a..22a089db9 100644 --- a/gcloud/beta/services/peered-dns-domains/delete +++ b/gcloud/beta/services/peered-dns-domains/delete @@ -18,14 +18,12 @@ EXAMPLES my-network in the current project, run: $ gcloud beta services peered-dns-domains delete example-com \ - --network=my-network \ - --service=peering-service + --network=my-network --service=peering-service To run the same command asynchronously (non-blocking), run: $ gcloud beta services peered-dns-domains delete example-com \ - --network=my-network \ - --service=peering-service --async + --network=my-network --service=peering-service --async POSITIONAL ARGUMENTS NAME diff --git a/gcloud/beta/services/vpc-peerings/connect b/gcloud/beta/services/vpc-peerings/connect index ab274fa6e..9843ec610 100644 --- a/gcloud/beta/services/vpc-peerings/connect +++ b/gcloud/beta/services/vpc-peerings/connect @@ -18,14 +18,13 @@ EXAMPLES the service to use, run: $ gcloud beta services vpc-peerings connect --network=my-network \ - --service=your-service \ - --ranges=google-range-1,google-range-2 + --service=your-service --ranges=google-range-1,google-range-2 To run the same command asynchronously (non-blocking), run: $ gcloud beta services vpc-peerings connect --network=my-network \ - --service=your-service \ - --ranges=google-range-1,google-range-2 --async + --service=your-service --ranges=google-range-1,google-range-2 \ + --async REQUIRED FLAGS --network=NETWORK diff --git a/gcloud/beta/services/vpc-peerings/update b/gcloud/beta/services/vpc-peerings/update index 7ba448ca7..4fff6d2b3 100644 --- a/gcloud/beta/services/vpc-peerings/update +++ b/gcloud/beta/services/vpc-peerings/update @@ -18,14 +18,13 @@ EXAMPLES google-range-1,google-range-2 for the service to use, run: $ gcloud beta services vpc-peerings update --network=my-network \ - --service=your-service \ - --ranges=google-range-1,google-range-2 + --service=your-service --ranges=google-range-1,google-range-2 To run the same command asynchronously (non-blocking), run: $ gcloud beta services vpc-peerings update --network=my-network \ - --service=your-service \ - --ranges=google-range-1,google-range-2 --async + --service=your-service --ranges=google-range-1,google-range-2 \ + --async REQUIRED FLAGS --network=NETWORK diff --git a/gcloud/beta/source/project-configs/update b/gcloud/beta/source/project-configs/update index 7c4fd3ce4..a71556836 100644 --- a/gcloud/beta/source/project-configs/update +++ b/gcloud/beta/source/project-configs/update @@ -19,8 +19,7 @@ EXAMPLES notifications, run: $ gcloud beta source project-configs update --add-topic=TOPIC_NAME \ - --service-account=SERVICE_ACCOUNT_EMAIL \ - --message-format=json + --service-account=SERVICE_ACCOUNT_EMAIL --message-format=json REQUIRED FLAGS Exactly one of these must be specified: diff --git a/gcloud/beta/source/repos/clone b/gcloud/beta/source/repos/clone index d5db23c2e..967287798 100644 --- a/gcloud/beta/source/repos/clone +++ b/gcloud/beta/source/repos/clone @@ -26,8 +26,8 @@ EXAMPLES $ gcloud beta source repos clone REPOSITORY_NAME DIRECTORY_NAME - $ cd DIRECTORY_NAME - ... create/edit files and create one or more commits ... + $ cd DIRECTORY_NAME ... create/edit files and create one or more \ + commits ... $ git push origin master diff --git a/gcloud/beta/source/repos/update b/gcloud/beta/source/repos/update index 2e2846fee..4b4e6c19a 100644 --- a/gcloud/beta/source/repos/update +++ b/gcloud/beta/source/repos/update @@ -14,8 +14,7 @@ EXAMPLES notifications, run: $ gcloud beta source repos update --add-topic=TOPIC_NAME \ - --service-account=SERVICE_ACCOUNT_EMAIL \ - --message-format=json + --service-account=SERVICE_ACCOUNT_EMAIL --message-format=json POSITIONAL ARGUMENTS Repo resource - Name of the Cloud Source repository to update. This diff --git a/gcloud/beta/spanner/backups/add-iam-policy-binding b/gcloud/beta/spanner/backups/add-iam-policy-binding index 6c57bec4f..13dbec078 100644 --- a/gcloud/beta/spanner/backups/add-iam-policy-binding +++ b/gcloud/beta/spanner/backups/add-iam-policy-binding @@ -17,8 +17,8 @@ EXAMPLES for the user 'test-user@gmail.com' with backup 'example-backup' and instance 'example-instance', run: - $ gcloud beta spanner backups add-iam-policy-binding example-backup \ - --instance='example-instance' \ + $ gcloud beta spanner backups add-iam-policy-binding \ + example-backup --instance='example-instance' \ --member='user:test-user@gmail.com' \ --role='roles/spanner.backupAdmin' @@ -26,11 +26,13 @@ EXAMPLES the role of 'roles/spanner.backupAdmin' and the user 'test-user@gmail.com' with backup 'example-backup' and instance 'example-instance', run: - $ gcloud beta spanner backups add-iam-policy-binding example-backup \ - --instance='example-instance' \ + $ gcloud beta spanner backups add-iam-policy-binding \ + example-backup --instance='example-instance' \ --member='user:test-user@gmail.com' \ --role='roles/spanner.backupAdmin' \ - --condition='expression=request.time < timestamp("2019-01-01T00:00:00Z"),title=expires_end_of_2018,description=Expires at midnight on 2018-12-31' + --condition='expression=request.time < + timestamp("2019-01-01T00:00:00Z"),title=expires_end_of_2018,descrip\ + tion=Expires at midnight on 2018-12-31' See https://cloud.google.com/iam/docs/managing-policies for details of policy role and member types. diff --git a/gcloud/beta/spanner/backups/remove-iam-policy-binding b/gcloud/beta/spanner/backups/remove-iam-policy-binding index 41483a3b6..5f7118502 100644 --- a/gcloud/beta/spanner/backups/remove-iam-policy-binding +++ b/gcloud/beta/spanner/backups/remove-iam-policy-binding @@ -19,8 +19,7 @@ EXAMPLES instance 'example-instance', run: $ gcloud beta spanner backups remove-iam-policy-binding \ - example-backup \ - --instance='example-instance' \ + example-backup --instance='example-instance' \ --member='user:test-user@gmail.com' \ --role='roles/spanner.backupAdmin' @@ -29,11 +28,12 @@ EXAMPLES with backup 'example-backup' and instance 'example-instance', run: $ gcloud beta spanner backups remove-iam-policy-binding \ - example-backup \ - --instance='example-instance' \ + example-backup --instance='example-instance' \ --member='user:test-user@gmail.com' \ --role='roles/spanner.backupAdmin' \ - --condition='expression=request.time < timestamp("2019-01-01T00:00:00Z"),title=expires_end_of_2018,description=Expires at midnight on 2018-12-31' + --condition='expression=request.time < + timestamp("2019-01-01T00:00:00Z"),title=expires_end_of_2018,descrip\ + tion=Expires at midnight on 2018-12-31' See https://cloud.google.com/iam/docs/managing-policies for details of policy role and member types. diff --git a/gcloud/beta/spanner/databases/create b/gcloud/beta/spanner/databases/create index 9f3cc3d76..68b555d1a 100644 --- a/gcloud/beta/spanner/databases/create +++ b/gcloud/beta/spanner/databases/create @@ -21,14 +21,13 @@ EXAMPLES To create a Cloud Spanner database with populated schema, run: $ gcloud beta spanner databases create testdb \ - --instance=my-instance-id + --instance=my-instance-id \ --ddl='CREATE TABLE mytable (a INT64, b INT64) PRIMARY KEY(a)' To create a Cloud Spanner database with the PostgreSQL dialect, run: $ gcloud beta spanner databases create testdb \ - --instance=my-instance-id - --database-dialect=POSTGRESQL + --instance=my-instance-id --database-dialect=POSTGRESQL POSITIONAL ARGUMENTS Database resource - The Cloud Spanner database to create. The arguments in diff --git a/gcloud/beta/spanner/databases/ddl/update b/gcloud/beta/spanner/databases/ddl/update index a119a1985..f61d69cea 100644 --- a/gcloud/beta/spanner/databases/ddl/update +++ b/gcloud/beta/spanner/databases/ddl/update @@ -13,7 +13,7 @@ EXAMPLES To add a column to a table in the given Cloud Spanner database, run: $ gcloud beta spanner databases ddl update my-database-id \ - --instance=my-instance-id + --instance=my-instance-id \ --ddl='ALTER TABLE test_table ADD COLUMN a INT64' POSITIONAL ARGUMENTS diff --git a/gcloud/beta/spanner/databases/sessions/delete b/gcloud/beta/spanner/databases/sessions/delete index 63d3e7ece..eb1ae9387 100644 --- a/gcloud/beta/spanner/databases/sessions/delete +++ b/gcloud/beta/spanner/databases/sessions/delete @@ -14,8 +14,7 @@ EXAMPLES To delete a Cloud Spanner session, run: $ gcloud beta spanner databases sessions delete my-session-id \ - --instance=my-instance-id - --database=my-database-id + --instance=my-instance-id --database=my-database-id POSITIONAL ARGUMENTS Session resource - The Cloud Spanner session to delete. The arguments in diff --git a/gcloud/beta/spanner/operations/cancel b/gcloud/beta/spanner/operations/cancel index 83499a9d7..c9042f85d 100644 --- a/gcloud/beta/spanner/operations/cancel +++ b/gcloud/beta/spanner/operations/cancel @@ -16,15 +16,13 @@ EXAMPLES To cancel a database operation with ID auto_12345, run: - $ gcloud beta spanner operations cancel _auto_12345 \ - --instance=my-instance-id - --database=my-database-id + $ gcloud beta spanner operations cancel _auto_12345 \ + --instance=my-instance-id --database=my-database-id To cancel a backup operation with ID auto_12345, run: - $ gcloud beta spanner operations cancel _auto_12345 \ - --instance=my-instance-id - --backup=my-backup-id + $ gcloud beta spanner operations cancel _auto_12345 \ + --instance=my-instance-id --backup=my-backup-id POSITIONAL ARGUMENTS OPERATION-ID diff --git a/gcloud/beta/spanner/operations/describe b/gcloud/beta/spanner/operations/describe index bb3b7461f..ae12169be 100644 --- a/gcloud/beta/spanner/operations/describe +++ b/gcloud/beta/spanner/operations/describe @@ -17,15 +17,13 @@ EXAMPLES To describe a Cloud Spanner database operation, run: - $ gcloud beta spanner operations describe _auto_12345 \ - --instance=my-instance-id - --database=my-database-id + $ gcloud beta spanner operations describe _auto_12345 \ + --instance=my-instance-id --database=my-database-id To describe a Cloud Spanner backup operation, run: - $ gcloud beta spanner operations describe _auto_12345 \ - --instance=my-instance-id - --backup=my-backup-id + $ gcloud beta spanner operations describe _auto_12345 \ + --instance=my-instance-id --backup=my-backup-id POSITIONAL ARGUMENTS OPERATION-ID diff --git a/gcloud/beta/sql/import/sql b/gcloud/beta/sql/import/sql index d8afab20c..da85c012f 100644 --- a/gcloud/beta/sql/import/sql +++ b/gcloud/beta/sql/import/sql @@ -17,7 +17,7 @@ EXAMPLES To import data from a SQL dump file into a database, testdb, on the specified Cloud SQL instance test-instance-1, run: - $ gcloud sql import sql test-instance-1 \ + $ gcloud sql import sql test-instance-1 \ gs://test-bucket/test-file.sql.gz --database=testdb POSITIONAL ARGUMENTS diff --git a/gcloud/beta/tasks/create-http-task b/gcloud/beta/tasks/create-http-task index f70cf01a9..f25cb7263 100644 --- a/gcloud/beta/tasks/create-http-task +++ b/gcloud/beta/tasks/create-http-task @@ -18,7 +18,7 @@ DESCRIPTION EXAMPLES To create a task: - $ gcloud beta tasks create-http-task --queue=my-queue + $ gcloud beta tasks create-http-task --queue=my-queue \ --url=http://example.com/handler-path my-task POSITIONAL ARGUMENTS diff --git a/gcloud/beta/tasks/queues/create b/gcloud/beta/tasks/queues/create index d7e7c0a3a..d066f4373 100644 --- a/gcloud/beta/tasks/queues/create +++ b/gcloud/beta/tasks/queues/create @@ -19,13 +19,10 @@ DESCRIPTION EXAMPLES To create a Cloud Tasks queue: - $ gcloud beta tasks queues create my-queue - --max-attempts=10 --max-retry-duration=5s - --max-doublings=4 --min-backoff=1s - --max-backoff=10s - --max-dispatches-per-second=100 - --max-concurrent-dispatches=10 - --routing-override=service:abc + $ gcloud beta tasks queues create my-queue --max-attempts=10 \ + --max-retry-duration=5s --max-doublings=4 --min-backoff=1s \ + --max-backoff=10s --max-dispatches-per-second=100 \ + --max-concurrent-dispatches=10 --routing-override=service:abc POSITIONAL ARGUMENTS QUEUE diff --git a/gcloud/beta/tasks/queues/create-app-engine-queue b/gcloud/beta/tasks/queues/create-app-engine-queue index 6cb4fcb61..2baaa8296 100644 --- a/gcloud/beta/tasks/queues/create-app-engine-queue +++ b/gcloud/beta/tasks/queues/create-app-engine-queue @@ -27,12 +27,10 @@ DESCRIPTION EXAMPLES To create a Cloud Tasks queue: - $ gcloud beta tasks queues create-app-engine-queue my-queue - --max-attempts=10 --max-retry-duration=5s - --max-doublings=4 --min-backoff=1s - --max-backoff=10s - --max-dispatches-per-second=100 - --max-concurrent-dispatches=10 + $ gcloud beta tasks queues create-app-engine-queue my-queue \ + --max-attempts=10 --max-retry-duration=5s --max-doublings=4 \ + --min-backoff=1s --max-backoff=10s \ + --max-dispatches-per-second=100 --max-concurrent-dispatches=10 \ --routing-override=service:abc POSITIONAL ARGUMENTS diff --git a/gcloud/beta/tasks/queues/create-pull-queue b/gcloud/beta/tasks/queues/create-pull-queue index e548afe4e..eba8587b3 100644 --- a/gcloud/beta/tasks/queues/create-pull-queue +++ b/gcloud/beta/tasks/queues/create-pull-queue @@ -18,8 +18,8 @@ DESCRIPTION EXAMPLES To create a Cloud Tasks pull queue: - $ gcloud beta tasks queues create-pull-queue my-queue - --max-attempts=10 --max-retry-duration=10s + $ gcloud beta tasks queues create-pull-queue my-queue \ + --max-attempts=10 --max-retry-duration=10s POSITIONAL ARGUMENTS QUEUE diff --git a/gcloud/beta/tasks/queues/update b/gcloud/beta/tasks/queues/update index 773136b29..29293867a 100644 --- a/gcloud/beta/tasks/queues/update +++ b/gcloud/beta/tasks/queues/update @@ -24,13 +24,11 @@ DESCRIPTION EXAMPLES To update a Cloud Tasks queue: - $ gcloud beta tasks queues update my-queue - --clear-max-attempts --clear-max-retry-duration - --clear-max-doublings --clear-min-backoff - --clear-max-backoff - --clear-max-dispatches-per-second - --clear-max-concurrent-dispatches - --clear-routing-override + $ gcloud beta tasks queues update my-queue --clear-max-attempts \ + --clear-max-retry-duration --clear-max-doublings \ + --clear-min-backoff --clear-max-backoff \ + --clear-max-dispatches-per-second \ + --clear-max-concurrent-dispatches --clear-routing-override POSITIONAL ARGUMENTS QUEUE diff --git a/gcloud/beta/tasks/queues/update-app-engine-queue b/gcloud/beta/tasks/queues/update-app-engine-queue index 684f030ac..9f060f176 100644 --- a/gcloud/beta/tasks/queues/update-app-engine-queue +++ b/gcloud/beta/tasks/queues/update-app-engine-queue @@ -32,13 +32,11 @@ DESCRIPTION EXAMPLES To update a Cloud Tasks queue: - $ gcloud beta tasks queues update-app-engine-queue my-queue - --clear-max-attempts --clear-max-retry-duration - --clear-max-doublings --clear-min-backoff - --clear-max-backoff - --clear-max-dispatches-per-second - --clear-max-concurrent-dispatches - --clear-routing-override + $ gcloud beta tasks queues update-app-engine-queue my-queue \ + --clear-max-attempts --clear-max-retry-duration \ + --clear-max-doublings --clear-min-backoff --clear-max-backoff \ + --clear-max-dispatches-per-second \ + --clear-max-concurrent-dispatches --clear-routing-override POSITIONAL ARGUMENTS QUEUE diff --git a/gcloud/bigtable/backups/create b/gcloud/bigtable/backups/create index 6c3e8ac94..f07b37a66 100644 --- a/gcloud/bigtable/backups/create +++ b/gcloud/bigtable/backups/create @@ -16,15 +16,16 @@ EXAMPLES which expires at '2019-03-30T10:49:41Z', run: $ gcloud bigtable backups create BACKUP_NAME \ - --instance=INSTANCE_NAME --cluster=CLUSTER_NAME - --table=TABLE_NAME --expiration-date=2019-03-30T10:49:41Z --async + --instance=INSTANCE_NAME --cluster=CLUSTER_NAME \ + --table=TABLE_NAME --expiration-date=2019-03-30T10:49:41Z \ + --async To create a backup 'BACKUP_NAME' syncronously from table 'TABLE_NAME' which expires in 2 weeks from now, run: $ gcloud bigtable backups create BACKUP_NAME \ - --instance=INSTANCE_NAME --cluster=CLUSTER_NAME - --table=TABLE_NAME --retention-period=2w + --instance=INSTANCE_NAME --cluster=CLUSTER_NAME \ + --table=TABLE_NAME --retention-period=2w POSITIONAL ARGUMENTS Backup resource - The Cloud Bigtable backup to create. The arguments in diff --git a/gcloud/bigtable/backups/update b/gcloud/bigtable/backups/update index c91d42be4..bb3b83b65 100644 --- a/gcloud/bigtable/backups/update +++ b/gcloud/bigtable/backups/update @@ -16,8 +16,8 @@ EXAMPLES To update the expire time of backup 'BACKUP_NAME' to 7 days from now, run: $ gcloud bigtable backups update BACKUP_NAME \ - --instance=INSTANCE_NAME --cluster=CLUSTER_NAME - --retention-period=7d + --instance=INSTANCE_NAME --cluster=CLUSTER_NAME \ + --retention-period=7d POSITIONAL ARGUMENTS Backup resource - Cloud Bigtable backup to update. The arguments in this diff --git a/gcloud/builds/submit b/gcloud/builds/submit index 2b43dac9a..936abf7a2 100644 --- a/gcloud/builds/submit +++ b/gcloud/builds/submit @@ -25,7 +25,7 @@ EXAMPLES To submit a build with source located at storage URL gs://bucket/object.zip: - $ gcloud builds submit "gs://bucket/object.zip" \ + $ gcloud builds submit "gs://bucket/object.zip" \ --tag=gcr.io/my-project/image To submit a build with source located at storage URL gs://bucket/object.zip diff --git a/gcloud/builds/worker-pools/create b/gcloud/builds/worker-pools/create index 955edc1be..cc4470d73 100644 --- a/gcloud/builds/worker-pools/create +++ b/gcloud/builds/worker-pools/create @@ -21,10 +21,9 @@ EXAMPLES projects/123/global/networks/default and have a disk size of 64GB, run: $ gcloud builds worker-pools create wp1 --project=p1 \ - --region=us-central1 \ - --peered-network=projects/123/global/networks/default \ - --worker-machine-type=e2-standard-2 \ - --worker-disk-size=64GB + --region=us-central1 \ + --peered-network=projects/123/global/networks/default \ + --worker-machine-type=e2-standard-2 --worker-disk-size=64GB POSITIONAL ARGUMENTS WORKER_POOL diff --git a/gcloud/builds/worker-pools/update b/gcloud/builds/worker-pools/update index 01041552d..2131afcfc 100644 --- a/gcloud/builds/worker-pools/update +++ b/gcloud/builds/worker-pools/update @@ -16,9 +16,8 @@ EXAMPLES To change the machine type and disk size of workers in a worker pool named wp1, run: - $ gcloud builds worker-pools update wp1 --region=us-central1 \ - --worker-machine-type=e2-standard-2 \ - --worker-disk-size=64GB + $ gcloud builds worker-pools update wp1 --region=us-central1 \ + --worker-machine-type=e2-standard-2 --worker-disk-size=64GB POSITIONAL ARGUMENTS WORKER_POOL diff --git a/gcloud/compute/addresses/create b/gcloud/compute/addresses/create index a7424b861..1f746afd7 100644 --- a/gcloud/compute/addresses/create +++ b/gcloud/compute/addresses/create @@ -34,29 +34,27 @@ EXAMPLES region, run: $ gcloud compute addresses create SUBNET-ADDRESS-1 \ - --region=us-central1 \ - --subnet=default + --region=us-central1 --subnet=default To reserve an IP range '10.110.0.0/16' from the network 'default' for 'VPC_PEERING', run: $ gcloud compute addresses create IP-RANGE-1 --global \ --addresses=10.110.0.0 --prefix-length=16 \ - --purpose=VPC_PEERING --network=default + --purpose=VPC_PEERING --network=default To reserve any IP range with prefix length '16' from the network 'default' for 'VPC_PEERING', run: $ gcloud compute addresses create IP-RANGE-1 --global \ - --prefix-length=16 --purpose=VPC_PEERING \ - --network=default + --prefix-length=16 --purpose=VPC_PEERING --network=default To reserve an address from network 'default' for PRIVATE_SERVICE_CONNECT, run: $ gcloud compute addresses create PSC-ADDRESS-1 --global \ - --addresses=10.110.0.10 \ - --purpose=PRIVATE_SERVICE_CONNECT --network=default + --addresses=10.110.0.10 --purpose=PRIVATE_SERVICE_CONNECT \ + --network=default POSITIONAL ARGUMENTS [NAME ...] diff --git a/gcloud/compute/disks/create b/gcloud/compute/disks/create index ce7cbe570..2d6a1f569 100644 --- a/gcloud/compute/disks/create +++ b/gcloud/compute/disks/create @@ -268,14 +268,14 @@ FLAGS At most one of these can be specified: --source-disk-region=SOURCE_DISK_REGION - Region of the source disk, this argument is not required if target - disk is in same region of source disk. Overrides the default - compute/region property value for this command invocation. + Region of the source disk. This argument is not required if the + target disk is in the same region as the source disk. Overrides the + default compute/region property value for this command invocation. --source-disk-zone=SOURCE_DISK_ZONE - Zone of the source disk, this argument is not required if target disk - is in same zone of source disk. Overrides the default compute/zone - property value for this command invocation. + Zone of the source disk. This argument is not required if the target + disk is in the same zone as the source disk. 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, diff --git a/gcloud/compute/external-vpn-gateways/update b/gcloud/compute/external-vpn-gateways/update index ec317dee3..8f3913148 100644 --- a/gcloud/compute/external-vpn-gateways/update +++ b/gcloud/compute/external-vpn-gateways/update @@ -30,8 +30,8 @@ DESCRIPTION EXAMPLES To update labels for an external VPN gateway, run: - $ gcloud compute external-vpn-gateways update my-external-gateway \ - --update-labels=k0=value1,k1=value2 + $ gcloud compute external-vpn-gateways update my-external-gateway \ + --update-labels=k0=value1,k1=value2 POSITIONAL ARGUMENTS NAME diff --git a/gcloud/compute/firewall-policies/rules/create b/gcloud/compute/firewall-policies/rules/create index d7e1de754..24a2128a0 100644 --- a/gcloud/compute/firewall-policies/rules/create +++ b/gcloud/compute/firewall-policies/rules/create @@ -22,8 +22,8 @@ EXAMPLES with ID ``123456789", run: $ gcloud compute firewall-policies rules create 10 \ - --firewall-policy=123456789 --action=allow - --description=example-rule + --firewall-policy=123456789 --action=allow \ + --description=example-rule POSITIONAL ARGUMENTS PRIORITY diff --git a/gcloud/compute/firewall-policies/rules/update b/gcloud/compute/firewall-policies/rules/update index a027a5fcb..1f5a356ee 100644 --- a/gcloud/compute/firewall-policies/rules/update +++ b/gcloud/compute/firewall-policies/rules/update @@ -23,8 +23,8 @@ EXAMPLES ``new-example-rule", run: $ gcloud compute firewall-policies rules update 10 \ - --firewall-policy=123456789 --action=allow - --description=new-example-rule + --firewall-policy=123456789 --action=allow \ + --description=new-example-rule POSITIONAL ARGUMENTS PRIORITY diff --git a/gcloud/compute/firewall-rules/create b/gcloud/compute/firewall-rules/create index f56d122c1..b83e832ae 100644 --- a/gcloud/compute/firewall-rules/create +++ b/gcloud/compute/firewall-rules/create @@ -24,15 +24,17 @@ DESCRIPTION EXAMPLES To create a firewall rule allowing incoming TCP traffic on port 8080, run: - $ gcloud compute firewall-rules create FooService --allow=tcp:8080 - --description="Allow incoming traffic on TCP port 8080" --direction=INGRESS + $ gcloud compute firewall-rules create FooService --allow=tcp:8080 \ + --description="Allow incoming traffic on TCP port 8080" \ + --direction=INGRESS To create a firewall rule that allows TCP traffic through port 80 and determines a list of specific IP address blocks that are allowed to make inbound connections, run: - $ gcloud compute firewall-rules create "tcp-rule" --allow=tcp:80 - --source-ranges="10.0.0.0/22,10.0.0.0/14" --description="Narrowing TCP traffic" + $ gcloud compute firewall-rules create "tcp-rule" --allow=tcp:80 \ + --source-ranges="10.0.0.0/22,10.0.0.0/14" \ + --description="Narrowing TCP traffic" To list existing firewall rules, run: diff --git a/gcloud/compute/forwarding-rules/update b/gcloud/compute/forwarding-rules/update index 0b309752a..c0497f8ce 100644 --- a/gcloud/compute/forwarding-rules/update +++ b/gcloud/compute/forwarding-rules/update @@ -21,8 +21,8 @@ EXAMPLES To add/update labels k0 and k1 and remove labels with key k3, run: $ gcloud compute forwarding-rules update example-fr \ - --region=us-central1 \ - --update-labels=k0=value1,k1=value2 --remove-labels=k3 + --region=us-central1 --update-labels=k0=value1,k1=value2 \ + --remove-labels=k3 Labels can be used to identify the forwarding rule and to filter them as in diff --git a/gcloud/compute/instance-groups/managed/create-instance b/gcloud/compute/instance-groups/managed/create-instance index a90456fc7..6a761c931 100644 --- a/gcloud/compute/instance-groups/managed/create-instance +++ b/gcloud/compute/instance-groups/managed/create-instance @@ -26,11 +26,12 @@ EXAMPLES metadata my-key: my-value and a disk disk-1 attached to it as the device device-1, run: - $ gcloud compute instance-groups managed create-instance \ - my-group --region=europe-west4 \ - --instance=instance-1 \ - --stateful-disk='device-name=foo,source=https://compute.googleapis.com/compute/alpha/projects/my-project/zones/europe-west4/disks/disk-1,mode=rw,auto-delete=on-permanent-instance-deletion' \ - --stateful-metadata='my-key=my-value' + $ gcloud compute instance-groups managed create-instance my-group \ + --region=europe-west4 --instance=instance-1 \ + --stateful-disk='device-name=foo,source=https://compute.googleap\ + is.com/compute/alpha/projects/my-project/zones/europe-west4/disks/di\ + sk-1,mode=rw,auto-delete=on-permanent-instance-deletion' \ + --stateful-metadata='my-key=my-value' POSITIONAL ARGUMENTS NAME diff --git a/gcloud/compute/instance-groups/managed/describe-instance b/gcloud/compute/instance-groups/managed/describe-instance index b44da64cf..2b1619e38 100644 --- a/gcloud/compute/instance-groups/managed/describe-instance +++ b/gcloud/compute/instance-groups/managed/describe-instance @@ -17,8 +17,7 @@ EXAMPLES run: $ gcloud compute instance-groups managed describe-instance \ - my-group --instance=instance-1 \ - --region=europe-west4 + my-group --instance=instance-1 --region=europe-west4 POSITIONAL ARGUMENTS NAME diff --git a/gcloud/compute/instance-groups/managed/list-errors b/gcloud/compute/instance-groups/managed/list-errors index b0edb4ffc..4dc44462a 100644 --- a/gcloud/compute/instance-groups/managed/list-errors +++ b/gcloud/compute/instance-groups/managed/list-errors @@ -34,8 +34,8 @@ DESCRIPTION EXAMPLES To list errors on managed instance group 'my-group', run: - $ gcloud compute instance-groups managed list-errors \ - my-group --format=yaml + $ gcloud compute instance-groups managed list-errors my-group \ + --format=yaml POSITIONAL ARGUMENTS NAME diff --git a/gcloud/compute/instance-groups/managed/list-instances b/gcloud/compute/instance-groups/managed/list-instances index b5b2ec25e..8e60c1b86 100644 --- a/gcloud/compute/instance-groups/managed/list-instances +++ b/gcloud/compute/instance-groups/managed/list-instances @@ -35,8 +35,8 @@ EXAMPLES To see additional details about the instances in a managed instance group my-group, including per-instance overrides, run: - $ gcloud compute instance-groups managed list-instances \ - my-group --format=yaml + $ gcloud compute instance-groups managed list-instances my-group \ + --format=yaml POSITIONAL ARGUMENTS NAME diff --git a/gcloud/compute/instance-groups/managed/update-instances b/gcloud/compute/instance-groups/managed/update-instances index e944c57f8..1a2dbbd0e 100644 --- a/gcloud/compute/instance-groups/managed/update-instances +++ b/gcloud/compute/instance-groups/managed/update-instances @@ -34,10 +34,9 @@ EXAMPLES To update instances instance-1, instance-2 in my-group, with minimal-action=none and most-disruptive-allowed-action=restart, run: - $ gcloud compute instance-groups managed update-instances \ - my-group --instances=instance-1,instance2 \ - --minimal-action=none - --most-disruptive-allowed-action=restart + $ gcloud compute instance-groups managed update-instances my-group \ + --instances=instance-1,instance2 --minimal-action=none \ + --most-disruptive-allowed-action=restart POSITIONAL ARGUMENTS NAME diff --git a/gcloud/compute/instance-templates/create-with-container b/gcloud/compute/instance-templates/create-with-container index 6d094996a..c6aa0a23f 100644 --- a/gcloud/compute/instance-templates/create-with-container +++ b/gcloud/compute/instance-templates/create-with-container @@ -61,16 +61,16 @@ EXAMPLES a command, run: $ gcloud compute instance-templates create-with-container \ - instance-template-1 \ - --container-image=gcr.io/google-containers/busybox \ + instance-template-1 \ + --container-image=gcr.io/google-containers/busybox \ --container-command='echo "Hello world"' To create a template running gcr.io/google-containers/busybox in privileged mode, run: $ gcloud compute instance-templates create-with-container \ - instance-template-1 \ - --container-image=gcr.io/google-containers/busybox \ + instance-template-1 \ + --container-image=gcr.io/google-containers/busybox \ --container-privileged POSITIONAL ARGUMENTS diff --git a/gcloud/compute/instances/create-with-container b/gcloud/compute/instances/create-with-container index ea94726f8..11c3600bb 100644 --- a/gcloud/compute/instances/create-with-container +++ b/gcloud/compute/instances/create-with-container @@ -69,15 +69,15 @@ EXAMPLES To run the gcr.io/google-containers/busybox image on an instance named 'instance-1' that executes 'echo "Hello world"' as a run command, run: - $ gcloud compute instances create-with-container instance-1 \ - --container-image=gcr.io/google-containers/busybox \ - --container-command='echo "Hello world"' + $ gcloud compute instances create-with-container instance-1 \ + --container-image=gcr.io/google-containers/busybox \ + --container-command='echo "Hello world"' To run the gcr.io/google-containers/busybox image in privileged mode, run: - $ gcloud compute instances create-with-container instance-1 \ - --container-image=gcr.io/google-containers/busybox - --container-privileged + $ gcloud compute instances create-with-container instance-1 \ + --container-image=gcr.io/google-containers/busybox \ + --container-privileged POSITIONAL ARGUMENTS INSTANCE_NAMES [INSTANCE_NAMES ...] diff --git a/gcloud/compute/instances/network-interfaces/get-effective-firewalls b/gcloud/compute/instances/network-interfaces/get-effective-firewalls index 57d18aa44..f2ba945dd 100644 --- a/gcloud/compute/instances/network-interfaces/get-effective-firewalls +++ b/gcloud/compute/instances/network-interfaces/get-effective-firewalls @@ -20,7 +20,8 @@ EXAMPLES To get the effective firewalls of instance with name example-instance, run: $ gcloud compute instances network-interfaces \ - get-effective-firewalls example-instance, + get-effective-firewalls example-instance + To show all fields of the firewall rules, please show in JSON format with option --format=json diff --git a/gcloud/compute/instances/os-inventory/list-instances b/gcloud/compute/instances/os-inventory/list-instances index 32144a488..787c58101 100644 --- a/gcloud/compute/instances/os-inventory/list-instances +++ b/gcloud/compute/instances/os-inventory/list-instances @@ -37,43 +37,39 @@ EXAMPLES installed, run: $ gcloud compute instances os-inventory list-instances \ - --package-name="google-cloud-sdk" \ - --package-version="235.0.0-0" + --package-name="google-cloud-sdk" --package-version="235.0.0-0" To list all instances with package name matching a regex ^google-cloud available for update through apt, run: $ gcloud compute instances os-inventory list-instances \ - --inventory-filter="\ - PackageUpdates.apt[].Name~^google-cloud*" + --inventory-filter="PackageUpdates.apt[].Name~^google-cloud*" To list all instances with package update google-cloud-sdk of version greater than or equal to 235.0.0-0 available through apt, run: $ gcloud compute instances os-inventory list-instances \ - --inventory-filter="\ - PackageUpdates.apt[].['google-cloud-sdk'].Version>=235.0.0-0" + --inventory-filter="PackageUpdates.apt[].['google-cloud-sdk'].Ve\ + rsion>=235.0.0-0" To list all instances missing the Stackdriver monitoring package stackdriver-agent, run: $ gcloud compute instances os-inventory list-instances \ - --inventory-filter="\ - NOT(InstalledPackages:stackdriver-agent)" + --inventory-filter="NOT(InstalledPackages:stackdriver-agent)" To list all Windows instances with an installed qfe hotfix whose ID equals KB4462930, run: $ gcloud compute instances os-inventory list-instances \ - --inventory-filter="\ - InstalledPackages.qfe[].HotFixID=KB4462930" + --inventory-filter="InstalledPackages.qfe[].HotFixID=KB4462930" To list all Windows instances with a wua update whose description contains the word Security, run: $ gcloud compute instances os-inventory list-instances \ - --inventory-filter="\ - InstalledPackages.wua[].Description:Security" + --inventory-filter="InstalledPackages.wua[].Description:Security\ + " FLAGS --inventory-filter=INVENTORY_FILTER diff --git a/gcloud/compute/instances/set-iam-policy b/gcloud/compute/instances/set-iam-policy index d12e03086..50c41a58d 100644 --- a/gcloud/compute/instances/set-iam-policy +++ b/gcloud/compute/instances/set-iam-policy @@ -11,8 +11,11 @@ DESCRIPTION EXAMPLES The following command reads an IAM policy defined in a JSON file - policy.json and sets it for the instance 'my-instance' and zone 'ZONE': $ gcloud compute instances set-iam-policy my-instance --zone=ZONE \ + policy.json and sets it for the instance 'my-instance' and zone 'ZONE': + + $ gcloud compute instances set-iam-policy my-instance --zone=ZONE \ policy.json + See https://cloud.google.com/iam/docs/managing-policies for details of policy role and member types. diff --git a/gcloud/compute/instances/set-scheduling b/gcloud/compute/instances/set-scheduling index 5abc66db5..e9f648045 100644 --- a/gcloud/compute/instances/set-scheduling +++ b/gcloud/compute/instances/set-scheduling @@ -18,7 +18,7 @@ DESCRIPTION EXAMPLES To set instance to be terminated during maintenance, run: - $ gcloud compute instances set-scheduling example-instance \ + $ gcloud compute instances set-scheduling example-instance \ --maintenance-policy=TERMINATE --zone=us-central1-b POSITIONAL ARGUMENTS diff --git a/gcloud/compute/instances/update-access-config b/gcloud/compute/instances/update-access-config index 8ec0caa0f..eedba0bce 100644 --- a/gcloud/compute/instances/update-access-config +++ b/gcloud/compute/instances/update-access-config @@ -18,7 +18,7 @@ DESCRIPTION EXAMPLES To update network interface of an instance to 'nic0', run: - $ gcloud compute instances update-access-config example-instance \ + $ gcloud compute instances update-access-config example-instance \ --network-interface=nic0 --zone=us-central1-b POSITIONAL ARGUMENTS diff --git a/gcloud/compute/instances/update-container b/gcloud/compute/instances/update-container index 410799987..639bb4f03 100644 --- a/gcloud/compute/instances/update-container +++ b/gcloud/compute/instances/update-container @@ -40,14 +40,14 @@ EXAMPLES To run the gcr.io/google-containers/busybox image on an instance named 'instance-1' that executes 'echo "Hello world"' as a run command, run: - $ gcloud compute instances update-container instance-1 \ - --container-image=gcr.io/google-containers/busybox \ + $ gcloud compute instances update-container instance-1 \ + --container-image=gcr.io/google-containers/busybox \ --container-command='echo "Hello world"' To run the gcr.io/google-containers/busybox image in privileged mode, run: - $ gcloud compute instances update-container instance-1 \ - --container-image=gcr.io/google-containers/busybox \ + $ gcloud compute instances update-container instance-1 \ + --container-image=gcr.io/google-containers/busybox \ --container-privileged POSITIONAL ARGUMENTS diff --git a/gcloud/compute/networks/create b/gcloud/compute/networks/create index e663b3857..795f01b7c 100644 --- a/gcloud/compute/networks/create +++ b/gcloud/compute/networks/create @@ -24,8 +24,7 @@ EXAMPLES run: $ gcloud compute networks create network-name \ - --bgp-routing-mode=global \ - --subnet-mode=custom + --bgp-routing-mode=global --subnet-mode=custom POSITIONAL ARGUMENTS NAME diff --git a/gcloud/compute/networks/get-effective-firewalls b/gcloud/compute/networks/get-effective-firewalls index 03a1df8db..17104e07e 100644 --- a/gcloud/compute/networks/get-effective-firewalls +++ b/gcloud/compute/networks/get-effective-firewalls @@ -15,7 +15,8 @@ DESCRIPTION EXAMPLES To get the effective firewalls of network with name example-network, run: - $ gcloud compute networks get-effective-firewalls example-network, + $ gcloud compute networks get-effective-firewalls example-network + To show all fields of the firewall rules, please show in JSON format with option --format=json diff --git a/gcloud/compute/networks/peerings/create b/gcloud/compute/networks/peerings/create index 48f3485c0..2165ec929 100644 --- a/gcloud/compute/networks/peerings/create +++ b/gcloud/compute/networks/peerings/create @@ -21,12 +21,10 @@ EXAMPLES imports custom routes and subnet routes with public IPs, run: $ gcloud compute networks peerings create peering-name \ - --network=local-network \ - --peer-network=peer-network \ - --export-custom-routes \ - --import-custom-routes \ - --export-subnet-routes-with-public-ip \ - --import-subnet-routes-with-public-ip + --network=local-network --peer-network=peer-network \ + --export-custom-routes --import-custom-routes \ + --export-subnet-routes-with-public-ip \ + --import-subnet-routes-with-public-ip POSITIONAL ARGUMENTS NAME diff --git a/gcloud/compute/networks/peerings/delete b/gcloud/compute/networks/peerings/delete index 108380913..ca5d03c14 100644 --- a/gcloud/compute/networks/peerings/delete +++ b/gcloud/compute/networks/peerings/delete @@ -15,7 +15,7 @@ EXAMPLES 'local-network', run: $ gcloud compute networks peerings delete peering-name \ - --network=local-network + --network=local-network POSITIONAL ARGUMENTS NAME diff --git a/gcloud/compute/networks/peerings/list-routes b/gcloud/compute/networks/peerings/list-routes index 1490ab7bc..c5f4e7437 100644 --- a/gcloud/compute/networks/peerings/list-routes +++ b/gcloud/compute/networks/peerings/list-routes @@ -16,9 +16,8 @@ DESCRIPTION EXAMPLES List received routes for VPC network peering in us-central1: - $ gcloud compute networks peerings list-routes peering-name \ - --network=network-name --region=us-central1 \ - --direction=INCOMING + $ gcloud compute networks peerings list-routes peering-name \ + --network=network-name --region=us-central1 --direction=INCOMING POSITIONAL ARGUMENTS NAME diff --git a/gcloud/compute/networks/peerings/update b/gcloud/compute/networks/peerings/update index 445d9000e..3fdaed02a 100644 --- a/gcloud/compute/networks/peerings/update +++ b/gcloud/compute/networks/peerings/update @@ -13,15 +13,14 @@ EXAMPLES routes, run: $ gcloud compute networks peerings update peering-name \ - --export-custom-routes \ - --import-custom-routes + --export-custom-routes --import-custom-routes To update the peering named peering-name to both export and import subnet routes with public ip, run: $ gcloud compute networks peerings update peering-name \ - --export-subnet-routes-with-public-ip \ - --import-subnet-routes-with-public-ip + --export-subnet-routes-with-public-ip \ + --import-subnet-routes-with-public-ip POSITIONAL ARGUMENTS NAME diff --git a/gcloud/compute/networks/update b/gcloud/compute/networks/update index 349047d7e..782d6e7f3 100644 --- a/gcloud/compute/networks/update +++ b/gcloud/compute/networks/update @@ -13,13 +13,13 @@ EXAMPLES To update regional network with the name 'network-name' to global, run: $ gcloud compute networks update network-name \ - --bgp-routing-mode=global + --bgp-routing-mode=global To update an auto subnet mode network with the name 'network-name' to custom subnet mode, run: $ gcloud compute networks update network-name \ - --switch-to-custom-subnet-mode + --switch-to-custom-subnet-mode POSITIONAL ARGUMENTS NAME diff --git a/gcloud/compute/networks/vpc-access/connectors/create b/gcloud/compute/networks/vpc-access/connectors/create index 2deffff04..ca933adb1 100644 --- a/gcloud/compute/networks/vpc-access/connectors/create +++ b/gcloud/compute/networks/vpc-access/connectors/create @@ -25,8 +25,8 @@ EXAMPLES CIDR range of '10.132.0.0/28'. $ gcloud compute networks vpc-access connectors create \ - my-vpc-connector --region=us-central1 --network=my-network - --range=10.132.0.0/28 + my-vpc-connector --region=us-central1 --network=my-network \ + --range=10.132.0.0/28 POSITIONAL ARGUMENTS Connector resource - Arguments and flags that specify the VPC Access diff --git a/gcloud/compute/networks/vpc-access/operations/describe b/gcloud/compute/networks/vpc-access/operations/describe index d15bbc980..bda76e4ef 100644 --- a/gcloud/compute/networks/vpc-access/operations/describe +++ b/gcloud/compute/networks/vpc-access/operations/describe @@ -20,8 +20,8 @@ EXAMPLES region us-central1: $ gcloud compute networks vpc-access operations describe \ - operation-1564112342235-435a134f8c3f8-81bb4b49-0830c1f8 - --region=us-central + operation-1564112342235-435a134f8c3f8-81bb4b49-0830c1f8 \ + --region=us-central POSITIONAL ARGUMENTS Operation resource - The operation to describe. The arguments in this diff --git a/gcloud/compute/os-config/os-policy-assignment-reports/describe b/gcloud/compute/os-config/os-policy-assignment-reports/describe index ff7ef9aec..59ca67298 100644 --- a/gcloud/compute/os-config/os-policy-assignment-reports/describe +++ b/gcloud/compute/os-config/os-policy-assignment-reports/describe @@ -24,7 +24,7 @@ EXAMPLES projects/my-project/locations/us-central1-a/instances/\ my-instance/osPolicyAssignments/my-assignment/report - $ gcloud compute os-config os-policy-assignment-reports describe \ + $ gcloud compute os-config os-policy-assignment-reports describe \ https://osconfig.googleapis.com/v1alpha/projects/my-project/\ locations/us-central1-a/instances/instance-name/\ osPolicyAssignments/assignment-id/report diff --git a/gcloud/compute/packet-mirrorings/create b/gcloud/compute/packet-mirrorings/create index 8cf2d3554..db0205ab1 100644 --- a/gcloud/compute/packet-mirrorings/create +++ b/gcloud/compute/packet-mirrorings/create @@ -18,19 +18,18 @@ EXAMPLES us-central1, and send the mirrored traffic to the collector-fr Forwarding Rule. - $ gcloud compute packet-mirrorings create my-pm - --network my-network --region us-central1 - --mirrored-subnets my-subnet --collector-ilb collector-fr - --filter-protocols tcp + $ gcloud compute packet-mirrorings create my-pm \ + --network my-network --region us-central1 \ + --mirrored-subnets my-subnet --collector-ilb collector-fr \ + --filter-protocols tcp Mirror all traffic between instances with tag t1 and external server with IP 11.22.33.44 in us-central1, and send the mirrored traffic to the collector-fr Forwarding Rule. - $ gcloud compute packet-mirrorings create my-pm - --network my-network --region us-central1 - --mirrored-tags t1 --collector-ilb collector-fr - --filter-cidr-ranges 11.22.33.44/32 + $ gcloud compute packet-mirrorings create my-pm \ + --network my-network --region us-central1 --mirrored-tags t1 \ + --collector-ilb collector-fr --filter-cidr-ranges 11.22.33.44/32 POSITIONAL ARGUMENTS NAME diff --git a/gcloud/compute/packet-mirrorings/delete b/gcloud/compute/packet-mirrorings/delete index 899bf0108..7f9121504 100644 --- a/gcloud/compute/packet-mirrorings/delete +++ b/gcloud/compute/packet-mirrorings/delete @@ -12,8 +12,7 @@ DESCRIPTION EXAMPLES Delete the Packet Mirroring policy pm-1 in region us-central1. - $ gcloud compute packet-mirrorings delete pm-1 - --region us-central1 + $ gcloud compute packet-mirrorings delete pm-1 --region us-central1 POSITIONAL ARGUMENTS NAME [NAME ...] diff --git a/gcloud/compute/packet-mirrorings/describe b/gcloud/compute/packet-mirrorings/describe index e7abd36d8..c0369e2ba 100644 --- a/gcloud/compute/packet-mirrorings/describe +++ b/gcloud/compute/packet-mirrorings/describe @@ -12,8 +12,7 @@ DESCRIPTION EXAMPLES Describe the Packet Mirroring policy pm-1 in region us-central1. - $ gcloud compute packet-mirrorings describe pm-1 - --region us-central1 + $ gcloud compute packet-mirrorings describe pm-1 --region us-central1 POSITIONAL ARGUMENTS NAME diff --git a/gcloud/compute/packet-mirrorings/update b/gcloud/compute/packet-mirrorings/update index 77aa983b8..7ebf08771 100644 --- a/gcloud/compute/packet-mirrorings/update +++ b/gcloud/compute/packet-mirrorings/update @@ -28,23 +28,23 @@ DESCRIPTION EXAMPLES Stop mirroring by tags, add subnet-1 as a mirrored subnet. - $ gcloud compute packet-mirrorings update my-pm - --region us-central1 --clear-mirrored-tags + $ gcloud compute packet-mirrorings update my-pm \ + --region us-central1 --clear-mirrored-tags \ --add-mirrored-subnets subnet-1 Change the load-balancer to send mirrored traffic to. - $ gcloud compute packet-mirrorings update my-pm + $ gcloud compute packet-mirrorings update my-pm \ --region us-central1 --collector-ilb new-forwarding-rule Disable a Packet Mirroring policy. - $ gcloud compute packet-mirrorings update my-pm + $ gcloud compute packet-mirrorings update my-pm \ --region us-central1 --no-enable Re-enable a disabled Packet Mirroring policy. - $ gcloud compute packet-mirrorings update my-pm + $ gcloud compute packet-mirrorings update my-pm \ --region us-central1 --enable POSITIONAL ARGUMENTS diff --git a/gcloud/compute/public-advertised-prefixes/create b/gcloud/compute/public-advertised-prefixes/create index 67bb397eb..da1ccbbe0 100644 --- a/gcloud/compute/public-advertised-prefixes/create +++ b/gcloud/compute/public-advertised-prefixes/create @@ -12,7 +12,7 @@ EXAMPLES $ gcloud compute public-advertised-prefixes create \ my-public-advertised-prefix --range=120.120.10.0/24 \ - --dns-verification-ip=120.120.10.15 + --dns-verification-ip=120.120.10.15 POSITIONAL ARGUMENTS NAME diff --git a/gcloud/compute/public-delegated-prefixes/create b/gcloud/compute/public-delegated-prefixes/create index 79c18cac9..b0732b533 100644 --- a/gcloud/compute/public-delegated-prefixes/create +++ b/gcloud/compute/public-delegated-prefixes/create @@ -13,7 +13,7 @@ EXAMPLES $ gcloud compute public-delegated-prefixes create \ my-public-delegated-prefix --public-advertised-prefix=my-pap \ - --range=120.120.10.128/27 --global + --range=120.120.10.128/27 --global POSITIONAL ARGUMENTS NAME diff --git a/gcloud/compute/routers/nats/create b/gcloud/compute/routers/nats/create index 31c85a37d..0d269ca41 100644 --- a/gcloud/compute/routers/nats/create +++ b/gcloud/compute/routers/nats/create @@ -25,14 +25,14 @@ DESCRIPTION EXAMPLES Auto-allocate NAT for all IP addresses of all subnets in the region: - $ gcloud compute routers nats create nat1 --router=my-router - --auto-allocate-nat-external-ips --nat-all-subnet-ip-ranges + $ gcloud compute routers nats create nat1 --router=my-router \ + --auto-allocate-nat-external-ips --nat-all-subnet-ip-ranges Specify IP addresses for NAT: Each IP address is the name of a reserved static IP address resource in the same region. - $ gcloud compute routers nats create nat1 --router=my-router - --nat-external-ip-pool=ip-address1,ip-address2 + $ gcloud compute routers nats create nat1 --router=my-router \ + --nat-external-ip-pool=ip-address1,ip-address2 Specify subnet ranges for NAT: @@ -40,9 +40,10 @@ EXAMPLES subnets in the region for the given VPC network. You can restrict which subnet primary and secondary ranges can use NAT. - $ gcloud compute routers nats create nat1 --router=my-router - --auto-allocate-nat-external-ips - --nat-custom-subnet-ip-ranges=subnet-1,subnet-3:secondary-range-1 + $ gcloud compute routers nats create nat1 --router=my-router \ + --auto-allocate-nat-external-ips \ + --nat-custom-subnet-ip-ranges=subnet-1,\ + subnet-3:secondary-range-1 POSITIONAL ARGUMENTS NAME diff --git a/gcloud/compute/routers/nats/rules/create b/gcloud/compute/routers/nats/rules/create index e2c7fbeae..31527e14d 100644 --- a/gcloud/compute/routers/nats/rules/create +++ b/gcloud/compute/routers/nats/rules/create @@ -17,9 +17,9 @@ EXAMPLES the CIDR Range "203.0.113.0/24". $ gcloud compute routers nats rules create 1 --nat=my-nat \ - --router=my-router --region=us-central1 - --match='inIpRange(destination.ip, "203.0.113.0/24")' - --source-nat-active-ips=a1 + --router=my-router --region=us-central1 \ + --match='inIpRange(destination.ip, "203.0.113.0/24")' \ + --source-nat-active-ips=a1 POSITIONAL ARGUMENTS RULE_NUMBER diff --git a/gcloud/compute/routers/nats/rules/update b/gcloud/compute/routers/nats/rules/update index 16af058b7..a7a43eb59 100644 --- a/gcloud/compute/routers/nats/rules/update +++ b/gcloud/compute/routers/nats/rules/update @@ -19,9 +19,9 @@ EXAMPLES new connections matching Rule 1 in NAT nat-1, run: $ gcloud compute routers nats rules update 1 --nat=nat1 \ - --router=my-router --region=us-central1 - --source-nat-drain-ips=address-1 - --source-nat-active-ips=address-2 + --router=my-router --region=us-central1 \ + --source-nat-drain-ips=address-1 \ + --source-nat-active-ips=address-2 POSITIONAL ARGUMENTS RULE_NUMBER diff --git a/gcloud/compute/routers/nats/update b/gcloud/compute/routers/nats/update index bc92e7a6b..599d9ddf6 100644 --- a/gcloud/compute/routers/nats/update +++ b/gcloud/compute/routers/nats/update @@ -32,9 +32,10 @@ DESCRIPTION EXAMPLES Change subnetworks and IP address resources associated with NAT: - $ gcloud compute routers nats update nat1 --router=my-router - --nat-external-ip-pool=ip-address2,ip-address3 - --nat-custom-subnet-ip-ranges=subnet-2,subnet-3:secondary-range-2 + $ gcloud compute routers nats update nat1 --router=my-router \ + --nat-external-ip-pool=ip-address2,ip-address3 \ + --nat-custom-subnet-ip-ranges=subnet-2,\ + subnet-3:secondary-range-2 Change minimum default ports allocated per VM associated with NAT: @@ -43,18 +44,18 @@ EXAMPLES Change connection timeouts associated with NAT: - $ gcloud compute routers nats update nat1 --router=my-router - --udp-mapping-idle-timeout=60s - --icmp-mapping-idle-timeout=60s - --tcp-established-connection-idle-timeout=60s - --tcp-transitory-connection-idle-timeout=60s + $ gcloud compute routers nats update nat1 --router=my-router \ + --udp-mapping-idle-timeout=60s --icmp-mapping-idle-timeout=60s \ + --tcp-established-connection-idle-timeout=60s \ + --tcp-transitory-connection-idle-timeout=60s Reset connection timeouts associated NAT to default values: - $ gcloud compute routers nats update nat1 --router=my-router - --clear-udp-mapping-idle-timeout --clear-icmp-mapping-idle-timeout - --clear-tcp-established-connection-idle-timeout - --clear-tcp-transitory-connection-idle-timeout + $ gcloud compute routers nats update nat1 --router=my-router \ + --clear-udp-mapping-idle-timeout \ + --clear-icmp-mapping-idle-timeout \ + --clear-tcp-established-connection-idle-timeout \ + --clear-tcp-transitory-connection-idle-timeout POSITIONAL ARGUMENTS NAME diff --git a/gcloud/compute/routes/create b/gcloud/compute/routes/create index a04da2dbc..c84459fe9 100644 --- a/gcloud/compute/routes/create +++ b/gcloud/compute/routes/create @@ -41,8 +41,8 @@ EXAMPLES '0.0.0.0/0' and with next hop gateway 'default-internet-gateway', run: $ gcloud compute routes create route-name \ - --destination-range=0.0.0.0/0 \ - --next-hop-gateway=default-internet-gateway + --destination-range=0.0.0.0/0 \ + --next-hop-gateway=default-internet-gateway POSITIONAL ARGUMENTS NAME diff --git a/gcloud/compute/shared-vpc/organizations/list-host-projects b/gcloud/compute/shared-vpc/organizations/list-host-projects index b674dcb42..b9190b821 100644 --- a/gcloud/compute/shared-vpc/organizations/list-host-projects +++ b/gcloud/compute/shared-vpc/organizations/list-host-projects @@ -15,6 +15,7 @@ EXAMPLES run: $ gcloud compute shared-vpc organizations list-host-projects 12345 + NAME CREATION_TIMESTAMP XPN_PROJECT_STATUS xpn-host1 2000-01-01T12:00:00.00-00:00 HOST xpn-host2 2000-01-02T12:00:00.00-00:00 HOST diff --git a/gcloud/compute/tpus/create b/gcloud/compute/tpus/create index 6e6d1fcd9..fe94c7dce 100644 --- a/gcloud/compute/tpus/create +++ b/gcloud/compute/tpus/create @@ -19,12 +19,9 @@ EXAMPLES The following command creates a TPU with ID my-tpu with explicit values for all required and optional parameters: - $ gcloud compute tpus create my-tpu \ - --zone=us-central1-a \ - --range='10.240.0.0/29' \ - --accelerator-type='v2-8' \ - --network=my-tf-network \ - --description='My TF Node' \ + $ gcloud compute tpus create my-tpu --zone=us-central1-a \ + --range='10.240.0.0/29' --accelerator-type='v2-8' \ + --network=my-tf-network --description='My TF Node' \ --version='1.1' POSITIONAL ARGUMENTS diff --git a/gcloud/compute/tpus/execution-groups/create b/gcloud/compute/tpus/execution-groups/create index fabd31d0c..064046f23 100644 --- a/gcloud/compute/tpus/execution-groups/create +++ b/gcloud/compute/tpus/execution-groups/create @@ -17,28 +17,31 @@ EXAMPLES To create both TPU and VM, run: $ gcloud compute tpus execution-groups create \ - --name=test-execution-group --zone=test-zone - --project=test-project --accelerator-type=v2-8 --tf-version=2.4.1 + --name=test-execution-group --zone=test-zone \ + --project=test-project --accelerator-type=v2-8 \ + --tf-version=2.4.1 To create both TPU and VM with additional flags, run: $ gcloud compute tpus execution-groups create \ --name=test-execution-group --zone=test-zone \ - --project=test-project --accelerator-type=v2-8 --tf-version=2.4.1 \ - --network=default --preemptible-vm --disk-size=100 \ - --machine-type=n1-standard-2 --use-dl-images + --project=test-project --accelerator-type=v2-8 \ + --tf-version=2.4.1 --network=default --preemptible-vm \ + --disk-size=100 --machine-type=n1-standard-2 --use-dl-images To create a VM only before creating the TPU, run: $ gcloud compute tpus execution-groups create \ --name=test-execution-group-tpu-only --zone=test-zone \ - --project=test-project --accelerator-type=v2-8 --tf-version=2.4.1 --tpu-only + --project=test-project --accelerator-type=v2-8 \ + --tf-version=2.4.1 --tpu-only To create the TPU only after the VM has been created, run: $ gcloud compute tpus execution-groups create \ --name=test-execution-group-tpu-only --zone=test-zone \ - --project=test-project --accelerator-type=v2-8 --tf-version=2.4.1 --vm-only + --project=test-project --accelerator-type=v2-8 \ + --tf-version=2.4.1 --vm-only FLAGS --accelerator-type=ACCELERATOR_TYPE; default="v2-8" diff --git a/gcloud/compute/tpus/execution-groups/delete b/gcloud/compute/tpus/execution-groups/delete index 2a53ed25d..e4e71f14d 100644 --- a/gcloud/compute/tpus/execution-groups/delete +++ b/gcloud/compute/tpus/execution-groups/delete @@ -15,8 +15,7 @@ EXAMPLES To delete the TPU only, run: $ gcloud compute tpus execution-groups delete test-execution-group \ - --zone=test-zone --project=test-project \ - --tpu-only + --zone=test-zone --project=test-project --tpu-only POSITIONAL ARGUMENTS EXECUTION_GROUP_NAME diff --git a/gcloud/compute/vpn-gateways/update b/gcloud/compute/vpn-gateways/update index 2be5e2f49..dd407abb2 100644 --- a/gcloud/compute/vpn-gateways/update +++ b/gcloud/compute/vpn-gateways/update @@ -32,8 +32,7 @@ EXAMPLES To update labels for a VPN gateway, run: $ gcloud compute vpn-gateways update my-gateway \ - --region=us-central1 \ - --update-labels=k0=value1,k1=value2 + --region=us-central1 --update-labels=k0=value1,k1=value2 POSITIONAL ARGUMENTS NAME diff --git a/gcloud/container/binauthz/attestations/create b/gcloud/container/binauthz/attestations/create index 7e5d4aa3e..86c81c080 100644 --- a/gcloud/container/binauthz/attestations/create +++ b/gcloud/container/binauthz/attestations/create @@ -18,10 +18,9 @@ EXAMPLES To create an attestation in the project "my_proj" as the attestor with resource path "projects/foo/attestors/bar", run: - $ gcloud container binauthz attestations create \ - --project=my_proj \ - --artifact-url='gcr.io/example-project/example-image@sha256:abcd' \ - --attestor=projects/foo/attestors/bar \ + $ gcloud container binauthz attestations create --project=my_proj \ + --artifact-url='gcr.io/example-project/example-image@sha256:abcd\ + ' --attestor=projects/foo/attestors/bar \ --signature-file=signed_artifact_attestation.pgp.sig \ --public-key-id=AAAA0000000000000000FFFFFFFFFFFFFFFFFFFF diff --git a/gcloud/container/binauthz/attestations/list b/gcloud/container/binauthz/attestations/list index 8d0c467c3..37b907c56 100644 --- a/gcloud/container/binauthz/attestations/list +++ b/gcloud/container/binauthz/attestations/list @@ -20,14 +20,14 @@ EXAMPLES attestor: $ gcloud container binauthz attestations list \ - --attestor=projects/foo/attestor/bar + --attestor=projects/foo/attestor/bar List the Occurrence messages for all attestations for the passed artifact-url bound to the passed attestor: $ gcloud container binauthz attestations list \ - --attestor=projects/foo/attestors/bar \ - --artifact-url='gcr.io/foo/example-image@sha256:abcd' + --attestor=projects/foo/attestors/bar \ + --artifact-url='gcr.io/foo/example-image@sha256:abcd' REQUIRED FLAGS Attestor resource - The Attestor whose Container Analysis Note will be diff --git a/gcloud/container/binauthz/attestors/create b/gcloud/container/binauthz/attestors/create index 15e8925d2..a9b6ba1a7 100644 --- a/gcloud/container/binauthz/attestors/create +++ b/gcloud/container/binauthz/attestors/create @@ -10,8 +10,7 @@ SYNOPSIS EXAMPLES To create an Attestor with an existing Note projects/my_proj/notes/my_note: - $ gcloud container binauthz attestors create \ - my_new_attestor + $ gcloud container binauthz attestors create my_new_attestor \ --attestation-authority-note=my_note \ --attestation-authority-note-project=my_proj \ diff --git a/gcloud/container/binauthz/attestors/public-keys/add b/gcloud/container/binauthz/attestors/public-keys/add index 1f60d1513..d84eb8862 100644 --- a/gcloud/container/binauthz/attestors/public-keys/add +++ b/gcloud/container/binauthz/attestors/public-keys/add @@ -18,18 +18,14 @@ EXAMPLES To add a new KMS public key to an existing Attestor my_attestor: $ gcloud container binauthz attestors public-keys add \ - --attestor=my_attestor \ - --keyversion-project=foo \ - --keyversion-location=us-west1 \ - --keyversion-keyring=aring \ - --keyversion-key=akey \ - --keyversion=1 + --attestor=my_attestor --keyversion-project=foo \ + --keyversion-location=us-west1 --keyversion-keyring=aring \ + --keyversion-key=akey --keyversion=1 To add a new PGP public key to an existing Attestor my_attestor: $ gcloud container binauthz attestors public-keys add \ - --attestor=my_attestor \ - --pgp-public-key-file=my_key.pub + --attestor=my_attestor --pgp-public-key-file=my_key.pub REQUIRED FLAGS Attestor resource - The attestor to which the public key should be added. diff --git a/gcloud/container/binauthz/attestors/public-keys/remove b/gcloud/container/binauthz/attestors/public-keys/remove index cf45df99f..f50cfbb95 100644 --- a/gcloud/container/binauthz/attestors/public-keys/remove +++ b/gcloud/container/binauthz/attestors/public-keys/remove @@ -10,8 +10,7 @@ EXAMPLES To remove a public key from the Attestor my_attestor: $ gcloud container binauthz attestors public-keys remove \ - 0638AADD940361EA2D7F14C58C124F0E663DA097 \ - --attestor=my_attestor + 0638AADD940361EA2D7F14C58C124F0E663DA097 --attestor=my_attestor POSITIONAL ARGUMENTS PUBLIC_KEY_ID diff --git a/gcloud/container/binauthz/attestors/public-keys/update b/gcloud/container/binauthz/attestors/public-keys/update index a2efebb1c..88296c2e3 100644 --- a/gcloud/container/binauthz/attestors/public-keys/update +++ b/gcloud/container/binauthz/attestors/public-keys/update @@ -12,8 +12,7 @@ EXAMPLES $ gcloud container binauthz attestors public-keys update \ 0638AADD940361EA2D7F14C58C124F0E663DA097 \ - --attestor=my_attestor \ - --pgp-public-key-file=my_key.pub + --attestor=my_attestor --pgp-public-key-file=my_key.pub POSITIONAL ARGUMENTS PUBLIC_KEY_ID diff --git a/gcloud/container/binauthz/create-signature-payload b/gcloud/container/binauthz/create-signature-payload index fdeacc2a0..bc74825a8 100644 --- a/gcloud/container/binauthz/create-signature-payload +++ b/gcloud/container/binauthz/create-signature-payload @@ -15,7 +15,8 @@ EXAMPLES To output serialized JSON to sign, run: $ gcloud container binauthz create-signature-payload \ - --artifact-url="gcr.io/example-project/example-image@sha256:abcd" + --artifact-url="gcr.io/example-project/example-image@sha256:abcd\ + " REQUIRED FLAGS --artifact-url=ARTIFACT_URL diff --git a/gcloud/container/clusters/create b/gcloud/container/clusters/create index af77c7b45..397be29e9 100644 --- a/gcloud/container/clusters/create +++ b/gcloud/container/clusters/create @@ -19,15 +19,16 @@ SYNOPSIS [--disk-type=DISK_TYPE] [--enable-autorepair] [--no-enable-autoupgrade] [--enable-binauthz] [--enable-cloud-logging] [--enable-cloud-monitoring] [--enable-cloud-run-alpha] - [--enable-dataplane-v2] [--enable-gvnic] [--enable-image-streaming] - [--enable-intra-node-visibility] [--enable-ip-alias] - [--enable-kubernetes-alpha] [--enable-l4-ilb-subsetting] - [--enable-legacy-authorization] [--enable-master-global-access] - [--enable-network-policy] [--enable-service-externalips] - [--enable-shielded-nodes] [--enable-stackdriver-kubernetes] - [--enable-vertical-pod-autoscaling] [--image-type=IMAGE_TYPE] - [--issue-client-certificate] [--labels=[KEY=VALUE,...]] - [--local-ssd-count=LOCAL_SSD_COUNT] [--logging=[COMPONENT,...]] + [--enable-dataplane-v2] [--enable-gvnic] [--enable-identity-service] + [--enable-image-streaming] [--enable-intra-node-visibility] + [--enable-ip-alias] [--enable-kubernetes-alpha] + [--enable-l4-ilb-subsetting] [--enable-legacy-authorization] + [--enable-master-global-access] [--enable-network-policy] + [--enable-service-externalips] [--enable-shielded-nodes] + [--enable-stackdriver-kubernetes] [--enable-vertical-pod-autoscaling] + [--image-type=IMAGE_TYPE] [--issue-client-certificate] + [--labels=[KEY=VALUE,...]] [--local-ssd-count=LOCAL_SSD_COUNT] + [--logging=[COMPONENT,...]] [--machine-type=MACHINE_TYPE, -m MACHINE_TYPE] [--max-nodes-per-pool=MAX_NODES_PER_POOL] [--max-pods-per-node=MAX_PODS_PER_NODE] @@ -369,6 +370,16 @@ FLAGS Enable the use of GVNIC for this cluster. Requires re-creation of nodes using either a node-pool upgrade or node-pool creation. + --enable-identity-service + Enable Identity Service component on the cluster. + + When enabled, users can authenticate to Kubernetes cluster with + external identity providers. + + Identity Service is by default disabled when creating a new cluster. To + disable Identity Service in an existing cluster, explicitly set flag + --no-enable-identity-service. + --enable-image-streaming Specifies whether to enable image streaming on cluster. @@ -615,7 +626,7 @@ FLAGS --monitoring=[COMPONENT,...] Set the components that have monitoring enabled. Valid component values - are: SYSTEM, NONE + are: SYSTEM, WORKLOAD (Deprecated), NONE For more information, look at https://cloud.google.com/stackdriver/docs/solutions/gke/installing#available-metrics diff --git a/gcloud/container/clusters/update b/gcloud/container/clusters/update index 72981769d..344e16213 100644 --- a/gcloud/container/clusters/update +++ b/gcloud/container/clusters/update @@ -10,14 +10,14 @@ SYNOPSIS | --database-encryption-key=DATABASE_ENCRYPTION_KEY | --disable-database-encryption | --disable-default-snat | --disable-workload-identity | --enable-autoscaling - | --enable-binauthz | --enable-image-streaming - | --enable-intra-node-visibility | --enable-l4-ilb-subsetting - | --enable-legacy-authorization | --enable-master-authorized-networks - | --enable-master-global-access | --enable-network-policy - | --enable-service-externalips | --enable-shielded-nodes - | --enable-stackdriver-kubernetes | --enable-vertical-pod-autoscaling - | --generate-password | --maintenance-window=START_TIME - | --node-locations=ZONE,[ZONE,...] + | --enable-binauthz | --enable-identity-service + | --enable-image-streaming | --enable-intra-node-visibility + | --enable-l4-ilb-subsetting | --enable-legacy-authorization + | --enable-master-authorized-networks | --enable-master-global-access + | --enable-network-policy | --enable-service-externalips + | --enable-shielded-nodes | --enable-stackdriver-kubernetes + | --enable-vertical-pod-autoscaling | --generate-password + | --maintenance-window=START_TIME | --node-locations=ZONE,[ZONE,...] | --notification-config=[pubsub=ENABLED|DISABLED, pubsub-topic=TOPIC,...] | --private-ipv6-google-access-type=PRIVATE_IPV6_GOOGLE_ACCESS_TYPE @@ -173,6 +173,16 @@ REQUIRED FLAGS --enable-binauthz Enable Binary Authorization for this cluster. + --enable-identity-service + Enable Identity Service component on the cluster. + + When enabled, users can authenticate to Kubernetes cluster with + external identity providers. + + Identity Service is by default disabled when creating a new cluster. + To disable Identity Service in an existing cluster, explicitly set + flag --no-enable-identity-service. + --enable-image-streaming Specifies whether to enable image streaming on cluster. @@ -823,7 +833,7 @@ REQUIRED FLAGS --monitoring=[COMPONENT,...] Set the components that have monitoring enabled. Valid component - values are: SYSTEM, NONE + values are: SYSTEM, WORKLOAD (Deprecated), NONE For more information, look at https://cloud.google.com/stackdriver/docs/solutions/gke/installing#available-metrics diff --git a/gcloud/container/hub/cloudrun/apply b/gcloud/container/hub/cloudrun/apply index 877d32d96..cd265d716 100644 --- a/gcloud/container/hub/cloudrun/apply +++ b/gcloud/container/hub/cloudrun/apply @@ -15,7 +15,7 @@ EXAMPLES To apply the CloudRun YAML file, run: $ gcloud container hub cloudrun apply \ - --kubeconfig=/path/to/kubeconfig \ + --kubeconfig=/path/to/kubeconfig \ --config=/path/to/cloud-run-cr.yaml REQUIRED FLAGS diff --git a/gcloud/container/hub/ingress/describe b/gcloud/container/hub/ingress/describe index 7625f8773..1be3b970e 100644 --- a/gcloud/container/hub/ingress/describe +++ b/gcloud/container/hub/ingress/describe @@ -7,7 +7,7 @@ SYNOPSIS DESCRIPTION This command describes the status of Multi-cluster Ingress Feature resource - in Hub. + in fleet. EXAMPLES To describe the Ingress Feature, run: diff --git a/gcloud/container/hub/ingress/disable b/gcloud/container/hub/ingress/disable index 5519141db..dae388b12 100644 --- a/gcloud/container/hub/ingress/disable +++ b/gcloud/container/hub/ingress/disable @@ -6,7 +6,7 @@ SYNOPSIS gcloud container hub ingress disable [--force] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - This command disables Multi-cluster Ingress Feature in Hub. + This command disables Multi-cluster Ingress Feature in a fleet. EXAMPLES To disable the Ingress Feature, run: diff --git a/gcloud/container/hub/ingress/enable b/gcloud/container/hub/ingress/enable index e847a72ba..ba3e2725b 100644 --- a/gcloud/container/hub/ingress/enable +++ b/gcloud/container/hub/ingress/enable @@ -6,7 +6,7 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - This command enables Multi-cluster Ingress Feature in Hub. + This command enables Multi-cluster Ingress Feature in a fleet. EXAMPLES To enable the Ingress Feature, run: diff --git a/gcloud/container/hub/ingress/update b/gcloud/container/hub/ingress/update index c4f2afba9..3d415a926 100644 --- a/gcloud/container/hub/ingress/update +++ b/gcloud/container/hub/ingress/update @@ -6,7 +6,7 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - This command updates Multi-cluster Ingress Feature in Hub. + This command updates Multi-cluster Ingress Feature in a fleet. EXAMPLES To update the Ingress Feature, run: diff --git a/gcloud/container/hub/memberships/register b/gcloud/container/hub/memberships/register index bb54fea5e..4647e0dc9 100644 --- a/gcloud/container/hub/memberships/register +++ b/gcloud/container/hub/memberships/register @@ -48,72 +48,72 @@ EXAMPLES kubeconfig file, and install the Connect Agent: $ gcloud container hub memberships register my-cluster \ - --context=my-cluster-context \ - --kubeconfig=/home/user/custom_kubeconfig \ - --service-account-key-file=/tmp/keyfile.json + --context=my-cluster-context \ + --kubeconfig=/home/user/custom_kubeconfig \ + --service-account-key-file=/tmp/keyfile.json Register a non-GKE or GKE On-Prem cluster referenced from the default kubeconfig file, and install the Connect Agent: $ gcloud container hub memberships register my-cluster \ - --context=my-cluster-context \ - --service-account-key-file=/tmp/keyfile.json + --context=my-cluster-context \ + --service-account-key-file=/tmp/keyfile.json Register a non-GKE or GKE On-Prem cluster, and install a specific version of the Connect Agent: $ gcloud container hub memberships register my-cluster \ - --context=my-cluster-context \ - --version=gkeconnect_20190802_02_00 \ - --service-account-key-file=/tmp/keyfile.json + --context=my-cluster-context \ + --version=gkeconnect_20190802_02_00 \ + --service-account-key-file=/tmp/keyfile.json Register a non-GKE or GKE On-Prem cluster and output a manifest that can be used to install the Connect Agent: $ gcloud container hub memberships register my-cluster \ - --context=my-cluster-context \ - --manifest-output-file=/tmp/manifest.yaml \ - --service-account-key-file=/tmp/keyfile.json + --context=my-cluster-context \ + --manifest-output-file=/tmp/manifest.yaml \ + --service-account-key-file=/tmp/keyfile.json Register a GKE cluster referenced from a GKE URI, and install the Connect Agent: $ gcloud container hub memberships register my-cluster \ - --gke-uri=my-cluster-gke-uri \ - --service-account-key-file=/tmp/keyfile.json + --gke-uri=my-cluster-gke-uri \ + --service-account-key-file=/tmp/keyfile.json Register a GKE cluster referenced from a GKE Cluster location and name, and install the Connect Agent: $ gcloud container hub memberships register my-cluster \ - --gke-cluster=my-cluster-region-or-zone/my-cluster \ - --service-account-key-file=/tmp/keyfile.json + --gke-cluster=my-cluster-region-or-zone/my-cluster \ + --service-account-key-file=/tmp/keyfile.json Register a GKE cluster, and install a specific version of the Connect Agent: $ gcloud container hub memberships register my-cluster \ - --gke-uri=my-cluster-gke-uri \ - --version=gkeconnect_20190802_02_00 \ - --service-account-key-file=/tmp/keyfile.json + --gke-uri=my-cluster-gke-uri \ + --version=gkeconnect_20190802_02_00 \ + --service-account-key-file=/tmp/keyfile.json $ gcloud container hub memberships register my-cluster \ - --gke-cluster=my-cluster-region-or-zone/my-cluster \ - --version=gkeconnect_20190802_02_00 \ - --service-account-key-file=/tmp/keyfile.json + --gke-cluster=my-cluster-region-or-zone/my-cluster \ + --version=gkeconnect_20190802_02_00 \ + --service-account-key-file=/tmp/keyfile.json Register a GKE cluster and output a manifest that can be used to install the Connect Agent: $ gcloud container hub memberships register my-cluster \ - --gke-uri=my-cluster-gke-uri \ - --manifest-output-file=/tmp/manifest.yaml \ - --service-account-key-file=/tmp/keyfile.json + --gke-uri=my-cluster-gke-uri \ + --manifest-output-file=/tmp/manifest.yaml \ + --service-account-key-file=/tmp/keyfile.json $ gcloud container hub memberships register my-cluster \ - --gke-cluster=my-cluster-region-or-zone/my-cluster \ - --manifest-output-file=/tmp/manifest.yaml \ - --service-account-key-file=/tmp/keyfile.json + --gke-cluster=my-cluster-region-or-zone/my-cluster \ + --manifest-output-file=/tmp/manifest.yaml \ + --service-account-key-file=/tmp/keyfile.json POSITIONAL ARGUMENTS CLUSTER_NAME diff --git a/gcloud/container/hub/memberships/unregister b/gcloud/container/hub/memberships/unregister index 62c970900..09ba9e168 100644 --- a/gcloud/container/hub/memberships/unregister +++ b/gcloud/container/hub/memberships/unregister @@ -39,8 +39,8 @@ EXAMPLES Unregister a non-GKE cluster referenced from a specific kubeconfig file: $ gcloud container hub memberships unregister my-membership \ - --context=my-cluster-context \ - --kubeconfig=/home/user/custom_kubeconfig + --context=my-cluster-context \ + --kubeconfig=/home/user/custom_kubeconfig Unregister a non-GKE cluster referenced from the default kubeconfig file: @@ -50,12 +50,12 @@ EXAMPLES Unregister a GKE cluster referenced from a GKE URI: $ gcloud container hub memberships unregister my-membership \ - --gke-uri=my-cluster-gke-uri + --gke-uri=my-cluster-gke-uri Unregister a GKE cluster referenced from a GKE Cluster location and name: $ gcloud container hub memberships unregister my-membership \ - --gke-cluster=my-cluster-region-or-zone/my-cluster + --gke-cluster=my-cluster-region-or-zone/my-cluster POSITIONAL ARGUMENTS CLUSTER_NAME diff --git a/gcloud/container/hub/mesh/describe b/gcloud/container/hub/mesh/describe index 59d5a8356..902bb6eee 100644 --- a/gcloud/container/hub/mesh/describe +++ b/gcloud/container/hub/mesh/describe @@ -6,7 +6,7 @@ SYNOPSIS gcloud container hub mesh describe [GCLOUD_WIDE_FLAG ...] DESCRIPTION - Describe the status of Service Mesh Feature resource in Hub. + Describe the status of Service Mesh Feature resource in a fleet. EXAMPLES To describe the Service Mesh Feature, run: diff --git a/gcloud/container/hub/mesh/disable b/gcloud/container/hub/mesh/disable index 1ca33bcb8..f68bdfe80 100644 --- a/gcloud/container/hub/mesh/disable +++ b/gcloud/container/hub/mesh/disable @@ -5,7 +5,7 @@ SYNOPSIS gcloud container hub mesh disable [--force] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - Disable the Service Mesh Feature in Hub. + Disable the Service Mesh Feature in a fleet. EXAMPLES To disable the Service Mesh Feature, run: diff --git a/gcloud/container/hub/mesh/enable b/gcloud/container/hub/mesh/enable index e9a84788d..ab199d42a 100644 --- a/gcloud/container/hub/mesh/enable +++ b/gcloud/container/hub/mesh/enable @@ -5,7 +5,7 @@ SYNOPSIS gcloud container hub mesh enable [GCLOUD_WIDE_FLAG ...] DESCRIPTION - Enable the Service Mesh Feature in Hub. + Enable the Service Mesh Feature in a fleet. EXAMPLES To enable the Service Mesh Feature, run: diff --git a/gcloud/container/hub/multi-cluster-services/describe b/gcloud/container/hub/multi-cluster-services/describe index c7756eeed..1ec73c15f 100644 --- a/gcloud/container/hub/multi-cluster-services/describe +++ b/gcloud/container/hub/multi-cluster-services/describe @@ -7,7 +7,7 @@ SYNOPSIS DESCRIPTION This command gets the detailed status of the Multi-cluster Services Feature - in Hub. + in a fleet. EXAMPLES To describe the Multi-cluster Services Feature, run: diff --git a/gcloud/container/hub/multi-cluster-services/disable b/gcloud/container/hub/multi-cluster-services/disable index fef74588b..22b7fd63b 100644 --- a/gcloud/container/hub/multi-cluster-services/disable +++ b/gcloud/container/hub/multi-cluster-services/disable @@ -7,7 +7,7 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - This command disables the Multi-cluster Services Feature in Hub. + This command disables the Multi-cluster Services Feature in a fleet. EXAMPLES To disable the Multi-cluster Services Feature, run: diff --git a/gcloud/container/hub/multi-cluster-services/enable b/gcloud/container/hub/multi-cluster-services/enable index fa8569a6a..534f67044 100644 --- a/gcloud/container/hub/multi-cluster-services/enable +++ b/gcloud/container/hub/multi-cluster-services/enable @@ -6,7 +6,7 @@ SYNOPSIS gcloud container hub multi-cluster-services enable [GCLOUD_WIDE_FLAG ...] DESCRIPTION - This command enables the Multi-cluster Services Feature in Hub. + This command enables the Multi-cluster Services Feature in a fleet. EXAMPLES To enable the Multi-cluster Services Feature, run: diff --git a/gcloud/container/images/add-tag b/gcloud/container/images/add-tag index 2f23e29be..169c9087e 100644 --- a/gcloud/container/images/add-tag +++ b/gcloud/container/images/add-tag @@ -14,24 +14,24 @@ DESCRIPTION EXAMPLES Add a tag to another tag: - $ gcloud container images add-tag gcr.io/myproject/myimage:mytag1 - gcr.io/myproject/myimage:mytag2 + $ gcloud container images add-tag gcr.io/myproject/myimage:mytag1 \ + gcr.io/myproject/myimage:mytag2 Add a tag to a digest $ gcloud container images add-tag \ - gcr.io/myproject/myimage@sha256:digest - gcr.io/myproject/myimage:mytag2 + gcr.io/myproject/myimage@sha256:digest \ + gcr.io/myproject/myimage:mytag2 Add a tag to latest - $ gcloud container images add-tag gcr.io/myproject/myimage - gcr.io/myproject/myimage:mytag2 + $ gcloud container images add-tag gcr.io/myproject/myimage \ + gcr.io/myproject/myimage:mytag2 Promote a tag to latest - $ gcloud container images add-tag gcr.io/myproject/myimage:mytag1 - gcr.io/myproject/myimage:latest + $ gcloud container images add-tag gcr.io/myproject/myimage:mytag1 \ + gcr.io/myproject/myimage:latest POSITIONAL ARGUMENTS SRC_IMAGE diff --git a/gcloud/container/images/delete b/gcloud/container/images/delete index 368107ebf..4e9b04232 100644 --- a/gcloud/container/images/delete +++ b/gcloud/container/images/delete @@ -29,8 +29,8 @@ EXAMPLES digests that lack tags: $ gcloud container images list-tags \ - [HOSTNAME]/[PROJECT-ID]/[IMAGE] \ - --filter='-tags:*' --format="get(digest)" --limit=$BIG_NUMBER + [HOSTNAME]/[PROJECT-ID]/[IMAGE] --filter='-tags:*' \ + --format="get(digest)" --limit=$BIG_NUMBER Then, delete these tagless images without prompting by running: diff --git a/gcloud/container/images/describe b/gcloud/container/images/describe index 601ac9577..c5c2fdc52 100644 --- a/gcloud/container/images/describe +++ b/gcloud/container/images/describe @@ -9,16 +9,20 @@ EXAMPLES Describe the specified image: $ gcloud container images describe gcr.io/myproject/myimage@digest - OR + + Or: + $ gcloud container images describe gcr.io/myproject/myimage:tag Find the digest for a tag: $ gcloud container images describe gcr.io/myproject/myimage:tag \ - --format="value(image_summary.digest)" - OR + --format="value(image_summary.digest)" + + Or: + $ gcloud container images describe gcr.io/myproject/myimage:tag \ - --format="value(image_summary.fully_qualified_digest)" + --format="value(image_summary.fully_qualified_digest)" POSITIONAL ARGUMENTS IMAGE_NAME diff --git a/gcloud/container/node-pools/create b/gcloud/container/node-pools/create index 8ad5df7fb..d194327a8 100644 --- a/gcloud/container/node-pools/create +++ b/gcloud/container/node-pools/create @@ -305,6 +305,7 @@ FLAGS Multiple locations can be specified, separated by commas. For example: $ gcloud container node-pools create node-pool-1 \ + --cluster=sample-cluster \ --node-locations=us-central1-a,us-central1-b --node-taints=[NODE_TAINT,...] diff --git a/gcloud/container/node-pools/update b/gcloud/container/node-pools/update index 8d3c9c555..984752756 100644 --- a/gcloud/container/node-pools/update +++ b/gcloud/container/node-pools/update @@ -50,6 +50,7 @@ REQUIRED FLAGS example: $ gcloud container node-pools update node-pool-1 \ + --cluster=sample-cluster \ --node-locations=us-central1-a,us-central1-b --system-config-from-file=SYSTEM_CONFIG_FROM_FILE diff --git a/gcloud/container/subnets/list-usable b/gcloud/container/subnets/list-usable index 5c09493ec..afdc46274 100644 --- a/gcloud/container/subnets/list-usable +++ b/gcloud/container/subnets/list-usable @@ -20,15 +20,14 @@ DESCRIPTION EXAMPLES List all subnetworks usable for cluster creation in project my-project. - $ gcloud container subnets list-usable \ - --project=my-project + $ gcloud container subnets list-usable --project=my-project List all subnetworks existing in project my-shared-host-project usable for cluster creation in project my-service-project. $ gcloud container subnets list-usable \ - --project=my-service-project \ - --network-project=my-shared-host-project + --project=my-service-project \ + --network-project=my-shared-host-project FLAGS --network-project=NETWORK_PROJECT diff --git a/gcloud/data-catalog/entries/create b/gcloud/data-catalog/entries/create index 1af746d9e..43106940b 100644 --- a/gcloud/data-catalog/entries/create +++ b/gcloud/data-catalog/entries/create @@ -20,32 +20,33 @@ DESCRIPTION EXAMPLES To create an entry for a Google Cloud Storage fileset, run: - $ gcloud data-catalog entries create entry1 \ - --location=us-central1 --entry-group=group1 \ + $ gcloud data-catalog entries create entry1 --location=us-central1 \ + --entry-group=group1 \ --gcs-file-patterns="gs://bucket1/abc/*,gs://bucket1/file1" \ --display-name="analytics data" type=FILESET To create an entry for a Google Cloud Storage fileset with an inline schema, run: - $ gcloud data-catalog entries create entry1 \ - --location=us-central1 --entry-group=group1 \ - --gcs-file-patterns="gs://bucket1/*" --display-name="sales data" \ + $ gcloud data-catalog entries create entry1 --location=us-central1 \ + --entry-group=group1 --gcs-file-patterns="gs://bucket1/*" \ + --display-name="sales data" \ --schema="qtr=STRING,sales=FLOAT,year=STRING" To create an entry for a resource of a custom type, run: - $ gcloud data-catalog entries create entry1 \ - --location=us-central1 --entry-group=group1 \ - --display-name="sales data" --linked-resource="www.resource.com" \ - --user-specified-type="type_name" --user-specified-system="system_name" + $ gcloud data-catalog entries create entry1 --location=us-central1 \ + --entry-group=group1 --display-name="sales data" \ + --linked-resource="www.resource.com" \ + --user-specified-type="type_name" \ + --user-specified-system="system_name" To create an entry for a Google Cloud Storage fileset with a schema from a file, run: - $ gcloud data-catalog entries create entry1 \ - --location=us-central1 --entry-group=group1 \ - --gcs-file-patterns="gs://bucket1/*" --display-name="sales data" \ + $ gcloud data-catalog entries create entry1 --location=us-central1 \ + --entry-group=group1 --gcs-file-patterns="gs://bucket1/*" \ + --display-name="sales data" \ --schema-from-file=/tmp/schema.json --type=FILESET POSITIONAL ARGUMENTS diff --git a/gcloud/data-catalog/entries/delete b/gcloud/data-catalog/entries/delete index 424749848..a4beec4b0 100644 --- a/gcloud/data-catalog/entries/delete +++ b/gcloud/data-catalog/entries/delete @@ -12,8 +12,8 @@ DESCRIPTION EXAMPLES To delete the entry 'entry1' in the group 'group1', run: - $ gcloud data-catalog entries delete entry1 \ - --entry-group=group1 --location=us-central1 + $ gcloud data-catalog entries delete entry1 --entry-group=group1 \ + --location=us-central1 POSITIONAL ARGUMENTS Entry resource - Entry to delete. The arguments in this group can be used diff --git a/gcloud/data-catalog/entries/describe b/gcloud/data-catalog/entries/describe index 2f9a30a2f..e20f96cd1 100644 --- a/gcloud/data-catalog/entries/describe +++ b/gcloud/data-catalog/entries/describe @@ -12,8 +12,8 @@ DESCRIPTION EXAMPLES To describe the entry 'entry1' in the group 'group1', run: - $ gcloud data-catalog entries describe entry1 \ - --entry-group=group1 --location=us-central1 + $ gcloud data-catalog entries describe entry1 --entry-group=group1 \ + --location=us-central1 POSITIONAL ARGUMENTS Entry resource - Entry to describe. The arguments in this group can be diff --git a/gcloud/data-catalog/entries/star b/gcloud/data-catalog/entries/star index a17fb6a04..9c4187d4e 100644 --- a/gcloud/data-catalog/entries/star +++ b/gcloud/data-catalog/entries/star @@ -12,8 +12,8 @@ DESCRIPTION EXAMPLES To star the entry 'entry1' in the group 'group1', run: - $ gcloud data-catalog entries star entry1 \ - --entry-group=group1 --location=us-central1 + $ gcloud data-catalog entries star entry1 --entry-group=group1 \ + --location=us-central1 POSITIONAL ARGUMENTS Entry resource - Entry to star. The arguments in this group can be used to diff --git a/gcloud/data-catalog/entries/unstar b/gcloud/data-catalog/entries/unstar index 05b4c1343..965bfca4e 100644 --- a/gcloud/data-catalog/entries/unstar +++ b/gcloud/data-catalog/entries/unstar @@ -12,8 +12,8 @@ DESCRIPTION EXAMPLES To unstar the entry 'entry1' in the group 'group1', run: - $ gcloud data-catalog entries unstar entry1 \ - --entry-group=group1 --location=us-central1 + $ gcloud data-catalog entries unstar entry1 --entry-group=group1 \ + --location=us-central1 POSITIONAL ARGUMENTS Entry resource - Entry to unstar. The arguments in this group can be used diff --git a/gcloud/data-catalog/entries/update b/gcloud/data-catalog/entries/update index 4fab493b2..c55be17b5 100644 --- a/gcloud/data-catalog/entries/update +++ b/gcloud/data-catalog/entries/update @@ -22,15 +22,13 @@ DESCRIPTION EXAMPLES To update the schema of a Cloud Pub/Sub entry inline, run: - $ gcloud data-catalog entries update entry1 \ - --location=global --entry-group=@pubsub \ - --schema="column1=type1,column2=type2" + $ gcloud data-catalog entries update entry1 --location=global \ + --entry-group=@pubsub --schema="column1=type1,column2=type2" To update the schema of a Cloud Pub/Sub entry from a file, run: - $ gcloud data-catalog entries update entry1 \ - --location=global --entry-group=@pubsub \ - --schema-from-file="/tmp/schema.json" + $ gcloud data-catalog entries update entry1 --location=global \ + --entry-group=@pubsub --schema-from-file="/tmp/schema.json" To lookup the entry of a Cloud Pub/Sub topic by its SQL name and update its schema in one command, run: diff --git a/gcloud/data-catalog/entry-groups/create b/gcloud/data-catalog/entry-groups/create index be136a3b1..582635edc 100644 --- a/gcloud/data-catalog/entry-groups/create +++ b/gcloud/data-catalog/entry-groups/create @@ -13,8 +13,9 @@ EXAMPLES To create an entry group for some data, run: $ gcloud data-catalog entry-groups create group1 \ - --location=us-central1 --display-name="analytics data - jan 2011" \ - --description="Entries related to January 2011 analytics data." + --location=us-central1 \ + --display-name="analytics data - jan 2011" \ + --description="Entries related to January 2011 analytics data." POSITIONAL ARGUMENTS Entry group resource - Entry group to create. The arguments in this group diff --git a/gcloud/data-catalog/tag-templates/create b/gcloud/data-catalog/tag-templates/create index d2bea8646..81e5d04ef 100644 --- a/gcloud/data-catalog/tag-templates/create +++ b/gcloud/data-catalog/tag-templates/create @@ -29,7 +29,8 @@ EXAMPLES $ gcloud data-catalog tag-templates create TEMPLATE \ --field=id=ID1,display-name=DISPLAY1,type=string \ - --field=id=ID2,display-name=DISPLAY2,type='enum(A|B)',required=TRUE + --field=id=ID2,display-name=DISPLAY2,type='enum(A|B)',\ + required=TRUE POSITIONAL ARGUMENTS Tag template resource - Tag template to create. The arguments in this diff --git a/gcloud/database-migration/migration-jobs/create b/gcloud/database-migration/migration-jobs/create index 500820c9b..ac46282ce 100644 --- a/gcloud/database-migration/migration-jobs/create +++ b/gcloud/database-migration/migration-jobs/create @@ -18,7 +18,7 @@ EXAMPLES To create a migration job with vpc peering connectivity: $ gcloud database-migration migration-jobs create MIGRATION_JOB \ - --region=us-central1 --display-name=my-job --source=cp1 \ + --region=us-central1 --display-name=my-job --source=cp1 \ --destination=cp2 --peer-vpc=network1 POSITIONAL ARGUMENTS diff --git a/gcloud/database-migration/migration-jobs/update b/gcloud/database-migration/migration-jobs/update index 7e9205e6b..7038ecae8 100644 --- a/gcloud/database-migration/migration-jobs/update +++ b/gcloud/database-migration/migration-jobs/update @@ -20,7 +20,7 @@ EXAMPLES destination connection profiles: $ gcloud database-migration migration-jobs update MIGRATION_JOB \ - --region=us-central1 --display-name=new-name --source=new-src \ + --region=us-central1 --display-name=new-name --source=new-src \ --destination=new-dest POSITIONAL ARGUMENTS diff --git a/gcloud/dataflow/flex-template/build b/gcloud/dataflow/flex-template/build index 0877a946f..d4e6cfb11 100644 --- a/gcloud/dataflow/flex-template/build +++ b/gcloud/dataflow/flex-template/build @@ -29,14 +29,14 @@ EXAMPLES To build and store a the flex template json file, run: $ gcloud dataflow flex-template build gs://template-file-gcs-path \ - --image=gcr://image-path \ + --image=gcr://image-path \ --metadata-file=/local/path/to/metadata.json --sdk-language=JAVA - $ gcloud dataflow flex-template build gs://template-file-gcs-path \ - --image-gcr-path=gcr://path-tos-tore-image \ - --jar=path/to/pipeline.jar --jar=path/to/dependency.jar \ - --env=FLEX_TEMPLATE_JAVA_MAIN_CLASS=classpath \ - --flex-template-base-image=JAVA11 \ + $ gcloud dataflow flex-template build gs://template-file-gcs-path \ + --image-gcr-path=gcr://path-tos-tore-image \ + --jar=path/to/pipeline.jar --jar=path/to/dependency.jar \ + --env=FLEX_TEMPLATE_JAVA_MAIN_CLASS=classpath \ + --flex-template-base-image=JAVA11 \ --metadata-file=/local/path/to/metadata.json --sdk-language=JAVA POSITIONAL ARGUMENTS diff --git a/gcloud/dataplex/tasks/add-iam-policy-binding b/gcloud/dataplex/tasks/add-iam-policy-binding index 88321cc58..a58894697 100644 --- a/gcloud/dataplex/tasks/add-iam-policy-binding +++ b/gcloud/dataplex/tasks/add-iam-policy-binding @@ -16,7 +16,7 @@ EXAMPLES location us-central, run: $ gcloud dataplex tasks add-iam-policy-binding test-task \ - --location=us-central1 --lake=test-lake \ + --location=us-central1 --lake=test-lake \ --role=roles/dataplex.viewer --member=user:testuser@gmail.com See https://cloud.google.com/dataplex/docs/iam-roles for details of policy diff --git a/gcloud/dataplex/tasks/create b/gcloud/dataplex/tasks/create index bce42036a..27432e0cd 100644 --- a/gcloud/dataplex/tasks/create +++ b/gcloud/dataplex/tasks/create @@ -47,7 +47,8 @@ EXAMPLES $ gcloud dataplex tasks create test-task --location=us-central1 \ --lake=test-lake \ - --execution-service-account=dataplex-demo-test@test-project.iam.gserviceaccount.com \ + --execution-service-account=dataplex-demo-test@test-project.iam.\ + gserviceaccount.com \ --spark-python-script-file=gs://test-bucket/test-file.py \ --trigger-type=ON_DEMAND @@ -59,9 +60,10 @@ EXAMPLES $ gcloud dataplex tasks create test-task --location=us-central1 \ --lake=test-lake \ - --execution-service-account=dataplex-demo-test@test-project.iam.gserviceaccount.com \ - --spark-python-script-file=gs://test-bucket/test-file.py \ - --trigger-type=RECURRING --trigger-schedule="0 * * * *" + --execution-service-account=dataplex-demo-test@test-project.iam.\ + gserviceaccount.com \ + --spark-python-script-file=gs://test-bucket/test-file.py \ + --trigger-type=RECURRING --trigger-schedule="0 * * * *" POSITIONAL ARGUMENTS Task resource - Arguments and flags that specify the Dataplex Task you diff --git a/gcloud/dataplex/tasks/remove-iam-policy-binding b/gcloud/dataplex/tasks/remove-iam-policy-binding index bcf3c31c9..9cf902b64 100644 --- a/gcloud/dataplex/tasks/remove-iam-policy-binding +++ b/gcloud/dataplex/tasks/remove-iam-policy-binding @@ -16,7 +16,7 @@ EXAMPLES location us-central1, run: $ gcloud dataplex tasks remove-iam-policy-binding test-task \ - --location=us-central1 --lake=test-lake \ + --location=us-central1 --lake=test-lake \ --role=roles/dataplex.viewer --member=user:testuser@gmail.com See https://cloud.google.com/dataplex/docs/iam-roles for details of policy diff --git a/gcloud/dataplex/tasks/update b/gcloud/dataplex/tasks/update index 5d3a3fbf6..be88e9667 100644 --- a/gcloud/dataplex/tasks/update +++ b/gcloud/dataplex/tasks/update @@ -37,8 +37,7 @@ EXAMPLES $ gcloud dataplex tasks update \ projects/test-project/locations/us-central1/lakes/test-lake/\ - tasks/test-task \ - --description='Updated Description' + tasks/test-task --description='Updated Description' POSITIONAL ARGUMENTS Task resource - Arguments and flags that specify the Dataplex Task you diff --git a/gcloud/dataproc/autoscaling-policies/set-iam-policy b/gcloud/dataproc/autoscaling-policies/set-iam-policy index dfcf5853a..179f5887b 100644 --- a/gcloud/dataproc/autoscaling-policies/set-iam-policy +++ b/gcloud/dataproc/autoscaling-policies/set-iam-policy @@ -17,8 +17,8 @@ EXAMPLES 'example-autoscaling-policy' $ gcloud dataproc autoscaling-policies set-iam-policy \ - autoscaling-policies set-iam-policy \ - example-autoscaling-policy policy.json + autoscaling-policies set-iam-policy example-autoscaling-policy \ + policy.json See https://cloud.google.com/iam/docs/managing-policies for details of the policy file format and contents. diff --git a/gcloud/dataproc/batches/submit/pyspark b/gcloud/dataproc/batches/submit/pyspark index 9b5797fc1..5817bbede 100644 --- a/gcloud/dataproc/batches/submit/pyspark +++ b/gcloud/dataproc/batches/submit/pyspark @@ -21,7 +21,7 @@ EXAMPLES To submit a PySpark batch job called "my-batch" that runs "my-pyspark.py", run: - $ gcloud dataproc batches submit pyspark pyspark my-pyspark.py \ + $ gcloud dataproc batches submit pyspark my-pyspark.py \ --batch=my-batch --deps-bucket=gs://my-bucket \ --region=us-central1 --py-files='path/to/my/python/script.py' diff --git a/gcloud/dataproc/jobs/submit/hadoop b/gcloud/dataproc/jobs/submit/hadoop index b606bee52..d70227c1a 100644 --- a/gcloud/dataproc/jobs/submit/hadoop +++ b/gcloud/dataproc/jobs/submit/hadoop @@ -24,8 +24,8 @@ EXAMPLES To submit a Hadoop job that runs a specific class of a jar, run: $ gcloud dataproc jobs submit hadoop --cluster=my_cluster \ - --class=org.my.main.Class \ - --jars=my_jar1.jar,my_jar2.jar -- arg1 arg2 + --class=org.my.main.Class --jars=my_jar1.jar,my_jar2.jar \ + -- arg1 arg2 To submit a Hadoop job that runs a jar that is already on the cluster, run: diff --git a/gcloud/dataproc/jobs/submit/hive b/gcloud/dataproc/jobs/submit/hive index ae5c06dd9..707317244 100644 --- a/gcloud/dataproc/jobs/submit/hive +++ b/gcloud/dataproc/jobs/submit/hive @@ -23,9 +23,9 @@ EXAMPLES To submit a Hive job with inline queries, run: - $ gcloud dataproc jobs submit hive --cluster=my_cluster - -e="CREATE EXTERNAL TABLE foo(bar int) LOCATION 'gs://my_bucket/'" - -e="SELECT * FROM foo WHERE bar > 2" + $ gcloud dataproc jobs submit hive --cluster=my_cluster \ + -e="CREATE EXTERNAL TABLE foo(bar int) LOCATION \ + 'gs://my_bucket/'" -e="SELECT * FROM foo WHERE bar > 2" REQUIRED FLAGS Exactly one of these must be specified: diff --git a/gcloud/dataproc/jobs/submit/pig b/gcloud/dataproc/jobs/submit/pig index 69ebf3e79..517cdbbe2 100644 --- a/gcloud/dataproc/jobs/submit/pig +++ b/gcloud/dataproc/jobs/submit/pig @@ -24,11 +24,11 @@ EXAMPLES To submit a Pig job with inline queries, run: - $ gcloud dataproc jobs submit pig --cluster=my_cluster - -e="LNS = LOAD 'gs://my_bucket/my_file.txt' AS (line)" - -e="WORDS = FOREACH LNS GENERATE FLATTEN(TOKENIZE(line)) AS word" - -e="GROUPS = GROUP WORDS BY word" - -e="WORD_COUNTS = FOREACH GROUPS GENERATE group, COUNT(WORDS)" + $ gcloud dataproc jobs submit pig --cluster=my_cluster \ + -e="LNS = LOAD 'gs://my_bucket/my_file.txt' AS (line)" \ + -e="WORDS = FOREACH LNS GENERATE FLATTEN(TOKENIZE(line)) AS \ + word" -e="GROUPS = GROUP WORDS BY word" \ + -e="WORD_COUNTS = FOREACH GROUPS GENERATE group, COUNT(WORDS)" \ -e="DUMP WORD_COUNTS" REQUIRED FLAGS diff --git a/gcloud/dataproc/jobs/submit/spark b/gcloud/dataproc/jobs/submit/spark index dafc46687..285db1ea5 100644 --- a/gcloud/dataproc/jobs/submit/spark +++ b/gcloud/dataproc/jobs/submit/spark @@ -30,8 +30,7 @@ EXAMPLES To submit a Spark job that runs a jar that is already on the cluster, run: $ gcloud dataproc jobs submit spark --cluster=my_cluster \ - --region=us-central1 \ - --class=org.apache.spark.examples.SparkPi \ + --region=us-central1 --class=org.apache.spark.examples.SparkPi \ --jars=file:///usr/lib/spark/examples/jars/spark-examples.jar \ -- 1000 diff --git a/gcloud/dataproc/jobs/submit/spark-r b/gcloud/dataproc/jobs/submit/spark-r index e9db0072f..523a210e3 100644 --- a/gcloud/dataproc/jobs/submit/spark-r +++ b/gcloud/dataproc/jobs/submit/spark-r @@ -24,8 +24,7 @@ EXAMPLES To submit a Spark job that runs a script already on the cluster, run: $ gcloud dataproc jobs submit spark-r --cluster=my_cluster \ - file:///.../my_script.R \ - -- gs://my_bucket/data.csv + file:///.../my_script.R -- gs://my_bucket/data.csv POSITIONAL ARGUMENTS R_FILE diff --git a/gcloud/dataproc/jobs/submit/spark-sql b/gcloud/dataproc/jobs/submit/spark-sql index c5bf9f950..2ccc9f875 100644 --- a/gcloud/dataproc/jobs/submit/spark-sql +++ b/gcloud/dataproc/jobs/submit/spark-sql @@ -23,9 +23,9 @@ EXAMPLES To submit a Spark SQL job with inline queries, run: - $ gcloud dataproc jobs submit spark-sql --cluster=my_cluster - -e="CREATE EXTERNAL TABLE foo(bar int) LOCATION 'gs://my_bucket/'" - -e="SELECT * FROM foo WHERE bar > 2" + $ gcloud dataproc jobs submit spark-sql --cluster=my_cluster \ + -e="CREATE EXTERNAL TABLE foo(bar int) LOCATION \ + 'gs://my_bucket/'" -e="SELECT * FROM foo WHERE bar > 2" REQUIRED FLAGS Exactly one of these must be specified: diff --git a/gcloud/dataproc/jobs/wait b/gcloud/dataproc/jobs/wait index 4b9658556..ff97e3ec5 100644 --- a/gcloud/dataproc/jobs/wait +++ b/gcloud/dataproc/jobs/wait @@ -17,7 +17,7 @@ EXAMPLES run: $ gcloud dataproc jobs list --format "table(reference.jobId)" \ - --limit 1 --log-http + --limit 1 --log-http To view the output of a job as it runs, run: diff --git a/gcloud/dataproc/workflow-templates/add-job/help b/gcloud/dataproc/workflow-templates/add-job/help index 32d2a1310..c946a0128 100644 --- a/gcloud/dataproc/workflow-templates/add-job/help +++ b/gcloud/dataproc/workflow-templates/add-job/help @@ -9,20 +9,17 @@ EXAMPLES To add a Hadoop MapReduce job, run: $ gcloud dataproc workflow-templates add-job hadoop \ - --workflow-template my_template --jar my_jar.jar \ - -- arg1 arg2 + --workflow-template my_template --jar my_jar.jar -- arg1 arg2 To add a Spark Scala or Java job, run: $ gcloud dataproc workflow-templates add-job spark \ - --workflow-template my_template --jar my_jar.jar \ - -- arg1 arg2 + --workflow-template my_template --jar my_jar.jar -- arg1 arg2 To add a PySpark job, run: $ gcloud dataproc workflow-templates add-job pyspark \ - --workflow-template my_template my_script.py \ - -- arg1 arg2 + --workflow-template my_template my_script.py -- arg1 arg2 To add a Spark SQL job, run: diff --git a/gcloud/dataproc/workflow-templates/help b/gcloud/dataproc/workflow-templates/help index abaaa682c..1f63df540 100644 --- a/gcloud/dataproc/workflow-templates/help +++ b/gcloud/dataproc/workflow-templates/help @@ -47,8 +47,7 @@ EXAMPLES To update cluster selector in a workflow template, run: $ gcloud dataproc workflow-templates set-cluster-selector \ - my_template \ - --cluster-labels environment=prod + my_template --cluster-labels environment=prod GCLOUD WIDE FLAGS These flags are available to all commands: --help. diff --git a/gcloud/debug/logpoints/help b/gcloud/debug/logpoints/help index c3197c3e3..9108e127d 100644 --- a/gcloud/debug/logpoints/help +++ b/gcloud/debug/logpoints/help @@ -17,7 +17,7 @@ EXAMPLES "product" variable whenever any request executes line 123 of the file product.py: - $ gcloud debug logpoints create product.py:123 \ + $ gcloud debug logpoints create product.py:123 \ "No description for {product.name}" The log output will appear wherever explicit logging output from your @@ -27,8 +27,8 @@ EXAMPLES If you want to log output only when certain runtime conditions are met, you can add a "--condition" option: - $ gcloud debug logpoints create product.py:123 \ - "Suspicious price: {product.name} costs {price}" \ + $ gcloud debug logpoints create product.py:123 \ + "Suspicious price: {product.name} costs {price}" \ --condition "price < .50" Logpoints remain active for 24 hours after creation. If you want to disable @@ -41,9 +41,8 @@ EXAMPLES first determine the logpoint ID using the logpoints list command, then delete that specific ID: - $ gcloud debug logpoints list - ID LOCATION ... - 567890abcdef1-1234-56789 product.py:123 ... + $ gcloud debug logpoints list ID LOCATION ... \ + 567890abcdef1-1234-56789 product.py:123 ... $ gcloud debug logpoints delete 567890abcdef1-1234-56789 For App Engine services, logpoint resources include the "logQuery" @@ -51,9 +50,8 @@ EXAMPLES command. You can save this property's value and use it to read logs from the command line: - $ log_query=$(gcloud debug logpoints create product.py:123 \ - "No description for {product.name}" \ - --format="value(logQuery)") + $ log_query=$(gcloud debug logpoints create product.py:123 \ + "No description for {product.name}" --format="value(logQuery)") $ gcloud logging read "$log_query" FLAGS diff --git a/gcloud/deploy/delivery-pipelines/add-iam-policy-binding b/gcloud/deploy/delivery-pipelines/add-iam-policy-binding index 11ecb09a4..abead1bfe 100644 --- a/gcloud/deploy/delivery-pipelines/add-iam-policy-binding +++ b/gcloud/deploy/delivery-pipelines/add-iam-policy-binding @@ -21,10 +21,9 @@ EXAMPLES 'us-central1', run: $ gcloud deploy delivery-pipelines add-iam-policy-binding \ - my-pipeline \ - --region='us-central1' \ - --member='user:test-user@gmail.com' \ - --role='roles/clouddeploy.operator' + my-pipeline --region='us-central1' \ + --member='user:test-user@gmail.com' \ + --role='roles/clouddeploy.operator' POSITIONAL ARGUMENTS Delivery pipeline resource - The delivery pipeline for which to add the diff --git a/gcloud/deploy/delivery-pipelines/remove-iam-policy-binding b/gcloud/deploy/delivery-pipelines/remove-iam-policy-binding index 08617a09c..5e3545af6 100644 --- a/gcloud/deploy/delivery-pipelines/remove-iam-policy-binding +++ b/gcloud/deploy/delivery-pipelines/remove-iam-policy-binding @@ -21,10 +21,9 @@ EXAMPLES 'my-pipeline' with the region 'us-central1', run: $ gcloud deploy delivery-pipelines remove-iam-policy-binding \ - my-pipeline \ - --region='us-central1' \ - --member='user:test-user@gmail.com' \ - --role='roles/clouddeploy.operator' + my-pipeline --region='us-central1' \ + --member='user:test-user@gmail.com' \ + --role='roles/clouddeploy.operator' POSITIONAL ARGUMENTS Delivery pipeline resource - The delivery pipeline for which to remove the diff --git a/gcloud/deploy/targets/add-iam-policy-binding b/gcloud/deploy/targets/add-iam-policy-binding index fa434db69..08e87da64 100644 --- a/gcloud/deploy/targets/add-iam-policy-binding +++ b/gcloud/deploy/targets/add-iam-policy-binding @@ -21,9 +21,8 @@ EXAMPLES 'us-central1', run: $ gcloud deploy targets add-iam-policy-binding my-target \ - --region='us-central1' \ - --member='user:test-user@gmail.com' \ - --role='roles/clouddeploy.operator' + --region='us-central1' --member='user:test-user@gmail.com' \ + --role='roles/clouddeploy.operator' POSITIONAL ARGUMENTS Target resource - The target for which to add the IAM policy binding. The diff --git a/gcloud/deploy/targets/remove-iam-policy-binding b/gcloud/deploy/targets/remove-iam-policy-binding index d1e97e48d..a5fd26c88 100644 --- a/gcloud/deploy/targets/remove-iam-policy-binding +++ b/gcloud/deploy/targets/remove-iam-policy-binding @@ -21,9 +21,8 @@ EXAMPLES 'my-target' with the region 'us-central1', run: $ gcloud deploy targets remove-iam-policy-binding my-target \ - --region='us-central1' \ - --member='user:test-user@gmail.com' \ - --role='roles/clouddeploy.operator' + --region='us-central1' --member='user:test-user@gmail.com' \ + --role='roles/clouddeploy.operator' POSITIONAL ARGUMENTS Target resource - The target for which to remove the IAM policy binding. diff --git a/gcloud/deployment-manager/deployments/create b/gcloud/deployment-manager/deployments/create index a0fe38779..ea0fc207b 100644 --- a/gcloud/deployment-manager/deployments/create +++ b/gcloud/deployment-manager/deployments/create @@ -20,14 +20,14 @@ EXAMPLES To create a new deployment from a top-level template file, run: - $ gcloud deployment-manager deployments create my-deployment \ - --template=template.{jinja|py} \ + $ gcloud deployment-manager deployments create my-deployment \ + --template=template.{jinja|py} \ --properties="string-key:'string-value',integer-key:12345" To create a new deployment directly from a composite type, run: - $ gcloud deployment-manager deployments create my-deployment \ - --composite-type=/composite: \ + $ gcloud deployment-manager deployments create my-deployment \ + --composite-type=/composite: \ --properties="string-key:'string-value',integer-key:12345" To preview a deployment without actually creating resources, run: diff --git a/gcloud/dns/dns-keys/list b/gcloud/dns/dns-keys/list index 66dbd21d1..3508d466a 100644 --- a/gcloud/dns/dns-keys/list +++ b/gcloud/dns/dns-keys/list @@ -16,8 +16,7 @@ EXAMPLES To see the DS records for every key-signing DnsKey in a managed zone, run: $ gcloud dns dns-keys list --zone=my_zone 3 \ - --format='value(ds_record())' \ - --filter='type=keySigning' + --format='value(ds_record())' --filter='type=keySigning' REQUIRED FLAGS --zone=ZONE diff --git a/gcloud/dns/policies/create b/gcloud/dns/policies/create index b732e001c..0f58bcee8 100644 --- a/gcloud/dns/policies/create +++ b/gcloud/dns/policies/create @@ -16,17 +16,15 @@ EXAMPLES To create a new policy with minimal arguments, run: $ gcloud dns policies create mypolicy \ - --description='My new policy test policy 5' \ - --networks='' + --description='My new policy test policy 5' --networks='' To create a new policy with all optional arguments, run: $ gcloud dns policies create mypolicy \ - --description='My new policy test policy 5' \ - --networks=network1,network2 \ - --alternative-name-servers=192.168.1.1,192.168.1.2 \ - --enable-inbound-forwarding \ - --enable-logging + --description='My new policy test policy 5' \ + --networks=network1,network2 \ + --alternative-name-servers=192.168.1.1,192.168.1.2 \ + --enable-inbound-forwarding --enable-logging POSITIONAL ARGUMENTS Policy resource - The policy to create. This represents a Cloud resource. diff --git a/gcloud/dns/record-sets/create b/gcloud/dns/record-sets/create index ba780fe23..caf06fba5 100644 --- a/gcloud/dns/record-sets/create +++ b/gcloud/dns/record-sets/create @@ -16,15 +16,14 @@ EXAMPLES [1.2.3.4, 9.8.7.6] and ttl 60 in my_zone run this: $ gcloud dns record-sets create foo.bar.com. \ - --rrdatas=1.2.3.4,9.8.7.6 --type=A --ttl=60 - --zone=my_zone + --rrdatas=1.2.3.4,9.8.7.6 --type=A --ttl=60 --zone=my_zone To create a record-set with dnsName foo.bar.com., record type A, rrdata [1.2.3.4, 9.8.7.6] and ttl 60 in my_zone in us-east1-a run this: $ gcloud dns record-sets create us-east1-a.bar.com. \ - --rrdatas=1.2.3.4,9.8.7.6 --type=A --ttl=60 - --zone=my_zone --location=us-east1-a + --rrdatas=1.2.3.4,9.8.7.6 --type=A --ttl=60 --zone=my_zone \ + --location=us-east1-a POSITIONAL ARGUMENTS DNS_NAME diff --git a/gcloud/dns/record-sets/export b/gcloud/dns/record-sets/export index b0b9f3eb9..2575c07b1 100644 --- a/gcloud/dns/record-sets/export +++ b/gcloud/dns/record-sets/export @@ -23,7 +23,7 @@ EXAMPLES Similarly, to import record-sets into a BIND zone formatted zone file, run: $ gcloud dns record-sets import pathto.zonefile --zone-file-format \ - --zone=examplezonename + --zone=examplezonename POSITIONAL ARGUMENTS RECORDS_FILE diff --git a/gcloud/dns/record-sets/transaction/add b/gcloud/dns/record-sets/transaction/add index 6b457a482..f25d2bf8b 100644 --- a/gcloud/dns/record-sets/transaction/add +++ b/gcloud/dns/record-sets/transaction/add @@ -19,15 +19,13 @@ EXAMPLES "my.domain.", and a managed zone "MANAGED_ZONE", run: $ gcloud dns record-sets transaction add "1.2.3.4" \ - --name=my.domain. --ttl=1234 \ - --type=A --zone=MANAGED_ZONE + --name=my.domain. --ttl=1234 --type=A --zone=MANAGED_ZONE To add a TXT record with multiple data values while specifying time to live as 14400 seconds, run: $ gcloud dns record-sets transaction add "Hello world" "Bye world" \ - --name=my.domain. --ttl=14400 \ - --type=TXT --zone=MANAGED_ZONE + --name=my.domain. --ttl=14400 --type=TXT --zone=MANAGED_ZONE POSITIONAL ARGUMENTS RRDATAS [RRDATAS ...] diff --git a/gcloud/dns/record-sets/transaction/help b/gcloud/dns/record-sets/transaction/help index 4b5bbb7ec..34793f6fd 100644 --- a/gcloud/dns/record-sets/transaction/help +++ b/gcloud/dns/record-sets/transaction/help @@ -18,8 +18,7 @@ EXAMPLES To append a record-set addition to the transaction, run: $ gcloud dns record-sets transaction add --name RECORD_SET_NAME \ - --ttl TTL --type TYPE DATA \ - --zone=MANAGED_ZONE + --ttl TTL --type TYPE DATA --zone=MANAGED_ZONE To append a record-set removal to the transaction, run: diff --git a/gcloud/dns/record-sets/transaction/remove b/gcloud/dns/record-sets/transaction/remove index 01f6987bf..b96dea33f 100644 --- a/gcloud/dns/record-sets/transaction/remove +++ b/gcloud/dns/record-sets/transaction/remove @@ -15,14 +15,13 @@ EXAMPLES To remove an A record, run: $ gcloud dns record-sets transaction remove --zone=MANAGED_ZONE \ - --name=my.domain. --ttl=1234 \ - --type=A "1.2.3.4" + --name=my.domain. --ttl=1234 --type=A "1.2.3.4" To remove a TXT record with multiple data values, run: $ gcloud dns record-sets transaction remove --zone=MANAGED_ZONE \ - --name=my.domain. --ttl=2345 \ - --type=TXT "Hello world" "Bye world" + --name=my.domain. --ttl=2345 --type=TXT "Hello world" \ + "Bye world" POSITIONAL ARGUMENTS RRDATAS [RRDATAS ...] diff --git a/gcloud/dns/record-sets/update b/gcloud/dns/record-sets/update index 594463051..3c7044ba1 100644 --- a/gcloud/dns/record-sets/update +++ b/gcloud/dns/record-sets/update @@ -16,8 +16,7 @@ EXAMPLES rrdata [1.2.3.4, 9.8.7.6] and ttl 60 in my_zone, run: $ gcloud dns record-sets update foo.bar.com. \ - --rrdatas=1.2.3.4,9.8.7.6 --type=A --ttl=60 - --zone=my_zone + --rrdatas=1.2.3.4,9.8.7.6 --type=A --ttl=60 --zone=my_zone POSITIONAL ARGUMENTS DNS_NAME diff --git a/gcloud/dns/response-policies/create b/gcloud/dns/response-policies/create index 8d3291843..b7795cdf1 100644 --- a/gcloud/dns/response-policies/create +++ b/gcloud/dns/response-policies/create @@ -14,21 +14,19 @@ EXAMPLES To create a new response policy with minimal arguments, run: $ gcloud dns response-policies create myresponsepolicy \ - --description='My new response policy.' - --networks='' + --description='My new response policy.' --networks='' To create a new response policy with all optional arguments, run: $ gcloud dns response-policies create myresponsepolicy \ - --description='My new response policy.' - --networks=network1,network2 + --description='My new response policy.' \ + --networks=network1,network2 To create a new zonal response policy scoped to a GKE cluster in us-central1-a, run (alpha/beta): $ gcloud dns response-policies create beta myresponsepolicy \ --description='My new response - policy.' - --gkeclusters=cluster1 --location=us-central1-a + policy.' --gkeclusters=cluster1 --location=us-central1-a POSITIONAL ARGUMENTS Response policy resource - The response policy to create. This represents diff --git a/gcloud/dns/response-policies/rules/create b/gcloud/dns/response-policies/rules/create index 035359fec..87cfaa2da 100644 --- a/gcloud/dns/response-policies/rules/create +++ b/gcloud/dns/response-policies/rules/create @@ -12,23 +12,24 @@ EXAMPLES To create a new response policy rule with local data rrsets, run: $ gcloud dns response-policies rules create myresponsepolicyrule \ - --response-policy="myresponsepolicy" - --dns-name="www.zone.com." - --local-data=name=www.zone.com.,type=CNAME,ttl=21600,rrdatas=zone.com. + --response-policy="myresponsepolicy" \ + --dns-name="www.zone.com." \ + --local-data=name=www.zone.com.,type=CNAME,ttl=21600,\ + rrdatas=zone.com. To create a new response policy rule with behavior, run: $ gcloud dns response-policies rules create myresponsepolicyrule \ - --response-policy="myresponsepolicy" - --dns-name="www.zone.com." --behavior=bypassResponsePolicy + --response-policy="myresponsepolicy" \ + --dns-name="www.zone.com." --behavior=bypassResponsePolicy To create a new response policy rule with behavior in a zonal response policy in us-east1-a, run: $ gcloud dns response-policies rules create myresponsepolicyrule \ - --response-policy="myresponsepolicy" - --dns-name="www.zone.com." --behavior=bypassResponsePolicy - --location=us-east1-a + --response-policy="myresponsepolicy" \ + --dns-name="www.zone.com." --behavior=bypassResponsePolicy \ + --location=us-east1-a POSITIONAL ARGUMENTS Response policy rule resource - The response policy rule to create. The diff --git a/gcloud/dns/response-policies/rules/help b/gcloud/dns/response-policies/rules/help index 93cd59599..aaa3d3872 100644 --- a/gcloud/dns/response-policies/rules/help +++ b/gcloud/dns/response-policies/rules/help @@ -9,27 +9,28 @@ EXAMPLES To create a new response policy rule with local data rrsets, run: $ gcloud dns response-policies rules myresponsepolicyrule \ - --response-policy="myresponsepolicy" - --dns-name="www.zone.com." - --local-data=name=www.zone.com.,type=CNAME,ttl=21600,rrdatas=zone.com. + --response-policy="myresponsepolicy" \ + --dns-name="www.zone.com." \ + --local-data=name=www.zone.com.,type=CNAME,ttl=21600,\ + rrdatas=zone.com. To create a new response policy rule with behavior, run: $ gcloud dns response-policies rules myresponsepolicyrule \ - --response-policy="myresponsepolicy" - --dns-name="www.zone.com." --behavior=bypassResponsePolicy + --response-policy="myresponsepolicy" \ + --dns-name="www.zone.com." --behavior=bypassResponsePolicy To update a new response policy rule with local data rrsets, run: $ gcloud dns response-policies rules myresponsepolicyrule \ - --response-policy="myresponsepolicy" - --local-data=name=www.zone.com.,type=A,ttl=21600,rrdatas=1.2.3.4 + --response-policy="myresponsepolicy" \ + --local-data=name=www.zone.com.,type=A,ttl=21600,rrdatas=1.2.3.4 To update a new response policy rule with behavior, run: $ gcloud dns response-policies rules myresponsepolicyrule \ - --response-policy="myresponsepolicy" - --behavior=bypassResponsePolicy + --response-policy="myresponsepolicy" \ + --behavior=bypassResponsePolicy GCLOUD WIDE FLAGS These flags are available to all commands: --help. diff --git a/gcloud/dns/response-policies/rules/update b/gcloud/dns/response-policies/rules/update index 4f8761992..16d6e1b59 100644 --- a/gcloud/dns/response-policies/rules/update +++ b/gcloud/dns/response-policies/rules/update @@ -15,20 +15,20 @@ EXAMPLES To update a new response policy rule with DNS name, run: $ gcloud dns response-policies rules update myresponsepolicyrule \ - --response-policy="myresponsepolicy" - --dns-name="www.newzone.com." # pylint: disable=line-too-long + --response-policy="myresponsepolicy" \ + --dns-name="www.newzone.com." # pylint: disable=line-too-long To update a new response policy rule with local data rrsets, run: $ gcloud dns response-policies rules update myresponsepolicyrule \ - --response-policy="myresponsepolicy" - --local-data=name=www.zone.com.,type=A,ttl=21600,rrdatas=1.2.3.4 + --response-policy="myresponsepolicy" \ + --local-data=name=www.zone.com.,type=A,ttl=21600,rrdatas=1.2.3.4 To update a new response policy rule with behavior, run: $ gcloud dns response-policies rules update myresponsepolicyrule \ - --response-policy="myresponsepolicy" - --behavior=bypassResponsePolicy + --response-policy="myresponsepolicy" \ + --behavior=bypassResponsePolicy POSITIONAL ARGUMENTS Response policy rule resource - The response policy rule to update. The diff --git a/gcloud/dns/response-policies/update b/gcloud/dns/response-policies/update index c5280ee79..3e0cbaa86 100644 --- a/gcloud/dns/response-policies/update +++ b/gcloud/dns/response-policies/update @@ -13,21 +13,20 @@ EXAMPLES To update a response policy with minimal arguments, run: $ gcloud dns response-policies update myresponsepolicy \ - --description='My updated response policy.' - --networks='' + --description='My updated response policy.' --networks='' To update a response policy with all optional arguments, run: $ gcloud dns response-policies update myresponsepolicy \ - --description='My updated response policy.' - --networks=network1,network2 + --description='My updated response policy.' \ + --networks=network1,network2 To update a new zonal response policy scoped to a GKE cluster in us-central1-a, run: $ gcloud dns response-policies update myresponsepolicy \ - --description='My new response policy.' - --gkeclusters=cluster1 --location=us-central1-a + --description='My new response policy.' --gkeclusters=cluster1 \ + --location=us-central1-a POSITIONAL ARGUMENTS Response policy resource - The response policy to update. This represents diff --git a/gcloud/endpoints/services/add-iam-policy-binding b/gcloud/endpoints/services/add-iam-policy-binding index 1209fa766..605f0085f 100644 --- a/gcloud/endpoints/services/add-iam-policy-binding +++ b/gcloud/endpoints/services/add-iam-policy-binding @@ -27,8 +27,8 @@ EXAMPLES 'my-service', run: $ gcloud endpoints services add-iam-policy-binding my-service \ - --member='serviceAccount:my-iam-account@my-project.iam.gserviceaccount.com' \ - --role='roles/servicemanagement.serviceConsumer' + --member='serviceAccount:my-iam-account@my-project.iam.gservicea\ + ccount.com' --role='roles/servicemanagement.serviceConsumer' See https://cloud.google.com/iam/docs/managing-policies for details of policy role and member types. diff --git a/gcloud/essential-contacts/compute b/gcloud/essential-contacts/compute index 3706f9fd5..b679214c0 100644 --- a/gcloud/essential-contacts/compute +++ b/gcloud/essential-contacts/compute @@ -25,8 +25,7 @@ EXAMPLES for the folder with id 123, run: $ gcloud essential-contacts compute \ - --notification-categories=product-updates,billing - --folder=123 + --notification-categories=product-updates,billing --folder=123 To compute contacts subscribed to the legal category for the organization with id 456, run: diff --git a/gcloud/essential-contacts/create b/gcloud/essential-contacts/create index b1e105105..c57c4d838 100644 --- a/gcloud/essential-contacts/create +++ b/gcloud/essential-contacts/create @@ -10,20 +10,24 @@ SYNOPSIS EXAMPLES To create a contact in the current project, run: - $ gcloud essential-contacts create --email=contact-email@example.com - --notification-categories=technical,product-updates --language=en-US + $ gcloud essential-contacts create \ + --email=contact-email@example.com \ + --notification-categories=technical,product-updates \ + --language=en-US To create a contact in the folder with id 456, run: - $ gcloud essential-contacts create --email=contact-email@example.com - --notification-categories=technical,product-updates --language=en-US - --folder=456 + $ gcloud essential-contacts create \ + --email=contact-email@example.com \ + --notification-categories=technical,product-updates \ + --language=en-US --folder=456 To create a contact in the organization with id 456, run: - $ gcloud essential-contacts create --email=contact-email@example.com - --notification-categories=technical,product-updates --language=en-US - --organization=456 + $ gcloud essential-contacts create \ + --email=contact-email@example.com \ + --notification-categories=technical,product-updates \ + --language=en-US --organization=456 REQUIRED FLAGS --email=EMAIL diff --git a/gcloud/essential-contacts/update b/gcloud/essential-contacts/update index 547511133..32e812196 100644 --- a/gcloud/essential-contacts/update +++ b/gcloud/essential-contacts/update @@ -23,7 +23,7 @@ EXAMPLES for the contact with id 123 in the organization with id 456, run: $ gcloud essential-contacts update 123 \ - --notification-categories=legal --language=en-US + --notification-categories=legal --language=en-US \ --organization=456 POSITIONAL ARGUMENTS diff --git a/gcloud/filestore/instances/restore b/gcloud/filestore/instances/restore index f39697cbb..7898fe7ff 100644 --- a/gcloud/filestore/instances/restore +++ b/gcloud/filestore/instances/restore @@ -17,10 +17,8 @@ EXAMPLES 'my-backup' in the region europe-west3. $ gcloud filestore instances restore my-instance \ - --zone=europe-west3-a \ - --file-share=vol1 \ - --source-backup=my-backup \ - --source-backup-region=europe-west3 + --zone=europe-west3-a --file-share=vol1 \ + --source-backup=my-backup --source-backup-region=europe-west3 POSITIONAL ARGUMENTS Instance resource - Arguments and flags that specify the Filestore diff --git a/gcloud/filestore/instances/update b/gcloud/filestore/instances/update index 1b6d4ca58..bd850d261 100644 --- a/gcloud/filestore/instances/update +++ b/gcloud/filestore/instances/update @@ -53,7 +53,7 @@ EXAMPLES capacity to CAPACITY. $ gcloud filestore instances update NAME --project=PROJECT_ID \ - --zone=ZONE --file-share=name=VOLUME_NAME,capacity=CAPACITY + --zone=ZONE --file-share=name=VOLUME_NAME,capacity=CAPACITY POSITIONAL ARGUMENTS Instance resource - The instance to update. The arguments in this group diff --git a/gcloud/firestore/indexes/fields/list b/gcloud/firestore/indexes/fields/list index 3e246140f..60ad5dbe6 100644 --- a/gcloud/firestore/indexes/fields/list +++ b/gcloud/firestore/indexes/fields/list @@ -25,9 +25,10 @@ EXAMPLES The following command lists the indexes of all fields with custom index settings: - $ gcloud firestore indexes fields list --format="table[box](\ - name,indexConfig.indexes:format='table[title=INDEXES,box](\ - fields.order.flatten(),fields.arrayConfig.flatten(),queryScope,state)')" + $ gcloud firestore indexes fields list \ + --format="table[box](name,indexConfig.indexes:format='table[titl\ + e=INDEXES,box](fields.order.flatten(),fields.arrayConfig.flatten(),q\ + ueryScope,state)')" FLAGS Collection group resource - Collection group of the index. diff --git a/gcloud/firestore/indexes/fields/update b/gcloud/firestore/indexes/fields/update index 19b362743..8845e30a6 100644 --- a/gcloud/firestore/indexes/fields/update +++ b/gcloud/firestore/indexes/fields/update @@ -20,16 +20,14 @@ EXAMPLES Events collection group, in which all indexes are disabled: $ gcloud firestore indexes fields update timestamp \ - --collection-group=Events - --disable-indexes + --collection-group=Events --disable-indexes The following command creates an exemption for the timestamp field in the Events collection group, in which the list of indexes is explicitly set to [ASCENDING, DESCENDING]: $ gcloud firestore indexes fields update timestamp \ - --collection-group=Events \ - --index=order=ASCENDING \ + --collection-group=Events --index=order=ASCENDING \ --index=order=DESCENDING The following command clears the exemption on the timestamp field in the diff --git a/gcloud/functions/deploy b/gcloud/functions/deploy index 947378751..6742d032b 100644 --- a/gcloud/functions/deploy +++ b/gcloud/functions/deploy @@ -408,28 +408,27 @@ FLAGS We recommend referencing the latest version when using secret volumes so that the secret's value changes are reflected immediately. - Only `--update-secrets` and `--remove-secrets` can be used together. If - both are specified, then `--remove-secrets` will be applied first. + Only --update-secrets and --remove-secrets can be used together. If both + are specified, then --remove-secrets will be applied first. - --remove-secrets=[SECRET_ENV_VAR,/secret_path,/mount_path:/secret_file_path,...] - List of secret environment variable names and secret paths to - remove. + --remove-secrets=[SECRET_ENV_VAR,/secret_path,/mount_path:/secret_file_path,...] + List of secret environment variable names and secret paths to + remove. - Existing secrets configuration of secret environment variable - names and secret paths not specified in this list will be - preserved. + Existing secrets configuration of secret environment variable names + and secret paths not specified in this list will be preserved. - To remove a secret environment variable, use the name of the - environment variable SECRET_ENV_VAR. + To remove a secret environment variable, use the name of the + environment variable SECRET_ENV_VAR. - To remove a file within a secret volume or the volume itself, use - the secret path as the key (either /secret_path or - /mount_path:/secret_file_path). + To remove a file within a secret volume or the volume itself, use + the secret path as the key (either /secret_path or + /mount_path:/secret_file_path). - --update-secrets=[SECRET_ENV_VAR=SECRET_VALUE_REF,/secret_path=SECRET_VALUE_REF,/mount_path:/secret_file_path=SECRET_VALUE_REF,...] - List of secret environment variables and secret volumes to - update. Existing secrets configuration not specified in this list - will be preserved. + --update-secrets=[SECRET_ENV_VAR=SECRET_VALUE_REF,/secret_path=SECRET_VALUE_REF,/mount_path:/secret_file_path=SECRET_VALUE_REF,...] + List of secret environment variables and secret volumes to update. + Existing secrets configuration not specified in this list will be + preserved. At most one of these can be specified: diff --git a/gcloud/game/servers/clusters/create b/gcloud/game/servers/clusters/create index 6d96c7efd..bc15d547a 100644 --- a/gcloud/game/servers/clusters/create +++ b/gcloud/game/servers/clusters/create @@ -17,16 +17,18 @@ EXAMPLES $ gcloud game servers clusters create my-cluster \ --project=my-project --realm=my-realm --location=my-location \ - --gke-cluster=projects/my-project/locations/my-location/clusters/my-gke-cluster \ - --namespace=default --labels=a=x,b=y --no-dry-run + --gke-cluster=projects/my-project/locations/my-location/\ + clusters/my-gke-cluster --namespace=default --labels=a=x,b=y \ + --no-dry-run To preview Game Server Cluster creation for 'my-cluster' in project 'my-project', realm 'my-realm', and location in 'my-location' run: $ gcloud game servers clusters create my-cluster \ --project=my-project --realm=my-realm --location=my-location \ - --gke-cluster=projects/my-project/locations/my-location/clusters/my-gke-cluster \ - --namespace=default --labels=a=x,b=y --dry-run + --gke-cluster=projects/my-project/locations/my-location/\ + clusters/my-gke-cluster --namespace=default --labels=a=x,b=y \ + --dry-run POSITIONAL ARGUMENTS Game server cluster resource - Cloud Game Server Cluster to create. The diff --git a/gcloud/game/servers/clusters/update b/gcloud/game/servers/clusters/update index cdd77e00e..d3ac2f92f 100644 --- a/gcloud/game/servers/clusters/update +++ b/gcloud/game/servers/clusters/update @@ -17,14 +17,14 @@ EXAMPLES $ gcloud game servers clusters update my-cluster \ --project=my-project --realm=my-realm --location=my-location \ - --update-labels="key1=val1" --no-dry-run + --update-labels="key1=val1" --no-dry-run To preview Game Server Cluster label update for 'my-cluster' in project 'my-project', realm 'my-realm', and location in 'my-location' run: $ gcloud game servers clusters update my-cluster \ --project=my-project --realm=my-realm --location=my-location \ - --update-labels="key1=val1" --dry-run + --update-labels="key1=val1" --dry-run POSITIONAL ARGUMENTS Game server cluster resource - Cloud Game Server Cluster to update. The diff --git a/gcloud/game/servers/configs/create b/gcloud/game/servers/configs/create index 285dc9b0f..ff43c1edc 100644 --- a/gcloud/game/servers/configs/create +++ b/gcloud/game/servers/configs/create @@ -18,8 +18,8 @@ EXAMPLES $ gcloud game servers configs create my-config \ --project=my-project --deployment=my-deployment \ - --location=global \ - --deployment=my-deployment --description=description --labels=a=x,b=y \ + --location=global --deployment=my-deployment \ + --description=description --labels=a=x,b=y \ --fleet-configs-file=fleet_configs.json POSITIONAL ARGUMENTS diff --git a/gcloud/game/servers/deployments/create b/gcloud/game/servers/deployments/create index 46b01f780..4fe70ab14 100644 --- a/gcloud/game/servers/deployments/create +++ b/gcloud/game/servers/deployments/create @@ -16,8 +16,7 @@ EXAMPLES $ gcloud game servers deployments create my-deployment \ --project=my-project --location=global \ - --description=description \ - --labels=a=x,b=y + --description=description --labels=a=x,b=y POSITIONAL ARGUMENTS Deployment resource - Cloud Game Server Deployment to create. The diff --git a/gcloud/iam/list-grantable-roles b/gcloud/iam/list-grantable-roles index aa1d90e95..fd025a6e7 100644 --- a/gcloud/iam/list-grantable-roles +++ b/gcloud/iam/list-grantable-roles @@ -25,7 +25,8 @@ EXAMPLES List grantable roles for a resource identified via URI: $ gcloud iam list-grantable-roles \ - https://www.googleapis.com/compute/v1/projects/example-project/zones/us-central1-f/instances/example-instance + https://www.googleapis.com/compute/v1/projects/example-project/\ + zones/us-central1-f/instances/example-instance POSITIONAL ARGUMENTS RESOURCE diff --git a/gcloud/iam/workload-identity-pools/create b/gcloud/iam/workload-identity-pools/create index b2b4f1599..233739061 100644 --- a/gcloud/iam/workload-identity-pools/create +++ b/gcloud/iam/workload-identity-pools/create @@ -17,11 +17,9 @@ EXAMPLES all required and optional parameters are provided. $ gcloud iam workload-identity-pools create \ - my-workload-identity-pool \ - --location="global" \ + my-workload-identity-pool --location="global" \ --display-name="My workload pool" \ - --description="My workload pool description" \ - --disabled + --description="My workload pool description" --disabled POSITIONAL ARGUMENTS Workload identity pool resource - The workload identity pool to create. diff --git a/gcloud/iam/workload-identity-pools/providers/create-aws b/gcloud/iam/workload-identity-pools/providers/create-aws index 2aef079f5..68e240eb5 100644 --- a/gcloud/iam/workload-identity-pools/providers/create-aws +++ b/gcloud/iam/workload-identity-pools/providers/create-aws @@ -20,15 +20,12 @@ EXAMPLES Explicit values for all required and optional parameters are provided. $ gcloud iam workload-identity-pools providers create-aws \ - my-workload-identity-pool-provider \ - --location="global" \ + my-workload-identity-pool-provider --location="global" \ --workload-identity-pool="my-workload-identity-pool" \ --display-name="My workload pool provider" \ --description="My workload pool provider description" \ - --disabled \ - --attribute-mapping="google.subject=assertion.arn" \ - --attribute-condition="true" \ - --account-id=1234567890 + --disabled --attribute-mapping="google.subject=assertion.arn" \ + --attribute-condition="true" --account-id=1234567890 POSITIONAL ARGUMENTS Workload identity pool provider resource - The workload identity pool diff --git a/gcloud/iam/workload-identity-pools/providers/create-oidc b/gcloud/iam/workload-identity-pools/providers/create-oidc index cebfb121f..3a1509d4f 100644 --- a/gcloud/iam/workload-identity-pools/providers/create-oidc +++ b/gcloud/iam/workload-identity-pools/providers/create-oidc @@ -20,16 +20,15 @@ EXAMPLES Explicit values for all required and optional parameters are provided. $ gcloud iam workload-identity-pools providers create-oidc \ - my-workload-identity-pool-provider \ - --location="global" \ + my-workload-identity-pool-provider --location="global" \ --workload-identity-pool="my-workload-identity-pool" \ --display-name="My workload pool provider" \ --description="My workload pool provider description" \ - --disabled \ - --attribute-mapping="google.subject=assertion.sub" \ + --disabled --attribute-mapping="google.subject=assertion.sub" \ --attribute-condition="true" \ --issuer-uri="https://test-idp.com" \ - --allowed-audiences=https://test-audience-1.com,https://test-audience-2.com + --allowed-audiences=https://test-audience-1.com,https://\ + test-audience-2.com POSITIONAL ARGUMENTS Workload identity pool provider resource - The workload identity pool diff --git a/gcloud/iam/workload-identity-pools/providers/delete b/gcloud/iam/workload-identity-pools/providers/delete index 21372996d..46edff238 100644 --- a/gcloud/iam/workload-identity-pools/providers/delete +++ b/gcloud/iam/workload-identity-pools/providers/delete @@ -17,8 +17,8 @@ EXAMPLES $ gcloud iam workload-identity-pools providers delete \ my-workload-identity-pool-provider \ - --workload-identity-pool="my-workload-identity-pool" \ - --location="global" + --workload-identity-pool="my-workload-identity-pool" \ + --location="global" POSITIONAL ARGUMENTS Workload identity pool provider resource - The workload identity pool diff --git a/gcloud/iam/workload-identity-pools/providers/describe b/gcloud/iam/workload-identity-pools/providers/describe index 8891ad68a..2597188b2 100644 --- a/gcloud/iam/workload-identity-pools/providers/describe +++ b/gcloud/iam/workload-identity-pools/providers/describe @@ -16,9 +16,9 @@ EXAMPLES the ID my-workload-identity-pool-provider: $ gcloud iam workload-identity-pools providers describe \ - my-workload-identity-pool-provider \ - --workload-identity-pool="my-workload-identity-pool" \ - --location="global" + my-workload-identity-pool-provider \ + --workload-identity-pool="my-workload-identity-pool" \ + --location="global" POSITIONAL ARGUMENTS Workload identity pool provider resource - The workload identity pool diff --git a/gcloud/iam/workload-identity-pools/providers/list b/gcloud/iam/workload-identity-pools/providers/list index c639669e0..c24800014 100644 --- a/gcloud/iam/workload-identity-pools/providers/list +++ b/gcloud/iam/workload-identity-pools/providers/list @@ -15,10 +15,9 @@ EXAMPLES The following command lists all workload identity pool providers in the workload identity pool, including soft-deleted providers: - $ gcloud iam workload-identity-pools providers list \ - --workload-identity-pool="my-workload-identity-pool" \ - --location="global" \ - --show-deleted + $ gcloud iam workload-identity-pools providers list \ + --workload-identity-pool="my-workload-identity-pool" \ + --location="global" --show-deleted REQUIRED FLAGS Workload identity pool resource - The location to list workload identity diff --git a/gcloud/iam/workload-identity-pools/providers/operations/describe b/gcloud/iam/workload-identity-pools/providers/operations/describe index 6497b8c93..96c4c6e45 100644 --- a/gcloud/iam/workload-identity-pools/providers/operations/describe +++ b/gcloud/iam/workload-identity-pools/providers/operations/describe @@ -18,8 +18,7 @@ EXAMPLES $ gcloud iam workload-identity-pools providers operations describe \ my-operation \ --workload-identity-pool="my-workload-identity-pool" \ - --provider="my-provider" \ - --location="global" + --provider="my-provider" --location="global" POSITIONAL ARGUMENTS Workload identity pool provider operation resource - The workload identity diff --git a/gcloud/iam/workload-identity-pools/providers/undelete b/gcloud/iam/workload-identity-pools/providers/undelete index 22916ecf5..ceae59d3d 100644 --- a/gcloud/iam/workload-identity-pools/providers/undelete +++ b/gcloud/iam/workload-identity-pools/providers/undelete @@ -17,8 +17,8 @@ EXAMPLES $ gcloud iam workload-identity-pools providers undelete \ my-workload-identity-pool-provider \ - --workload-identity-pool="my-workload-identity-pool" \ - --location="global" + --workload-identity-pool="my-workload-identity-pool" \ + --location="global" POSITIONAL ARGUMENTS Workload identity pool provider resource - The workload identity pool diff --git a/gcloud/iam/workload-identity-pools/providers/update-aws b/gcloud/iam/workload-identity-pools/providers/update-aws index 821bbb5ab..c269b80fa 100644 --- a/gcloud/iam/workload-identity-pools/providers/update-aws +++ b/gcloud/iam/workload-identity-pools/providers/update-aws @@ -24,10 +24,8 @@ EXAMPLES --workload-identity-pool="my-workload-identity-pool" \ --display-name="My workload pool provider" \ --description="My workload pool provider description" \ - --disabled \ - --attribute-mapping="google.subject=assertion.arn" \ - --attribute-condition="true" \ - --account-id=1234567890 + --disabled --attribute-mapping="google.subject=assertion.arn" \ + --attribute-condition="true" --account-id=1234567890 POSITIONAL ARGUMENTS Workload identity pool provider resource - The workload identity pool diff --git a/gcloud/iam/workload-identity-pools/providers/update-oidc b/gcloud/iam/workload-identity-pools/providers/update-oidc index a76205b47..1adf1e4e3 100644 --- a/gcloud/iam/workload-identity-pools/providers/update-oidc +++ b/gcloud/iam/workload-identity-pools/providers/update-oidc @@ -21,16 +21,15 @@ EXAMPLES and optional parameters are provided: $ gcloud iam workload-identity-pools providers update-oidc \ - my-workload-identity-pool-provider \ - --location="global" \ + my-workload-identity-pool-provider --location="global" \ --workload-identity-pool="my-workload-identity-pool" \ --display-name="My workload pool provider" \ --description="My workload pool provider description" \ - --disabled \ - --attribute-mapping="google.subject=assertion.sub" \ + --disabled --attribute-mapping="google.subject=assertion.sub" \ --attribute-condition="true" \ - --issuer-uri="https://test-idp.com" - --allowed-audiences=https://test-audience-1.com,https://test-audience-2.com + --issuer-uri="https://test-idp.com" \ + --allowed-audiences=https://test-audience-1.com,https://\ + test-audience-2.com POSITIONAL ARGUMENTS Workload identity pool provider resource - The workload identity pool diff --git a/gcloud/iam/workload-identity-pools/update b/gcloud/iam/workload-identity-pools/update index 0405f8039..10db2e6ee 100644 --- a/gcloud/iam/workload-identity-pools/update +++ b/gcloud/iam/workload-identity-pools/update @@ -15,11 +15,9 @@ EXAMPLES my-workload-identity-pool: $ gcloud iam workload-identity-pools update \ - my-workload-identity-pool \ - --location="global" + my-workload-identity-pool --location="global" \ --display-name="My workload pool" \ - --description="My workload pool description" \ - --disabled + --description="My workload pool description" --disabled POSITIONAL ARGUMENTS Workload identity pool resource - The workload identity pool to update. diff --git a/gcloud/iap/settings/get b/gcloud/iap/settings/get index 94206e749..eab7b9301 100644 --- a/gcloud/iap/settings/get +++ b/gcloud/iap/settings/get @@ -42,7 +42,7 @@ EXAMPLES run: $ gcloud iap settings get --project=PROJECT_ID \ - --resource-type=app-engine --service=SERVICE_ID + --resource-type=app-engine --service=SERVICE_ID \ --version=VERSION_ID To get the IAP setting for all backend services within a project, run: diff --git a/gcloud/iap/settings/set b/gcloud/iap/settings/set index 9357800fb..e214bbd97 100644 --- a/gcloud/iap/settings/set +++ b/gcloud/iap/settings/set @@ -42,7 +42,7 @@ EXAMPLES run: $ gcloud iap settings set SETTING_FILE --project=PROJECT_ID \ - --resource-type=app-engine --service=SERVICE_ID + --resource-type=app-engine --service=SERVICE_ID \ --version=VERSION_ID To set the IAP setting for all backend services within a project, run: diff --git a/gcloud/iap/web/add-iam-policy-binding b/gcloud/iap/web/add-iam-policy-binding index 0bfc1cee6..c02ae6f97 100644 --- a/gcloud/iap/web/add-iam-policy-binding +++ b/gcloud/iap/web/add-iam-policy-binding @@ -23,16 +23,14 @@ EXAMPLES $ gcloud iap web add-iam-policy-binding \ --resource-type=IAP_IAM_RESOURCE \ - --member='user:test-user@gmail.com' - --role='roles/editor' + --member='user:test-user@gmail.com' --role='roles/editor' To add an IAM policy binding for the role of 'roles/editor' for all authenticated users on IAP IAM resource IAP_IAM_RESOURCE, run: $ gcloud iap web add-iam-policy-binding \ --resource-type=IAP_IAM_RESOURCE \ - --member='allAuthenticatedUsers' - --role='roles/editor' + --member='allAuthenticatedUsers' --role='roles/editor' To add an IAM policy binding which expires at the end of the year 2018 for the role of 'roles/browser' and the user 'test-user@gmail.com' on IAP IAM @@ -40,8 +38,8 @@ EXAMPLES $ gcloud iap web add-iam-policy-binding \ --resource-type=IAP_IAM_RESOURCE \ - --member='user:test-user@gmail.com' - --role='roles/browser' --condition='expression=request.time < + --member='user:test-user@gmail.com' --role='roles/browser' \ + --condition='expression=request.time < timestamp("2019-01-01T00:00:00Z"),title=expires_end_of_2018, description=Expires at midnight on 2018-12-31' diff --git a/gcloud/iap/web/enable b/gcloud/iap/web/enable index 6c8895bec..d2d2e6808 100644 --- a/gcloud/iap/web/enable +++ b/gcloud/iap/web/enable @@ -17,13 +17,13 @@ DESCRIPTION EXAMPLES To enable IAP on an App Engine application, run: - $ gcloud iap web enable --resource-type=app-engine + $ gcloud iap web enable --resource-type=app-engine \ --oauth2-client-id=CLIENT_ID --oauth2-client-secret=SECRET To enable IAP on a backend service, run: - $ gcloud iap web enable --resource-type=backend-services - --oauth2-client-id=CLIENT_ID --oauth2-client-secret=SECRET + $ gcloud iap web enable --resource-type=backend-services \ + --oauth2-client-id=CLIENT_ID --oauth2-client-secret=SECRET \ --service=SERVICE_ID FLAGS diff --git a/gcloud/iap/web/get-iam-policy b/gcloud/iap/web/get-iam-policy index 1f83937b1..57505d825 100644 --- a/gcloud/iap/web/get-iam-policy +++ b/gcloud/iap/web/get-iam-policy @@ -40,8 +40,7 @@ EXAMPLES within an App Engine service version, run: $ gcloud iap web get-iam-policy --resource-type=app-engine \ - --service=SERVICE_ID - --version=VERSION + --service=SERVICE_ID --version=VERSION To get the IAM policy for the web accesses to the IAP protected resources within all backend services, run: diff --git a/gcloud/iap/web/remove-iam-policy-binding b/gcloud/iap/web/remove-iam-policy-binding index 5824cba9d..24b1f8a87 100644 --- a/gcloud/iap/web/remove-iam-policy-binding +++ b/gcloud/iap/web/remove-iam-policy-binding @@ -24,16 +24,14 @@ EXAMPLES $ gcloud iap web remove-iam-policy-binding \ --resource-type=IAP_IAM_RESOURCE \ - --member='user:test-user@gmail.com' - --role='roles/editor' + --member='user:test-user@gmail.com' --role='roles/editor' To remove an IAM policy binding for the role of 'roles/editor' from all authenticated users on IAP IAM resource IAP_IAM_RESOURCE,run: $ gcloud iap web remove-iam-policy-binding \ --resource-type=IAP_IAM_RESOURCE \ - --member='allAuthenticatedUsers' - --role='roles/editor' + --member='allAuthenticatedUsers' --role='roles/editor' To remove an IAM policy binding with a condition of expression='request.time < timestamp("2019-01-01T00:00:00Z")', @@ -43,8 +41,8 @@ EXAMPLES $ gcloud iap web remove-iam-policy-binding \ --resource-type=IAP_IAM_RESOURCE \ - --member='user:test-user@gmail.com' - --role='roles/browser' --condition='expression=request.time < + --member='user:test-user@gmail.com' --role='roles/browser' \ + --condition='expression=request.time < timestamp("2019-01-01T00:00:00Z"),title=expires_end_of_2018, description=Expires at midnight on 2018-12-31' @@ -54,8 +52,7 @@ EXAMPLES $ gcloud iap web remove-iam-policy-binding \ --resource-type=IAP_IAM_RESOURCE \ - --member='user:test-user@gmail.com' - --role='roles/browser' --all + --member='user:test-user@gmail.com' --role='roles/browser' --all See https://cloud.google.com/iam/docs/managing-policies for details of policy role and member types. diff --git a/gcloud/iap/web/set-iam-policy b/gcloud/iap/web/set-iam-policy index 820389a95..efa7c4629 100644 --- a/gcloud/iap/web/set-iam-policy +++ b/gcloud/iap/web/set-iam-policy @@ -37,15 +37,14 @@ EXAMPLES within an App Engine service, run: $ gcloud iap web set-iam-policy POLICY_FILE \ - --resource-type=app-engine - --service=SERVICE_ID + --resource-type=app-engine --service=SERVICE_ID To set the IAM policy for the web accesses to the IAP protected resources within an App Engine service version, run: $ gcloud iap web set-iam-policy POLICY_FILE \ - --resource-type=app-engine - --service=SERVICE_ID --version=VERSION + --resource-type=app-engine --service=SERVICE_ID \ + --version=VERSION To set the IAM policy for the web accesses to the IAP protected resources within all backend services, run: @@ -57,8 +56,7 @@ EXAMPLES within a backend service, run: $ gcloud iap web set-iam-policy POLICY_FILE \ - --resource-type=backend-services - --service=SERVICE_ID + --resource-type=backend-services --service=SERVICE_ID POSITIONAL ARGUMENTS POLICY_FILE diff --git a/gcloud/identity/groups/create b/gcloud/identity/groups/create index da6466fe1..fbbe80d79 100644 --- a/gcloud/identity/groups/create +++ b/gcloud/identity/groups/create @@ -24,16 +24,14 @@ EXAMPLES descripton: $ gcloud identity groups create eng-discuss@example.com \ - --organization="example.com" \ - --display-name="Engineer Discuss" \ + --organization="example.com" --display-name="Engineer Discuss" \ --description="Group for engineering discussions" To create a new security group: - $ gcloud identity groups create security-group@example.com \ - --organization="example.com" \ - --group-type="security" \ - --display-name="Security Group" \ + $ gcloud identity groups create security-group@example.com \ + --organization="example.com" --group-type="security" \ + --display-name="Security Group" \ --description="Description of Security Group" POSITIONAL ARGUMENTS diff --git a/gcloud/identity/groups/memberships/add b/gcloud/identity/groups/memberships/add index b0ed3ff8e..22e5e4a3f 100644 --- a/gcloud/identity/groups/memberships/add +++ b/gcloud/identity/groups/memberships/add @@ -14,7 +14,7 @@ EXAMPLES To create a new membership in a group: $ gcloud identity groups memberships add \ - --group-email="eng-discuss@foo.com" \ + --group-email="eng-discuss@foo.com" \ --member-email="user@foo.com" REQUIRED FLAGS diff --git a/gcloud/identity/groups/memberships/modify-membership-roles b/gcloud/identity/groups/memberships/modify-membership-roles index 36e55c20b..eb54c6aea 100644 --- a/gcloud/identity/groups/memberships/modify-membership-roles +++ b/gcloud/identity/groups/memberships/modify-membership-roles @@ -17,9 +17,8 @@ EXAMPLES To add a new membership role to an existing group-member pair. $ gcloud identity groups memberships modify-membership-roles \ - --group-email="eng-discuss@foo.com" \ - --member-email="user@foo.com" \ - --add-roles=OWNER + --group-email="eng-discuss@foo.com" \ + --member-email="user@foo.com" --add-roles=OWNER REQUIRED FLAGS --group-email=GROUP_EMAIL diff --git a/gcloud/identity/groups/search b/gcloud/identity/groups/search index dd4699e80..fdf346d7b 100644 --- a/gcloud/identity/groups/search +++ b/gcloud/identity/groups/search @@ -14,10 +14,9 @@ DESCRIPTION EXAMPLES To Search groups: - $ gcloud identity groups search --organization="5149234212" \ - --labels="cloudidentity.googleapis.com/groups.discussion_forum" \ - --page-size=3 \ - --page-token="ala9glealanal908" + $ gcloud identity groups search --organization="5149234212" \ + --labels="cloudidentity.googleapis.com/groups.discussion_forum" \ + --page-size=3 --page-token="ala9glealanal908" REQUIRED FLAGS --labels=LABELS diff --git a/gcloud/identity/groups/update b/gcloud/identity/groups/update index 4c28728b7..751037e13 100644 --- a/gcloud/identity/groups/update +++ b/gcloud/identity/groups/update @@ -14,8 +14,8 @@ DESCRIPTION EXAMPLES To update a group: - $ gcloud identity groups update eng-discuss@foo.com \ - --display-name="New Engineer Discuss" \ + $ gcloud identity groups update eng-discuss@foo.com \ + --display-name="New Engineer Discuss" \ --description="Group for engineering discussions" POSITIONAL ARGUMENTS diff --git a/gcloud/kms/asymmetric-decrypt b/gcloud/kms/asymmetric-decrypt index e813e856c..7696ae2e2 100644 --- a/gcloud/kms/asymmetric-decrypt +++ b/gcloud/kms/asymmetric-decrypt @@ -21,13 +21,10 @@ EXAMPLES it using the asymmetric CryptoKey dont-panic Version 3 and write the plaintext to '/tmp/my/secret.file.dec'. - $ gcloud kms asymmetric-decrypt \ - --location=us-central1 \ - --keyring=hitchhiker \ - --key=dont-panic \ - --version=3 \ - --ciphertext-file=/tmp/my/secret.file.enc \ - --plaintext-file=/tmp/my/secret.file.dec + $ gcloud kms asymmetric-decrypt --location=us-central1 \ + --keyring=hitchhiker --key=dont-panic --version=3 \ + --ciphertext-file=/tmp/my/secret.file.enc \ + --plaintext-file=/tmp/my/secret.file.dec REQUIRED FLAGS --ciphertext-file=CIPHERTEXT_FILE diff --git a/gcloud/kms/asymmetric-sign b/gcloud/kms/asymmetric-sign index 68998b640..df95252e2 100644 --- a/gcloud/kms/asymmetric-sign +++ b/gcloud/kms/asymmetric-sign @@ -25,14 +25,10 @@ EXAMPLES CryptoKey dont-panic Version 3, and save the signature in base64 format to '/tmp/my/signature'. - $ gcloud kms asymmetric-sign \ - --location=us-central1 \ - --keyring=hitchhiker \ - --key=dont-panic \ - --version=3 \ - --digest-algorithm=sha256 \ - --input-file=/tmp/my/file.to.sign \ - --signature-file=/tmp/my/signature + $ gcloud kms asymmetric-sign --location=us-central1 \ + --keyring=hitchhiker --key=dont-panic --version=3 \ + --digest-algorithm=sha256 --input-file=/tmp/my/file.to.sign \ + --signature-file=/tmp/my/signature REQUIRED FLAGS --input-file=INPUT_FILE diff --git a/gcloud/kms/decrypt b/gcloud/kms/decrypt index 46f2c18fd..e2f50f823 100644 --- a/gcloud/kms/decrypt +++ b/gcloud/kms/decrypt @@ -37,24 +37,18 @@ EXAMPLES fellowship and location global and write the plaintext to 'path/to/plaintext.dec', run: - $ gcloud kms decrypt \ - --key=frodo \ - --keyring=fellowship \ - --location=global \ - --ciphertext-file=path/to/input/ciphertext \ + $ gcloud kms decrypt --key=frodo --keyring=fellowship \ + --location=global --ciphertext-file=path/to/input/ciphertext \ --plaintext-file=path/to/output/plaintext.dec To decrypt the file 'path/to/ciphertext' using the key frodo and the additional authenticated data that was used to encrypt the ciphertext, and write the decrypted plaintext to stdout, run: - $ gcloud kms decrypt \ - --key=frodo \ - --keyring=fellowship \ + $ gcloud kms decrypt --key=frodo --keyring=fellowship \ --location=global \ --additional-authenticated-data-file=path/to/aad \ - --ciphertext-file=path/to/input/ciphertext \ - --plaintext-file='-' + --ciphertext-file=path/to/input/ciphertext --plaintext-file='-' REQUIRED FLAGS --ciphertext-file=CIPHERTEXT_FILE diff --git a/gcloud/kms/ekm-connections/add-iam-policy-binding b/gcloud/kms/ekm-connections/add-iam-policy-binding new file mode 100644 index 000000000..e7817019f --- /dev/null +++ b/gcloud/kms/ekm-connections/add-iam-policy-binding @@ -0,0 +1,141 @@ +NAME + gcloud kms ekm-connections add-iam-policy-binding - add IAM policy binding + for a kms ekm connection + +SYNOPSIS + gcloud kms ekm-connections add-iam-policy-binding + (EKM_CONNECTION : --location=LOCATION) --member=PRINCIPAL --role=ROLE + [--condition=[KEY=VALUE,...] + | --condition-from-file=CONDITION_FROM_FILE] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Adds a policy binding to the IAM policy of a kms ekm connection. A binding + consists of at least one member, a role, and an optional condition. + +EXAMPLES + To add an IAM policy binding for the role of 'roles/editor' for the user + 'test-user@gmail.com' on the ekm connection laplace with location global, + run: + + $ gcloud kms ekm-connections add-iam-policy-binding laplace \ + --location='global' --member='user:test-user@gmail.com' \ + --role='roles/editor' + + To add an IAM policy binding which expires at the end of the year 2022 for + the role of 'roles/editor' and the user 'test-user@gmail.com' on the + laplace fellowship and location global, run: + + $ gcloud kms ekm-connections add-iam-policy-binding laplace \ + --location='global' --member='user:test-user@gmail.com' \ + --role='roles/editor' \ + --condition='expression=request.time < + timestamp("2023-01-01T00:00:00Z"),title=expires_end_of_2022,descrip\ + tion=Expires at midnight on 2022-12-31' + + See https://cloud.google.com/iam/docs/managing-policies for details of + policy role and member types. + +POSITIONAL ARGUMENTS + Ekm connection resource - The ekm connection 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 ekm_connection on the command line with a fully + specified name; + â—† provide the argument --project on the command line; + â—† set the property core/project. + + This must be specified. + + EKM_CONNECTION + ID of the ekm connection or fully qualified identifier for the ekm + connection. To set the ekm_connection attribute: + â–¸ provide the argument ekm_connection on the command line. + + This positional must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + The location of the resource. To set the location attribute: + â–¸ provide the argument ekm_connection 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. + +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=CONDITION_FROM_FILE + Path to a local JSON or YAML file that defines the condition. To see + available fields, see the help for --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 cloudkms/v1 API. The full documentation for this API + can be found at: https://cloud.google.com/kms/ + +NOTES + These variants are also available: + + $ gcloud alpha kms ekm-connections add-iam-policy-binding + + $ gcloud beta kms ekm-connections add-iam-policy-binding + diff --git a/gcloud/kms/ekm-connections/create b/gcloud/kms/ekm-connections/create new file mode 100644 index 000000000..e1d1e9bc4 --- /dev/null +++ b/gcloud/kms/ekm-connections/create @@ -0,0 +1,81 @@ +NAME + gcloud kms ekm-connections create - create a new ekm connection + +SYNOPSIS + gcloud kms ekm-connections create (EKM_CONNECTION : --location=LOCATION) + --hostname=HOSTNAME + --server-certificates-files=[SERVER_CERTIFICATES,...] + --service-directory-service=SERVICE_DIRECTORY_SERVICE + [--endpoint-filter=ENDPOINT_FILTER] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Creates a new connection within the given location. + +EXAMPLES + The following command creates an ekm connection named laplace within the + location us-central1: + + $ gcloud kms ekm-connections create laplace --location=us-central1 \ + --service-directory-service="foo" \ + --endpoint-filter="foo > bar" --hostname="hostname.foo" \ + --server-certificates-files=foo.pem,bar.pem + +POSITIONAL ARGUMENTS + Ekmconnection resource - The KMS ekm connection 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 ekm_connection on the command line with a fully + specified name; + â—† set the property core/project. + + This must be specified. + + EKM_CONNECTION + ID of the ekmconnection or fully qualified identifier for the + ekmconnection. To set the ekmconnection attribute: + â–¸ provide the argument ekm_connection on the command line. + + This positional must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + The Cloud location for the ekmconnection. To set the location + attribute: + â–¸ provide the argument ekm_connection on the command line with a + fully specified name; + â–¸ provide the argument --location on the command line. + +REQUIRED FLAGS + --hostname=HOSTNAME + The hostname of the EKM replica used at TLS and HTTP layers. + + --server-certificates-files=[SERVER_CERTIFICATES,...] + A list of filenames of leaf server certificates used to authenticate + HTTPS connections to the EKM replica in PEM format. If files are not in + PEM, the assumed format will be DER. + + --service-directory-service=SERVICE_DIRECTORY_SERVICE + The resource name of the Service Directory service pointing to an EKM + replica. + +OPTIONAL FLAGS + --endpoint-filter=ENDPOINT_FILTER + The filter applied to the endpoints of the resolved service. If no + filter is specified, all endpoints will be considered. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --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 kms ekm-connections create + + $ gcloud beta kms ekm-connections create + diff --git a/gcloud/kms/ekm-connections/describe b/gcloud/kms/ekm-connections/describe new file mode 100644 index 000000000..8b0b54d25 --- /dev/null +++ b/gcloud/kms/ekm-connections/describe @@ -0,0 +1,57 @@ +NAME + gcloud kms ekm-connections describe - get metadata for an ekmconnection + +SYNOPSIS + gcloud kms ekm-connections describe (EKM_CONNECTION : --location=LOCATION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Returns metadata for the given ekmconnection. + +EXAMPLES + The following command returns the metadata for the ekmconnection laplace in + the location us-east1: + + $ gcloud kms ekm-connections describe laplace --location=us-east1 + +POSITIONAL ARGUMENTS + Ekmconnection resource - The KMS ekm connection 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 ekm_connection on the command line with a fully + specified name; + â—† set the property core/project. + + This must be specified. + + EKM_CONNECTION + ID of the ekmconnection or fully qualified identifier for the + ekmconnection. To set the ekmconnection attribute: + â–¸ provide the argument ekm_connection on the command line. + + This positional must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + The Cloud location for the ekmconnection. To set the location + attribute: + â–¸ provide the argument ekm_connection on the command line with a + fully specified name; + â–¸ provide the argument --location on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha kms ekm-connections describe + + $ gcloud beta kms ekm-connections describe + diff --git a/gcloud/kms/ekm-connections/get-iam-policy b/gcloud/kms/ekm-connections/get-iam-policy new file mode 100644 index 000000000..c79d4ab4b --- /dev/null +++ b/gcloud/kms/ekm-connections/get-iam-policy @@ -0,0 +1,95 @@ +NAME + gcloud kms ekm-connections get-iam-policy - get the IAM policy for an ekm + connection + +SYNOPSIS + gcloud kms ekm-connections get-iam-policy + (EKM_CONNECTION : --location=LOCATION) [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Displays the IAM policy associated with an ekm connection. 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 + kms ekm-connections set-iam-policy for additional details. + +EXAMPLES + To print the IAM policy for a given ekm connection, run: + + $ gcloud kms ekm-connections get-iam-policy --location=my-location \ + my-ekmconnection + +POSITIONAL ARGUMENTS + Ekm connection resource - The ekm connection for which to get 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 ekm_connection on the command line with a fully + specified name; + â—† provide the argument --project on the command line; + â—† set the property core/project. + + This must be specified. + + EKM_CONNECTION + ID of the ekm connection or fully qualified identifier for the ekm + connection. To set the ekm_connection attribute: + â–¸ provide the argument ekm_connection on the command line. + + This positional must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + The location of the resource. To set the location attribute: + â–¸ provide the argument ekm_connection 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. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the cloudkms/v1 API. The full documentation for this API + can be found at: https://cloud.google.com/kms/ + +NOTES + These variants are also available: + + $ gcloud alpha kms ekm-connections get-iam-policy + + $ gcloud beta kms ekm-connections get-iam-policy + diff --git a/gcloud/kms/ekm-connections/help b/gcloud/kms/ekm-connections/help new file mode 100644 index 000000000..56133ce58 --- /dev/null +++ b/gcloud/kms/ekm-connections/help @@ -0,0 +1,49 @@ +NAME + gcloud kms ekm-connections - create and manage ekm connections + +SYNOPSIS + gcloud kms ekm-connections COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Ekm Connections are used to control the connection settings for an + EXTERNAL_VPC CryptoKey. + +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 + Add IAM policy binding for a kms ekm connection. + + create + Create a new ekm connection. + + describe + Get metadata for an ekmconnection. + + get-iam-policy + Get the IAM policy for an ekm connection. + + list + List ekmconnections within a location. + + remove-iam-policy-binding + Remove IAM policy binding for a kms ekm connection. + + set-iam-policy + Set the IAM policy binding for a KMS ekm connection. + + update + Update an ekmconnection. + +NOTES + These variants are also available: + + $ gcloud alpha kms ekm-connections + + $ gcloud beta kms ekm-connections + diff --git a/gcloud/kms/ekm-connections/list b/gcloud/kms/ekm-connections/list new file mode 100644 index 000000000..801d5fd77 --- /dev/null +++ b/gcloud/kms/ekm-connections/list @@ -0,0 +1,79 @@ +NAME + gcloud kms ekm-connections list - list ekmconnections within a location + +SYNOPSIS + gcloud kms ekm-connections list --location=LOCATION [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Lists all ekmconnections within the given location. + +EXAMPLES + The following command lists a maximum of five ekmconnections in the + location global: + + $ gcloud kms ekm-connections list --location=global --limit=5 + +REQUIRED FLAGS + Location resource - The KMS location 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 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. + +NOTES + These variants are also available: + + $ gcloud alpha kms ekm-connections list + + $ gcloud beta kms ekm-connections list + diff --git a/gcloud/kms/ekm-connections/remove-iam-policy-binding b/gcloud/kms/ekm-connections/remove-iam-policy-binding new file mode 100644 index 000000000..b6ef2bada --- /dev/null +++ b/gcloud/kms/ekm-connections/remove-iam-policy-binding @@ -0,0 +1,157 @@ +NAME + gcloud kms ekm-connections remove-iam-policy-binding - remove IAM policy + binding for a kms ekm connection + +SYNOPSIS + gcloud kms ekm-connections remove-iam-policy-binding + (EKM_CONNECTION : --location=LOCATION) --member=PRINCIPAL --role=ROLE + [--all | --condition=[KEY=VALUE,...] + | --condition-from-file=CONDITION_FROM_FILE] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Removes a policy binding from the IAM policy of a kms ekm connection. A + binding consists of at least one member, a role, and an optional condition. + +EXAMPLES + To remove an IAM policy binding for the role of 'roles/editor' for the user + 'test-user@gmail.com' on the ekm connection laplace with location global, + run: + + $ gcloud kms ekm-connections remove-iam-policy-binding laplace \ + --location='global' --member='user:test-user@gmail.com' \ + --role='roles/editor' + + To remove an IAM policy binding with a condition of + expression='request.time < timestamp("2023-01-01T00:00:00Z")', + title='expires_end_of_2022', and description='Expires at midnight on + 2022-12-31' for the role of 'roles/editor' for the user + 'test-user@gmail.com' on the ekm connection laplace with location global, + run: + + $ gcloud kms ekm-connections remove-iam-policy-binding laplace \ + --location='global' --member='user:test-user@gmail.com' \ + --role='roles/editor' \ + --condition='expression=request.time < + timestamp("2023-01-01T00:00:00Z"),title=expires_end_of_2022,descrip\ + tion=Expires at midnight on 2022-12-31' + + To remove all IAM policy bindings regardless of the condition for the role + of 'roles/editor' and for the user 'test-user@gmail.com' on the ekm + connection laplace with location global, run: + + $ gcloud kms ekm-connections remove-iam-policy-binding laplace \ + --location='global' --member='user:test-user@gmail.com' \ + --role='roles/editor' --all + + See https://cloud.google.com/iam/docs/managing-policies for details of + policy role and member types. + +POSITIONAL ARGUMENTS + Ekm connection resource - The ekm connection 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 ekm_connection on the command line with a fully + specified name; + â—† provide the argument --project on the command line; + â—† set the property core/project. + + This must be specified. + + EKM_CONNECTION + ID of the ekm connection or fully qualified identifier for the ekm + connection. To set the ekm_connection attribute: + â–¸ provide the argument ekm_connection on the command line. + + This positional must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + The location of the resource. To set the location attribute: + â–¸ provide the argument ekm_connection 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. + +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=CONDITION_FROM_FILE + Path to a local JSON or YAML file that defines the condition. To see + available fields, see the help for --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 cloudkms/v1 API. The full documentation for this API + can be found at: https://cloud.google.com/kms/ + +NOTES + These variants are also available: + + $ gcloud alpha kms ekm-connections remove-iam-policy-binding + + $ gcloud beta kms ekm-connections remove-iam-policy-binding + diff --git a/gcloud/kms/ekm-connections/set-iam-policy b/gcloud/kms/ekm-connections/set-iam-policy new file mode 100644 index 000000000..1dcfd86d2 --- /dev/null +++ b/gcloud/kms/ekm-connections/set-iam-policy @@ -0,0 +1,80 @@ +NAME + gcloud kms ekm-connections set-iam-policy - set the IAM policy binding for + a KMS ekm connection + +SYNOPSIS + gcloud kms ekm-connections set-iam-policy + (EKM_CONNECTION : --location=LOCATION) POLICY_FILE + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Sets the IAM policy for the given ekm connection as defined in a JSON or + YAML file. + + 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 ekm connection 'laplace' with the location + 'global': + + $ gcloud kms ekm-connections set-iam-policy laplace policy.json \ + --location=global + + See https://cloud.google.com/iam/docs/managing-policies for details of the + policy file format and contents. + +POSITIONAL ARGUMENTS + Ekm connection resource - The ekm connection for which to set 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 ekm_connection on the command line with a fully + specified name; + â—† provide the argument --project on the command line; + â—† set the property core/project. + + This must be specified. + + EKM_CONNECTION + ID of the ekm connection or fully qualified identifier for the ekm + connection. To set the ekm_connection attribute: + â–¸ provide the argument ekm_connection on the command line. + + This positional must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + The location of the resource. To set the location attribute: + â–¸ provide the argument ekm_connection 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. + + 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 cloudkms/v1 API. The full documentation for this API + can be found at: https://cloud.google.com/kms/ + +NOTES + These variants are also available: + + $ gcloud alpha kms ekm-connections set-iam-policy + + $ gcloud beta kms ekm-connections set-iam-policy + diff --git a/gcloud/kms/ekm-connections/update b/gcloud/kms/ekm-connections/update new file mode 100644 index 000000000..1d4412e75 --- /dev/null +++ b/gcloud/kms/ekm-connections/update @@ -0,0 +1,88 @@ +NAME + gcloud kms ekm-connections update - update an ekmconnection + +SYNOPSIS + gcloud kms ekm-connections update (EKM_CONNECTION : --location=LOCATION) + [--endpoint-filter=ENDPOINT_FILTER] [--hostname=HOSTNAME] + [--server-certificates-files=[SERVER_CERTIFICATES,...]] + [--service-directory-service=SERVICE_DIRECTORY_SERVICE] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + gcloud kms ekm-connections update can be used to update the ekmconnection. + Updates can be made to the ekmconnection's service resolver's fields. + +EXAMPLES + The following command updates an ekm-connection named laplace service + resolver's hostname within location us-east1: + + $ gcloud kms ekm-connections update laplace --location=us-east1 \ + --hostname=newhostname.foo \ + + The following command updates an ekm-connection named laplace service + resolver's service_directory_service, endpoint_filter, hostname, and + server_certificates within location us-east1: + + $ gcloud kms ekm-connections update laplace --location=us-east1 \ + --service-directory-service="foo" \ + --endpoint-filter="foo > bar" --hostname="newhostname.foo" \ + --server-certificates-files=foo.pem,bar.pem + +POSITIONAL ARGUMENTS + Ekmconnection resource - The KMS ekm connection 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 ekm_connection on the command line with a fully + specified name; + â—† set the property core/project. + + This must be specified. + + EKM_CONNECTION + ID of the ekmconnection or fully qualified identifier for the + ekmconnection. To set the ekmconnection attribute: + â–¸ provide the argument ekm_connection on the command line. + + This positional must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + The Cloud location for the ekmconnection. To set the location + attribute: + â–¸ provide the argument ekm_connection on the command line with a + fully specified name; + â–¸ provide the argument --location on the command line. + +FLAGS + --endpoint-filter=ENDPOINT_FILTER + The filter applied to the endpoints of the resolved service. If no + filter is specified, all endpoints will be considered. + + --hostname=HOSTNAME + The hostname of the EKM replica used at TLS and HTTP layers. + + --server-certificates-files=[SERVER_CERTIFICATES,...] + A list of filenames of leaf server certificates used to authenticate + HTTPS connections to the EKM replica in PEM format. If files are not in + PEM, the assumed format will be DER. + + --service-directory-service=SERVICE_DIRECTORY_SERVICE + The resource name of the Service Directory service pointing to an EKM + replica. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --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 kms ekm-connections update + + $ gcloud beta kms ekm-connections update + diff --git a/gcloud/kms/encrypt b/gcloud/kms/encrypt index a19ac37a0..d47774dfb 100644 --- a/gcloud/kms/encrypt +++ b/gcloud/kms/encrypt @@ -33,11 +33,8 @@ EXAMPLES using the CryptoKey frodo with the KeyRing fellowship and Location global, and write the ciphertext to 'path/to/ciphertext'. - $ gcloud kms encrypt \ - --key=frodo \ - --keyring=fellowship \ - --location=global \ - --plaintext-file=path/to/input/plaintext \ + $ gcloud kms encrypt --key=frodo --keyring=fellowship \ + --location=global --plaintext-file=path/to/input/plaintext \ --ciphertext-file=path/to/output/ciphertext REQUIRED FLAGS diff --git a/gcloud/kms/help b/gcloud/kms/help index 76d3eb533..5708428e9 100644 --- a/gcloud/kms/help +++ b/gcloud/kms/help @@ -28,6 +28,9 @@ GCLOUD WIDE FLAGS GROUPS GROUP is one of the following: + ekm-connections + Create and manage ekm connections. + import-jobs Create and manage import jobs. diff --git a/gcloud/kms/import-jobs/create b/gcloud/kms/import-jobs/create index d7a9166f5..a849c4141 100644 --- a/gcloud/kms/import-jobs/create +++ b/gcloud/kms/import-jobs/create @@ -14,7 +14,8 @@ EXAMPLES 'fellowship' keyring, and 'us-central1' location: $ gcloud kms import-jobs create strider --location=us-central1 \ - --keyring=fellowship --import-method=rsa-oaep-3072-sha1-aes-256 \ + --keyring=fellowship \ + --import-method=rsa-oaep-3072-sha1-aes-256 \ --protection-level=hsm POSITIONAL ARGUMENTS diff --git a/gcloud/kms/keys/create b/gcloud/kms/keys/create index e758ed9bf..1894f8c66 100644 --- a/gcloud/kms/keys/create +++ b/gcloud/kms/keys/create @@ -57,75 +57,59 @@ EXAMPLES The following command creates a key named frodo with protection level software within the keyring fellowship and location us-east1: - $ gcloud kms keys create frodo \ - --location=us-east1 \ - --keyring=fellowship \ - --purpose=encryption + $ gcloud kms keys create frodo --location=us-east1 \ + --keyring=fellowship --purpose=encryption The following command creates a key named strider with protection level software within the keyring rangers and location global with a specified rotation schedule: - $ gcloud kms keys create strider \ - --location=global --keyring=rangers \ - --purpose=encryption \ - --rotation-period=30d \ + $ gcloud kms keys create strider --location=global \ + --keyring=rangers --purpose=encryption --rotation-period=30d \ --next-rotation-time=2017-10-12T12:34:56.1234Z The following command creates a key named foo with protection level software within the keyring fellowship and location us-east1 with two specified labels: - $ gcloud kms keys create foo \ - --location=us-east1 \ - --keyring=fellowship \ - --purpose=encryption \ + $ gcloud kms keys create foo --location=us-east1 \ + --keyring=fellowship --purpose=encryption \ --labels=env=prod,team=kms The following command creates an asymmetric key named samwise with protection level software and default algorithm ec-sign-p256-sha256 within the keyring fellowship and location us-east1: - $ gcloud kms keys create samwise \ - --location=us-east1 \ - --keyring=fellowship \ - --purpose=asymmetric-signing \ + $ gcloud kms keys create samwise --location=us-east1 \ + --keyring=fellowship --purpose=asymmetric-signing \ --default-algorithm=ec-sign-p256-sha256 The following command creates a key named gimli with protection level hsm and default algorithm google-symmetric-encryption within the keyring fellowship and location us-east1: - $ gcloud kms keys create gimli \ - --location=us-east1 \ - --keyring=fellowship \ - --purpose=encryption \ - --protection-level=hsm + $ gcloud kms keys create gimli --location=us-east1 \ + --keyring=fellowship --purpose=encryption --protection-level=hsm The following command creates a key named legolas with protection level external and default algorithm external-symmetric-encryption within the keyring fellowship and location us-central1: - $ gcloud kms keys create legolas \ - --location=us-central1 \ - --keyring=fellowship \ - --purpose=encryption \ + $ gcloud kms keys create legolas --location=us-central1 \ + --keyring=fellowship --purpose=encryption \ --default-algorithm=external-symmetric-encryption \ - --protection-level=external - --skip-initial-version-creation + --protection-level=external --skip-initial-version-creation The following command creates a key named bilbo with protection level external-vpc and default algorithm external-symmetric-encryption and an EkmConnection of eagles within the keyring fellowship and location us-central1: - $ gcloud kms keys create bilbo \ - --location=us-central1 \ - --keyring=fellowship \ - --purpose=encryption \ + $ gcloud kms keys create bilbo --location=us-central1 \ + --keyring=fellowship --purpose=encryption \ --default-algorithm=external-symmetric-encryption \ - --protection-level=external-vpc - --skip-initial-version-creation + --protection-level=external-vpc \ + --skip-initial-version-creation \ --crypto-key-backend="projects/$(gcloud config get project)/ locations/us-central1/ekmConnections/eagles" diff --git a/gcloud/kms/keys/remove-rotation-schedule b/gcloud/kms/keys/remove-rotation-schedule index 2759e483a..c85b05f48 100644 --- a/gcloud/kms/keys/remove-rotation-schedule +++ b/gcloud/kms/keys/remove-rotation-schedule @@ -13,8 +13,7 @@ EXAMPLES The following command removes the rotation schedule for the key named frodo within the keyring fellowship and location global: - $ gcloud kms keys remove-rotation-schedule frodo \ - --location=global \ + $ gcloud kms keys remove-rotation-schedule frodo --location=global \ --keyring=fellowship POSITIONAL ARGUMENTS diff --git a/gcloud/kms/keys/set-rotation-schedule b/gcloud/kms/keys/set-rotation-schedule index 11e90c232..40a493268 100644 --- a/gcloud/kms/keys/set-rotation-schedule +++ b/gcloud/kms/keys/set-rotation-schedule @@ -24,10 +24,8 @@ EXAMPLES within the keyring fellowship and location global starting at the specified time: - $ gcloud kms keys set-rotation-schedule frodo \ - --location=global \ - --keyring=fellowship \ - --rotation-period=30d \ + $ gcloud kms keys set-rotation-schedule frodo --location=global \ + --keyring=fellowship --rotation-period=30d \ --next-rotation-time=2017-10-12T12:34:56.1234Z POSITIONAL ARGUMENTS diff --git a/gcloud/kms/keys/update b/gcloud/kms/keys/update index 335b1d8c1..210df09e6 100644 --- a/gcloud/kms/keys/update +++ b/gcloud/kms/keys/update @@ -36,52 +36,41 @@ EXAMPLES within the keyring fellowship and location global starting at the specified time: - $ gcloud kms keys update frodo \ - --location=global \ - --keyring=fellowship \ - --rotation-period=30d \ + $ gcloud kms keys update frodo --location=global \ + --keyring=fellowship --rotation-period=30d \ --next-rotation-time=2017-10-12T12:34:56.1234Z The following command removes the rotation schedule for the key named frodo within the keyring fellowship and location global: - $ gcloud kms keys update frodo \ - --location=global \ - --keyring=fellowship \ - --remove-rotation-schedule + $ gcloud kms keys update frodo --location=global \ + --keyring=fellowship --remove-rotation-schedule The following command updates the labels value for the key named frodo within the keyring fellowship and location global. If the label key does not exist at the time, it will be added: - $ gcloud kms keys update frodo \ - --location=global \ - --keyring=fellowship \ - --update-labels=k1=v1 + $ gcloud kms keys update frodo --location=global \ + --keyring=fellowship --update-labels=k1=v1 The following command removes labels k1 and k2 from the key named frodo within the keyring fellowship and location global: - $ gcloud kms keys update frodo \ - --location=global \ - --keyring=fellowship \ - --remove-labels=k1,k2 + $ gcloud kms keys update frodo --location=global \ + --keyring=fellowship --remove-labels=k1,k2 The following command updates the primary version for the key named frodo within the keyring fellowship and location global: - $ gcloud kms keys update frodo \ - --location=global \ - --keyring=fellowship \ - --primary-version=1 + $ gcloud kms keys update frodo --location=global \ + --keyring=fellowship --primary-version=1 The following command updates the default algorithm for the key named frodo within the keyring fellowship and location global, assuming the key originally has purpose 'asymmetric-encryption' and algorithm 'rsa-decrypt-oaep-2048-sha256': - $ gcloud kms keys update frodo \ - --location=global \ + $ gcloud kms keys update frodo --location=global \ --keyring=fellowship \ --default-algorithm=rsa-decrypt-oaep-4096-sha256 diff --git a/gcloud/kms/keys/versions/create b/gcloud/kms/keys/versions/create index be7c69e5d..25f52dfb2 100644 --- a/gcloud/kms/keys/versions/create +++ b/gcloud/kms/keys/versions/create @@ -15,8 +15,7 @@ EXAMPLES fellowship keyring, and global location and sets it as the primary version: $ gcloud kms keys versions create --location=global \ - --keyring=fellowship \ - --key=frodo --primary + --keyring=fellowship --key=frodo --primary The following command creates a new version within the legolas key, fellowship keyring, us-central1 location, @@ -24,8 +23,7 @@ EXAMPLES and sets it as the key's primary version: $ gcloud kms keys versions create --location=us-central1 \ - --keyring=fellowship \ - --key=legolas \ + --keyring=fellowship --key=legolas \ --external-key-uri=https://example.kms/v0/some/key/path \ --primary @@ -35,10 +33,8 @@ EXAMPLES version: $ gcloud kms keys versions create --location=us-central1 \ - --keyring=fellowship \ - --key=bilbo \ - --ekm-connection-key-path=v0/some/key/path \ - --primary + --keyring=fellowship --key=bilbo \ + --ekm-connection-key-path=v0/some/key/path --primary FLAGS --ekm-connection-key-path=EKM_CONNECTION_KEY_PATH diff --git a/gcloud/kms/keys/versions/get-public-key b/gcloud/kms/keys/versions/get-public-key index e6063285d..51f1183ef 100644 --- a/gcloud/kms/keys/versions/get-public-key +++ b/gcloud/kms/keys/versions/get-public-key @@ -17,11 +17,9 @@ EXAMPLES The following command saves the public key for CryptoKey frodo Version 2 to '/tmp/my/pem.file': - $ gcloud kms keys versions get-public-key 2 \ - --key=frodo \ - --keyring=fellowship \ - --location=us-east1 \ - --output-file=/tmp/my/pem.file + $ gcloud kms keys versions get-public-key 2 --key=frodo \ + --keyring=fellowship --location=us-east1 \ + --output-file=/tmp/my/pem.file POSITIONAL ARGUMENTS VERSION diff --git a/gcloud/kms/keys/versions/import b/gcloud/kms/keys/versions/import index 8e5e77463..485408cd3 100644 --- a/gcloud/kms/keys/versions/import +++ b/gcloud/kms/keys/versions/import @@ -23,11 +23,9 @@ EXAMPLES the provided key material. $ gcloud kms keys versions import --location=global \ - --keyring=fellowship \ - --key=frodo \ - --import-job=strider \ - --rsa-aes-wrapped-key-file=path/to/target/key \ - --algorithm=google-symmetric-encryption + --keyring=fellowship --key=frodo --import-job=strider \ + --rsa-aes-wrapped-key-file=path/to/target/key \ + --algorithm=google-symmetric-encryption REQUIRED FLAGS --algorithm=ALGORITHM diff --git a/gcloud/kms/keys/versions/list b/gcloud/kms/keys/versions/list index 2b738b2d2..88fb7c531 100644 --- a/gcloud/kms/keys/versions/list +++ b/gcloud/kms/keys/versions/list @@ -15,8 +15,7 @@ EXAMPLES fellowship, and location global: $ gcloud kms keys versions list --location=global \ - --keyring=fellowship \ - --key=frodo + --keyring=fellowship --key=frodo FLAGS --key=KEY diff --git a/gcloud/kms/keys/versions/update b/gcloud/kms/keys/versions/update index 87b3417d5..c3f40fe15 100644 --- a/gcloud/kms/keys/versions/update +++ b/gcloud/kms/keys/versions/update @@ -19,33 +19,27 @@ EXAMPLES fellowship and location us-east1: $ gcloud kms keys versions update 8 --location=us-east1 \ - --keyring=fellowship \ - --key=frodo \ - --state=enabled + --keyring=fellowship --key=frodo --state=enabled The following command disables the key version 8 of key frodo within keyring fellowship and location us-east1: $ gcloud kms keys versions update 8 --location=us-east1 \ - --keyring=fellowship \ - --key=frodo \ - --state=disabled + --keyring=fellowship --key=frodo --state=disabled The following command updates the external key URI of version 8 of key frodo within keyring fellowship and location us-east1: $ gcloud kms keys versions update 8 --location=us-east1 \ - --keyring=fellowship \ - --key=frodo \ - --external-key-uri=https://example.kms/v0/some/key/path + --keyring=fellowship --key=frodo \ + --external-key-uri=https://example.kms/v0/some/key/path The following command updates the ekm connection key path of version 8 of key bilbo within keyring fellowship and location us-east1: $ gcloud kms keys versions update 8 --location=us-east1 \ - --keyring=fellowship \ - --key=bilbo \ - --ekm-connection-key-path=v0/some/key/path + --keyring=fellowship --key=bilbo \ + --ekm-connection-key-path=v0/some/key/path POSITIONAL ARGUMENTS VERSION diff --git a/gcloud/kms/mac-sign b/gcloud/kms/mac-sign index a3b2b0cbf..e5c9fa465 100644 --- a/gcloud/kms/mac-sign +++ b/gcloud/kms/mac-sign @@ -22,13 +22,9 @@ EXAMPLES it using the symmetric MAC CryptoKey dont-panic Version 3, and save the signature in base64 format to '/tmp/my/signature'. - $ gcloud kms mac-sign \ - --location=us-central1 \ - --keyring=hitchhiker \ - --key=dont-panic \ - --version=3 \ - --input-file=/tmp/my/file.to.sign \ - --signature-file=/tmp/my/signature + $ gcloud kms mac-sign --location=us-central1 --keyring=hitchhiker \ + --key=dont-panic --version=3 --input-file=/tmp/my/file.to.sign \ + --signature-file=/tmp/my/signature REQUIRED FLAGS --input-file=INPUT_FILE diff --git a/gcloud/kms/mac-verify b/gcloud/kms/mac-verify index c708dd243..d51af848f 100644 --- a/gcloud/kms/mac-verify +++ b/gcloud/kms/mac-verify @@ -21,13 +21,10 @@ EXAMPLES file used previously to generate the MAC tag ('/tmp/my/original.data.file'). - $ gcloud kms mac-verify \ - --location=us-central1 \ - --keyring=hitchhiker \ - --key=dont-panic \ - --version=3 \ - --input-file=/tmp/my/original.data.file \ - --signature-file=/tmp/my/file.to.verify + $ gcloud kms mac-verify --location=us-central1 \ + --keyring=hitchhiker --key=dont-panic --version=3 \ + --input-file=/tmp/my/original.data.file \ + --signature-file=/tmp/my/file.to.verify REQUIRED FLAGS --input-file=INPUT_FILE diff --git a/gcloud/logging/sinks/create b/gcloud/logging/sinks/create index 57cb00957..b0afd3a63 100644 --- a/gcloud/logging/sinks/create +++ b/gcloud/logging/sinks/create @@ -38,8 +38,9 @@ DESCRIPTION EXAMPLES To route all Google Compute Engine logs to BigQuery, run: - $ gcloud logging sinks create my-bq-sink - bigquery.googleapis.com/projects/my-project/datasets/my_dataset --log-filter='resource.type="gce_instance"' + $ gcloud logging sinks create my-bq-sink \ + bigquery.googleapis.com/projects/my-project/datasets/\ + my_dataset --log-filter='resource.type="gce_instance"' To route "syslog" from App Engine Flexible to a Cloud Storage bucket, run: @@ -50,13 +51,15 @@ EXAMPLES To route Google App Engine logs with ERROR severity, run: - $ gcloud logging sinks create my-error-logs - bigquery.googleapis.com/projects/my-project/datasets/my_dataset --log-filter='resource.type="gae_app" AND severity=ERROR' + $ gcloud logging sinks create my-error-logs \ + bigquery.googleapis.com/projects/my-project/datasets/\ + my_dataset --log-filter='resource.type="gae_app" AND severity=ERROR' To route all logs to a log bucket in a different project, run: - $ gcloud logging sinks create my-sink - logging.googleapis.com/projects/my-central-project/locations/global/buckets/my-central-bucket + $ gcloud logging sinks create my-sink \ + logging.googleapis.com/projects/my-central-project/locations/\ + global/buckets/my-central-bucket POSITIONAL ARGUMENTS SINK_NAME diff --git a/gcloud/logging/views/update b/gcloud/logging/views/update index 407e99b3f..9112809f4 100644 --- a/gcloud/logging/views/update +++ b/gcloud/logging/views/update @@ -15,8 +15,7 @@ EXAMPLES To update a view in your project, run: $ gcloud logging views update my-view --bucket=my-bucket \ - --location=global - --description=my-new-description + --location=global --description=my-new-description POSITIONAL ARGUMENTS VIEW_ID diff --git a/gcloud/memcache/instances/create b/gcloud/memcache/instances/create index 5007475e4..23b3294fc 100644 --- a/gcloud/memcache/instances/create +++ b/gcloud/memcache/instances/create @@ -22,8 +22,8 @@ EXAMPLES 'us-central1' with 3 nodes, each with 2 CPUs and 2GB of memory, run: $ gcloud memcache instances create my-memcache-instance \ - --region=us-central1 \ - --node-count=3 --node-cpu=2 --node-memory=2GB + --region=us-central1 --node-count=3 --node-cpu=2 \ + --node-memory=2GB POSITIONAL ARGUMENTS Instance resource - Arguments and flags that specify the Memcached diff --git a/gcloud/metastore/services/import/gcs b/gcloud/metastore/services/import/gcs index 124202530..e539c5d9e 100644 --- a/gcloud/metastore/services/import/gcs +++ b/gcloud/metastore/services/import/gcs @@ -24,7 +24,7 @@ EXAMPLES $ gcloud metastore services import gcs my-service \ --import-id=my-import --description='testing description' \ - --dump-type=mysql --database-dump=gs://database-dump + --dump-type=mysql --database-dump=gs://database-dump POSITIONAL ARGUMENTS Service resource - Arguments and flags that specify the Dataproc Metastore diff --git a/gcloud/ml-engine/models/delete b/gcloud/ml-engine/models/delete index 5fa62a429..82858c08e 100644 --- a/gcloud/ml-engine/models/delete +++ b/gcloud/ml-engine/models/delete @@ -9,8 +9,8 @@ EXAMPLES To delete all models matching the regular expression vision[0-9]+, run: $ gcloud ml-engine models list --uri \ - --filter 'name ~ vision[0-9]+' | - xargs -n 1 gcloud ml-engine models delete + --filter 'name ~ vision[0-9]+' | xargs -n 1 gcloud ml-engine \ + models delete POSITIONAL ARGUMENTS MODEL diff --git a/gcloud/ml/language/classify-text b/gcloud/ml/language/classify-text index ada0b6be1..3f5cd5b25 100644 --- a/gcloud/ml/language/classify-text +++ b/gcloud/ml/language/classify-text @@ -31,7 +31,7 @@ EXAMPLES $ gcloud ml language classify-text \ --content-file='gs://bucket_name/mycontent.html' \ - --content-type=HTML --language=ja-JP + --content-type=HTML --language=ja-JP REQUIRED FLAGS Exactly one of these must be specified: diff --git a/gcloud/ml/speech/recognize b/gcloud/ml/speech/recognize index a0c8de822..68a7c7506 100644 --- a/gcloud/ml/speech/recognize +++ b/gcloud/ml/speech/recognize @@ -28,8 +28,8 @@ EXAMPLES custom sampling rate and encoding that uses hints and filters profanity: $ gcloud ml speech recognize 'gs://bucket/myaudio' \ - --language-code=es-ES --sample-rate=2200 --hints=Bueno \ - --encoding=OGG_OPUS --filter-profanity + --language-code=es-ES --sample-rate=2200 --hints=Bueno \ + --encoding=OGG_OPUS --filter-profanity POSITIONAL ARGUMENTS AUDIO @@ -91,6 +91,12 @@ OPTIONAL FLAGS audio that is not one of the specific audio models. For example, long-form audio. Ideally the audio is high-fidelity, recorded at a 16khz or greater sampling rate. + medical_conversation + Best for audio that originated from a conversation between a + medical provider and patient. + medical_dictation + Best for audio that originated from dictation notes by a medical + provider. phone_call audio that originated from a phone call (typically recorded at an 8khz sampling rate). diff --git a/gcloud/ml/speech/recognize-long-running b/gcloud/ml/speech/recognize-long-running index 08d743bcf..550750b09 100644 --- a/gcloud/ml/speech/recognize-long-running +++ b/gcloud/ml/speech/recognize-long-running @@ -100,6 +100,12 @@ OPTIONAL FLAGS audio that is not one of the specific audio models. For example, long-form audio. Ideally the audio is high-fidelity, recorded at a 16khz or greater sampling rate. + medical_conversation + Best for audio that originated from a conversation between a + medical provider and patient. + medical_dictation + Best for audio that originated from dictation notes by a medical + provider. phone_call audio that originated from a phone call (typically recorded at an 8khz sampling rate). diff --git a/gcloud/ml/vision/detect-text-pdf b/gcloud/ml/vision/detect-text-pdf index 85935784a..27ecbd338 100644 --- a/gcloud/ml/vision/detect-text-pdf +++ b/gcloud/ml/vision/detect-text-pdf @@ -16,8 +16,8 @@ EXAMPLES To detect text for input PDF file 'gs://my_bucket/input_file' and store output in 'gs://my_bucket/out_put_prefix': - $ gcloud ml vision detect-text-pdf gs://my_bucket/input_file - gs://my_bucket/out_put_prefix + $ gcloud ml vision detect-text-pdf gs://my_bucket/input_file \ + gs://my_bucket/out_put_prefix POSITIONAL ARGUMENTS INPUT_FILE diff --git a/gcloud/ml/vision/detect-text-tiff b/gcloud/ml/vision/detect-text-tiff index 886104993..2dcae09da 100644 --- a/gcloud/ml/vision/detect-text-tiff +++ b/gcloud/ml/vision/detect-text-tiff @@ -16,8 +16,8 @@ EXAMPLES To detect text for input TIFF file gs://my_bucket/input_file and store output in gs://my_bucket/out_put_prefix: - $ gcloud ml vision detect-text-tiff gs://my_bucket/input_file - gs://my_bucket/out_put_prefix + $ gcloud ml vision detect-text-tiff gs://my_bucket/input_file \ + gs://my_bucket/out_put_prefix POSITIONAL ARGUMENTS INPUT_FILE diff --git a/gcloud/network-management/connectivity-tests/create b/gcloud/network-management/connectivity-tests/create index b4873b08d..e5a4973a1 100644 --- a/gcloud/network-management/connectivity-tests/create +++ b/gcloud/network-management/connectivity-tests/create @@ -29,8 +29,10 @@ EXAMPLES network. $ gcloud network-management connectivity-tests create my-test \ - --source-instance=projects/my-project/zones/us-west-1/instances/my-instance - --destination-ip-address=10.142.0.2 --destination-network=projects/my-project/global/networks/peering-network + --source-instance=projects/my-project/zones/us-west-1/\ + instances/my-instance --destination-ip-address=10.142.0.2 \ + --destination-network=projects/my-project/global/networks/\ + peering-network POSITIONAL ARGUMENTS Connectivity test resource - Name of the connectivity test you want to @@ -137,8 +139,7 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the networkmanagement/v1 API. The full documentation for - this API can be found at: - http://g3doc/cloud/network/topology/boq/goa/nicbilling/server/README + this API can be found at: https://cloud.google.com/ NOTES This variant is also available: diff --git a/gcloud/network-management/connectivity-tests/delete b/gcloud/network-management/connectivity-tests/delete index c3c6c23bd..603ad9d34 100644 --- a/gcloud/network-management/connectivity-tests/delete +++ b/gcloud/network-management/connectivity-tests/delete @@ -46,8 +46,7 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the networkmanagement/v1 API. The full documentation for - this API can be found at: - http://g3doc/cloud/network/topology/boq/goa/nicbilling/server/README + this API can be found at: https://cloud.google.com/ NOTES This variant is also available: diff --git a/gcloud/network-management/connectivity-tests/describe b/gcloud/network-management/connectivity-tests/describe index 448dca36f..62e8167d6 100644 --- a/gcloud/network-management/connectivity-tests/describe +++ b/gcloud/network-management/connectivity-tests/describe @@ -41,8 +41,7 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the networkmanagement/v1 API. The full documentation for - this API can be found at: - http://g3doc/cloud/network/topology/boq/goa/nicbilling/server/README + this API can be found at: https://cloud.google.com/ NOTES This variant is also available: diff --git a/gcloud/network-management/connectivity-tests/list b/gcloud/network-management/connectivity-tests/list index 2e2f3494a..218c5e0b1 100644 --- a/gcloud/network-management/connectivity-tests/list +++ b/gcloud/network-management/connectivity-tests/list @@ -53,8 +53,7 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the networkmanagement/v1 API. The full documentation for - this API can be found at: - http://g3doc/cloud/network/topology/boq/goa/nicbilling/server/README + this API can be found at: https://cloud.google.com/ NOTES This variant is also available: diff --git a/gcloud/network-management/connectivity-tests/rerun b/gcloud/network-management/connectivity-tests/rerun index d64d220b0..2d81b800c 100644 --- a/gcloud/network-management/connectivity-tests/rerun +++ b/gcloud/network-management/connectivity-tests/rerun @@ -46,8 +46,7 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the networkmanagement/v1 API. The full documentation for - this API can be found at: - http://g3doc/cloud/network/topology/boq/goa/nicbilling/server/README + this API can be found at: https://cloud.google.com/ NOTES This variant is also available: diff --git a/gcloud/network-management/connectivity-tests/update b/gcloud/network-management/connectivity-tests/update index c84e4d75f..374772111 100644 --- a/gcloud/network-management/connectivity-tests/update +++ b/gcloud/network-management/connectivity-tests/update @@ -36,7 +36,8 @@ EXAMPLES modifying the description and destination IP address. $ gcloud network-management connectivity-tests update my-test \ - --description='update dst addr' --destination-ip-address='10.142.0.3' + --description='update dst addr' \ + --destination-ip-address='10.142.0.3' POSITIONAL ARGUMENTS Connectivity test resource - Name of the connectivity test you want to @@ -179,8 +180,7 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the networkmanagement/v1 API. The full documentation for - this API can be found at: - http://g3doc/cloud/network/topology/boq/goa/nicbilling/server/README + this API can be found at: https://cloud.google.com/ NOTES This variant is also available: diff --git a/gcloud/network-management/operations/describe b/gcloud/network-management/operations/describe index 3108d2737..776a838d5 100644 --- a/gcloud/network-management/operations/describe +++ b/gcloud/network-management/operations/describe @@ -41,8 +41,7 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the networkmanagement/v1 API. The full documentation for - this API can be found at: - http://g3doc/cloud/network/topology/boq/goa/nicbilling/server/README + this API can be found at: https://cloud.google.com/ NOTES This variant is also available: diff --git a/gcloud/network-management/operations/list b/gcloud/network-management/operations/list index 38cecb7c7..ad0fbfbad 100644 --- a/gcloud/network-management/operations/list +++ b/gcloud/network-management/operations/list @@ -54,8 +54,7 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the networkmanagement/v1 API. The full documentation for - this API can be found at: - http://g3doc/cloud/network/topology/boq/goa/nicbilling/server/README + this API can be found at: https://cloud.google.com/ NOTES This variant is also available: diff --git a/gcloud/policy-troubleshoot/iam b/gcloud/policy-troubleshoot/iam index 984cd0cfb..5e2d95f91 100644 --- a/gcloud/policy-troubleshoot/iam +++ b/gcloud/policy-troubleshoot/iam @@ -15,8 +15,8 @@ EXAMPLES $ gcloud policy-troubleshoot iam \ //cloudresourcemanager.googleapis.com/projects/project-id \ - --principal-email=my-iam-account@somedomain.com \ - --permission=resourcemanager.projects.get + --principal-email=my-iam-account@somedomain.com \ + --permission=resourcemanager.projects.get See https://cloud.google.com/iam/docs/policies for more information about IAM policies. diff --git a/gcloud/privateca/certificates/create b/gcloud/privateca/certificates/create index 9654a3578..b85c4db66 100644 --- a/gcloud/privateca/certificates/create +++ b/gcloud/privateca/certificates/create @@ -26,18 +26,14 @@ EXAMPLES $ gcloud privateca certificates create frontend-server-tls \ --issuer-pool=my-pool --issuer-location=us-west1 \ - --csr=./csr.pem \ - --cert-output-file=./cert.pem \ - --validity=P30D + --csr=./csr.pem --cert-output-file=./cert.pem --validity=P30D To create a certificate using a client-generated key: $ gcloud privateca certificates create frontend-server-tls \ --issuer-pool=my-pool --issuer-location=us-west1 \ - --generate-key \ - --key-output-file=./key \ - --cert-output-file=./cert.pem \ - --dns-san=www.joonix.net \ + --generate-key --key-output-file=./key \ + --cert-output-file=./cert.pem --dns-san=www.joonix.net \ --use-preset-profile=leaf_server_tls POSITIONAL ARGUMENTS diff --git a/gcloud/privateca/certificates/export b/gcloud/privateca/certificates/export index e1e4a775a..f26525370 100644 --- a/gcloud/privateca/certificates/export +++ b/gcloud/privateca/certificates/export @@ -13,15 +13,14 @@ EXAMPLES $ gcloud privateca certificates export my-cert \ --issuer-pool=my-pool --issuer-location=us-west1 \ - --output-file=cert.pem + --output-file=cert.pem To export a pem-encoded certificate along with its issuing chain in the same file, run the following: $ gcloud privateca certificates export my-cert \ --issuer-pool=my-pool --issuer-location=us-west1 \ - --include-chain \ - --output-file=chain.pem + --include-chain --output-file=chain.pem You can omit the --issuer-location flag in both of the above examples if you've already set the privateca/location property. For example: @@ -36,8 +35,7 @@ The following is equivalent to the first example above. The following is equivalent to the second example above. $ gcloud privateca certificates export my-cert \ - --issuer-pool=my-pool --include-chain \ - --output-file=chain.pem + --issuer-pool=my-pool --include-chain --output-file=chain.pem POSITIONAL ARGUMENTS CERTIFICATE resource - The certificate to export. The arguments in this diff --git a/gcloud/privateca/certificates/list b/gcloud/privateca/certificates/list index 0ccc7ac26..fbcf4e3c5 100644 --- a/gcloud/privateca/certificates/list +++ b/gcloud/privateca/certificates/list @@ -25,7 +25,8 @@ EXAMPLES $ gcloud privateca certificates list --issuer-pool=my-pool \ --location=us-west1 \ - --filter="issuer_certificate_authority='projects/1234567890/locations/us-west1/caPools/my-pool/certificateAuthorities/my-ca'" + --filter="issuer_certificate_authority='projects/1234567890/loca\ + tions/us-west1/caPools/my-pool/certificateAuthorities/my-ca'" You can omit the --location flag in both of the above examples if you've already set the privateca/location property. For example: diff --git a/gcloud/privateca/certificates/revoke b/gcloud/privateca/certificates/revoke index 83fa213e7..241704fe5 100644 --- a/gcloud/privateca/certificates/revoke +++ b/gcloud/privateca/certificates/revoke @@ -15,17 +15,16 @@ EXAMPLES To revoke the 'frontend-server-tls' certificate due to key compromise: $ gcloud privateca certificates revoke \ - --certificate=frontend-server-tls \ - --issuer-pool=my-pool --issuer-location=us-west1 \ - --reason=key_compromise + --certificate=frontend-server-tls --issuer-pool=my-pool \ + --issuer-location=us-west1 --reason=key_compromise To revoke the a certificate with the serial number '7dc1d9186372de2e1f4824abb1c4c9e5e43cbb40' due to a newer one being issued: $ gcloud privateca certificates revoke \ - --serial-number=7dc1d9186372de2e1f4824abb1c4c9e5e43cbb40 \ - --issuer-pool=my-pool --issuer-location=us-west1 \ - --reason=superseded + --serial-number=7dc1d9186372de2e1f4824abb1c4c9e5e43cbb40 \ + --issuer-pool=my-pool --issuer-location=us-west1 \ + --reason=superseded REQUIRED FLAGS The certificate identifier. diff --git a/gcloud/privateca/certificates/update b/gcloud/privateca/certificates/update index 91babb1a1..47f64b064 100644 --- a/gcloud/privateca/certificates/update +++ b/gcloud/privateca/certificates/update @@ -12,8 +12,8 @@ EXAMPLES To update labels on a certificate: $ gcloud privateca certificates update frontend-server-tls \ - --issuer-pool=my-pool --issuer-location=us-west1 \ - --update-labels=in_use=true + --issuer-pool=my-pool --issuer-location=us-west1 \ + --update-labels=in_use=true POSITIONAL ARGUMENTS CERTIFICATE resource - The certificate to update. The arguments in this diff --git a/gcloud/privateca/pools/add-iam-policy-binding b/gcloud/privateca/pools/add-iam-policy-binding index 9913e0356..18521153e 100644 --- a/gcloud/privateca/pools/add-iam-policy-binding +++ b/gcloud/privateca/pools/add-iam-policy-binding @@ -21,9 +21,8 @@ EXAMPLES the CA pool 'my-pool' with the location 'us-west1', run: $ gcloud privateca pools add-iam-policy-binding my-pool \ - --location='us-west1' \ - --member='user:test-user@gmail.com' \ - --role='roles/privateca.certificateManager' + --location='us-west1' --member='user:test-user@gmail.com' \ + --role='roles/privateca.certificateManager' POSITIONAL ARGUMENTS CA Pool resource - The CA pool for which to add the IAM policy binding. diff --git a/gcloud/privateca/pools/create b/gcloud/privateca/pools/create index a25cf0c10..22db53c2b 100644 --- a/gcloud/privateca/pools/create +++ b/gcloud/privateca/pools/create @@ -11,19 +11,18 @@ EXAMPLES To create a CA pool in the dev ops tier: $ gcloud privateca pools create my-pool --location=us-west1 \ - --tier=devops + --tier=devops To create a CA pool and restrict what it can issue: $ gcloud privateca pools create my-pool --location=us-west1 \ - --issuance-policy=policy.yaml + --issuance-policy=policy.yaml To create a CA pool that doesn't publicly publish CA certificates and CRLs: $ gcloud privateca pools create my-pool --location=us-west1 \ - --issuance-policy=policy.yaml \ - --no-publish-ca-cert \ - --no-publish-crl + --issuance-policy=policy.yaml --no-publish-ca-cert \ + --no-publish-crl POSITIONAL ARGUMENTS CA POOL resource - The ca pool to create. The arguments in this group can diff --git a/gcloud/privateca/pools/describe b/gcloud/privateca/pools/describe index dca17575c..4cc5ed77a 100644 --- a/gcloud/privateca/pools/describe +++ b/gcloud/privateca/pools/describe @@ -11,8 +11,7 @@ DESCRIPTION EXAMPLES To get metadata for the CA pool 'my-pool' in location 'us-west1': - $ gcloud privateca pools describe my-pool \ - --location=us-west1 + $ gcloud privateca pools describe my-pool --location=us-west1 POSITIONAL ARGUMENTS CA Pool resource - The CA pool for which to obtain metadata. The arguments diff --git a/gcloud/privateca/pools/get-ca-certs b/gcloud/privateca/pools/get-ca-certs index b32daf29a..bbc2170d0 100644 --- a/gcloud/privateca/pools/get-ca-certs +++ b/gcloud/privateca/pools/get-ca-certs @@ -10,8 +10,7 @@ EXAMPLES To get the root CA certs for all active CAs in the CA pool: $ gcloud privateca pools get-ca-certs my-pool \ - --output-file=ca-certificates.pem \ - --location=us-west1 + --output-file=ca-certificates.pem --location=us-west1 POSITIONAL ARGUMENTS CA POOL resource - The ca pool whose CA certificates should be fetched. diff --git a/gcloud/privateca/pools/remove-iam-policy-binding b/gcloud/privateca/pools/remove-iam-policy-binding index accdb4fef..646dad2bb 100644 --- a/gcloud/privateca/pools/remove-iam-policy-binding +++ b/gcloud/privateca/pools/remove-iam-policy-binding @@ -21,8 +21,7 @@ EXAMPLES the CA pool 'my-pool' with the location 'us-west1', run: $ gcloud privateca pools remove-iam-policy-binding my-pool \ - --location=us-west1 \ - --member='user:test-user@gmail.com' \ + --location=us-west1 --member='user:test-user@gmail.com' \ --role='roles/privateca.certificateManager' POSITIONAL ARGUMENTS diff --git a/gcloud/privateca/pools/update b/gcloud/privateca/pools/update index 64dc1771a..029d5e996 100644 --- a/gcloud/privateca/pools/update +++ b/gcloud/privateca/pools/update @@ -10,15 +10,13 @@ SYNOPSIS EXAMPLES To update labels on a CA pool: - $ gcloud privateca pools update my-pool \ - --location=us-west1 \ - --update-labels=foo=bar + $ gcloud privateca pools update my-pool --location=us-west1 \ + --update-labels=foo=bar To disable publishing CRLs on a CA pool: - $ gcloud privateca pools update my-pool \ - --location=us-west1 \ - --no-publish-crl + $ gcloud privateca pools update my-pool --location=us-west1 \ + --no-publish-crl POSITIONAL ARGUMENTS CA POOL resource - The ca pool to update. The arguments in this group can diff --git a/gcloud/privateca/roots/create b/gcloud/privateca/roots/create index 841826c0b..ca33ec1ad 100644 --- a/gcloud/privateca/roots/create +++ b/gcloud/privateca/roots/create @@ -21,18 +21,19 @@ SYNOPSIS EXAMPLES To create a root CA that supports one layer of subordinates: - $ gcloud privateca roots create prod-root \ - --location=us-west1 --pool=my-pool \ - --kms-key-version="projects/joonix-pki/locations/us-west1/keyRings/kr1/cryptoKeys/k1/cryptoKeyVersions/1" \ + $ gcloud privateca roots create prod-root --location=us-west1 \ + --pool=my-pool \ + --kms-key-version="projects/joonix-pki/locations/us-west1/keyRin\ + gs/kr1/cryptoKeys/k1/cryptoKeyVersions/1" \ --subject="CN=Joonix Production Root CA, O=Google" \ --max-chain-length=1 To create a root CA that is based on an existing CA: - $ gcloud privateca roots create prod-root \ - --location=us-west1 --pool=my-pool \ - --kms-key-version="projects/joonix-pki/locations/us-west1/keyRings/kr1/cryptoKeys/k1/cryptoKeyVersions/1" \ - --from-ca=source-root + $ gcloud privateca roots create prod-root --location=us-west1 \ + --pool=my-pool \ + --kms-key-version="projects/joonix-pki/locations/us-west1/keyRin\ + gs/kr1/cryptoKeys/k1/cryptoKeyVersions/1" --from-ca=source-root POSITIONAL ARGUMENTS Certificate Authority resource - The name of the root CA to create. The diff --git a/gcloud/privateca/roots/describe b/gcloud/privateca/roots/describe index 827a508d3..4d8ecc539 100644 --- a/gcloud/privateca/roots/describe +++ b/gcloud/privateca/roots/describe @@ -14,15 +14,15 @@ EXAMPLES To get metadata for the root CA 'prod-root' in location 'us-west1' and CA Pool 'my-pool': - $ gcloud privateca roots describe server-tls-1 \ - --location=us-west1 --pool=my-pool + $ gcloud privateca roots describe server-tls-1 --location=us-west1 \ + --pool=my-pool To download the PEM-encoded CA certificate chain for the 'prod-root' CA in location 'us-west1' and CA Pool 'my-pool' to a file called 'prod-root.crt': - $ gcloud privateca roots describe prod-root \ - --location=us-west1 --pool=my-pool \ - --format="value(pemCaCertificates)" > ./prod-root.crt + $ gcloud privateca roots describe prod-root --location=us-west1 \ + --pool=my-pool --format="value(pemCaCertificates)" > \ + ./prod-root.crt POSITIONAL ARGUMENTS CERTIFICATE AUTHORITY resource - The certificate authority for which to diff --git a/gcloud/privateca/roots/update b/gcloud/privateca/roots/update index 5a680d81d..ea727844e 100644 --- a/gcloud/privateca/roots/update +++ b/gcloud/privateca/roots/update @@ -11,10 +11,8 @@ SYNOPSIS EXAMPLES To update labels on a root CA: - $ gcloud privateca roots update prod-root \ - --location=us-west1 \ - --pool=my-pool \ - --update-labels=foo=bar + $ gcloud privateca roots update prod-root --location=us-west1 \ + --pool=my-pool --update-labels=foo=bar POSITIONAL ARGUMENTS CERTIFICATE AUTHORITY resource - The certificate authority to update. The diff --git a/gcloud/privateca/subordinates/activate b/gcloud/privateca/subordinates/activate index e13ed2336..afb50f1f8 100644 --- a/gcloud/privateca/subordinates/activate +++ b/gcloud/privateca/subordinates/activate @@ -14,9 +14,8 @@ EXAMPLES and CA Pool 'server-tls-pool' using a PEM certificate chain in 'chain.crt': $ gcloud privateca subordinates activate server-tls-1 \ - --location=us-west1 \ - --pool=server-tls-pool \ - --pem-chain=./chain.crt + --location=us-west1 --pool=server-tls-pool \ + --pem-chain=./chain.crt POSITIONAL ARGUMENTS CERTIFICATE AUTHORITY resource - The certificate authority to activate. diff --git a/gcloud/privateca/subordinates/create b/gcloud/privateca/subordinates/create index 054abce76..1e2db85bd 100644 --- a/gcloud/privateca/subordinates/create +++ b/gcloud/privateca/subordinates/create @@ -29,26 +29,27 @@ EXAMPLES --location=us-west1 --pool=my-pool \ --subject="CN=Joonix TLS CA, O=Google" \ --issuer-pool=other-pool --issuer-location=us-west1 \ - --kms-key-version="projects/joonix-pki/locations/us-west1/keyRings/kr1/cryptoKeys/key2/cryptoKeyVersions/1" + --kms-key-version="projects/joonix-pki/locations/us-west1/keyRin\ + gs/kr1/cryptoKeys/key2/cryptoKeyVersions/1" To create a subordinate CA named 'server-tls-1' whose issuer is located elsewhere: $ gcloud privateca subordinates create server-tls-1 \ --location=us-west1 --pool=my-pool \ - --subject="CN=Joonix TLS CA, O=Google" \ - --create-csr \ + --subject="CN=Joonix TLS CA, O=Google" --create-csr \ --csr-output-file=./csr.pem \ - --kms-key-version="projects/joonix-pki/locations/us-west1/keyRings/kr1/cryptoKeys/key2/cryptoKeyVersions/1" + --kms-key-version="projects/joonix-pki/locations/us-west1/keyRin\ + gs/kr1/cryptoKeys/key2/cryptoKeyVersions/1" To create a subordinate CA named 'server-tls-1' chaining up to a root CA named 'prod-root' based on an existing CA: $ gcloud privateca subordinates create server-tls-1 \ - --location=us-west1 --pool=my-pool \ - --issuer-pool=other-pool --issuer-location=us-west1 \ - --from-ca=source-ca \ - --kms-key-version="projects/joonix-pki/locations/us-west1/keyRings/kr1/cryptoKeys/key2/cryptoKeyVersions/1" + --location=us-west1 --pool=my-pool --issuer-pool=other-pool \ + --issuer-location=us-west1 --from-ca=source-ca \ + --kms-key-version="projects/joonix-pki/locations/us-west1/keyRin\ + gs/kr1/cryptoKeys/key2/cryptoKeyVersions/1" POSITIONAL ARGUMENTS Certificate Authority resource - The name of the subordinate CA to create. diff --git a/gcloud/privateca/subordinates/delete b/gcloud/privateca/subordinates/delete index 545259298..b12849139 100644 --- a/gcloud/privateca/subordinates/delete +++ b/gcloud/privateca/subordinates/delete @@ -38,8 +38,8 @@ EXAMPLES To undo the deletion for a subordinate CA: - $ gcloud privateca subordinates undelete server-tls-1 --pool=my-pool - --location=us-west1 + $ gcloud privateca subordinates undelete server-tls-1 \ + --pool=my-pool --location=us-west1 POSITIONAL ARGUMENTS CERTIFICATE AUTHORITY resource - The certificate authority to delete. The diff --git a/gcloud/privateca/subordinates/describe b/gcloud/privateca/subordinates/describe index 6d0b6c76a..237a47baa 100644 --- a/gcloud/privateca/subordinates/describe +++ b/gcloud/privateca/subordinates/describe @@ -15,15 +15,13 @@ EXAMPLES and location 'us-west1': $ gcloud privateca subordinates describe server-tls-1 \ - --location=us-west1 \ - --pool=my-pool + --location=us-west1 --pool=my-pool To download the PEM-encoded CA certificate chain for the 'server-tls-1' CA in location 'us-west1' to a file called 'server-tls-1.crt': $ gcloud privateca subordinates describe server-tls-1 \ - --location=us-west1 \ - --pool=my-pool \ + --location=us-west1 --pool=my-pool \ --format="value(pemCaCertificates)" > ./server-tls-1.crt POSITIONAL ARGUMENTS diff --git a/gcloud/privateca/subordinates/update b/gcloud/privateca/subordinates/update index 7e9d15e91..26f9bb5a0 100644 --- a/gcloud/privateca/subordinates/update +++ b/gcloud/privateca/subordinates/update @@ -11,17 +11,13 @@ SYNOPSIS EXAMPLES To update labels on a subordinate CA: - $ gcloud privateca subordinates update server-tls-1 \ - --pool=my-pool \ - --location=us-west1 \ - --update-labels=foo=bar + $ gcloud privateca subordinates update server-tls-1 --pool=my-pool \ + --location=us-west1 --update-labels=foo=bar To update the CA certificate chain for a subordinate CA: - $ gcloud privateca subordinates update server-tls-1 \ - --pool=my-pool \ - --location=us-west1 \ - --pem-chain=pem_chain.txt + $ gcloud privateca subordinates update server-tls-1 --pool=my-pool \ + --location=us-west1 --pem-chain=pem_chain.txt POSITIONAL ARGUMENTS CERTIFICATE AUTHORITY resource - The certificate authority to update. The diff --git a/gcloud/privateca/templates/add-iam-policy-binding b/gcloud/privateca/templates/add-iam-policy-binding index 280ff2549..80a4380a7 100644 --- a/gcloud/privateca/templates/add-iam-policy-binding +++ b/gcloud/privateca/templates/add-iam-policy-binding @@ -22,9 +22,8 @@ EXAMPLES 'mtls-template' with the location 'us-west1', run: $ gcloud privateca templates add-iam-policy-binding mtls-template \ - --location='us-west1' \ - --member='user:test-user@gmail.com' \ - --role='roles/privateca.templateUser' + --location='us-west1' --member='user:test-user@gmail.com' \ + --role='roles/privateca.templateUser' POSITIONAL ARGUMENTS Certificate Template resource - The certificate template for which to add diff --git a/gcloud/privateca/templates/remove-iam-policy-binding b/gcloud/privateca/templates/remove-iam-policy-binding index 7cb39be50..5f3e124d2 100644 --- a/gcloud/privateca/templates/remove-iam-policy-binding +++ b/gcloud/privateca/templates/remove-iam-policy-binding @@ -22,9 +22,8 @@ EXAMPLES certificate template 'my-template' with the location 'us-west1', run: $ gcloud privateca templates remove-iam-policy-binding my-template \ - --location=us-west1 \ - --member='user:test-user@gmail.com' \ - --role='roles/privateca.templateUser' + --location=us-west1 --member='user:test-user@gmail.com' \ + --role='roles/privateca.templateUser' POSITIONAL ARGUMENTS Certificate Template resource - The certificate template for which to diff --git a/gcloud/pubsub/lite-reservations/create b/gcloud/pubsub/lite-reservations/create index d2838c101..92e9bb197 100644 --- a/gcloud/pubsub/lite-reservations/create +++ b/gcloud/pubsub/lite-reservations/create @@ -12,8 +12,7 @@ EXAMPLES To create a Pub/Sub lite-reservation, run: $ gcloud pubsub lite-reservations create myreservation \ - --location=us-central1 \ - --throughput-capacity=2 + --location=us-central1 --throughput-capacity=2 POSITIONAL ARGUMENTS RESERVATION diff --git a/gcloud/pubsub/lite-reservations/delete b/gcloud/pubsub/lite-reservations/delete index b22349ed6..f0c1183a8 100644 --- a/gcloud/pubsub/lite-reservations/delete +++ b/gcloud/pubsub/lite-reservations/delete @@ -12,7 +12,7 @@ EXAMPLES To delete a Pub/Sub Lite reservation, run: $ gcloud pubsub lite-reservations delete myreservation \ - --location=us-central1 + --location=us-central1 POSITIONAL ARGUMENTS Reservation resource - Reservation to delete. The arguments in this group diff --git a/gcloud/pubsub/lite-reservations/describe b/gcloud/pubsub/lite-reservations/describe index 7c405ed9a..ea3d51938 100644 --- a/gcloud/pubsub/lite-reservations/describe +++ b/gcloud/pubsub/lite-reservations/describe @@ -13,7 +13,7 @@ EXAMPLES To describe a Pub/Sub Lite reservation, run: $ gcloud pubsub lite-reservations describe myreservation \ - --location=us-central1 + --location=us-central1 POSITIONAL ARGUMENTS Reservation resource - Reservation to describe. The arguments in this diff --git a/gcloud/pubsub/lite-reservations/list b/gcloud/pubsub/lite-reservations/list index f2e7012ba..0f1d57618 100644 --- a/gcloud/pubsub/lite-reservations/list +++ b/gcloud/pubsub/lite-reservations/list @@ -13,7 +13,7 @@ EXAMPLES To list Pub/Sub Lite reservations, run: $ gcloud pubsub lite-reservations list --location=us-central1 \ - --limit=5 + --limit=5 REQUIRED FLAGS Location resource - Location to list reservations for. This represents a diff --git a/gcloud/pubsub/lite-reservations/list-topics b/gcloud/pubsub/lite-reservations/list-topics index af77678ab..c7f7a6607 100644 --- a/gcloud/pubsub/lite-reservations/list-topics +++ b/gcloud/pubsub/lite-reservations/list-topics @@ -15,7 +15,7 @@ EXAMPLES To list Pub/Sub Lite topics for a given Lite reservation, run: $ gcloud pubsub lite-reservations list-topics myreservation \ - --location=us-central1 + --location=us-central1 POSITIONAL ARGUMENTS Reservation resource - Reservation to list topics for. The arguments in diff --git a/gcloud/pubsub/lite-reservations/update b/gcloud/pubsub/lite-reservations/update index 07ced8c81..42fd22785 100644 --- a/gcloud/pubsub/lite-reservations/update +++ b/gcloud/pubsub/lite-reservations/update @@ -12,8 +12,7 @@ EXAMPLES To update a Pub/Sub Lite reservation, run: $ gcloud pubsub lite-reservations update myreservation \ - --location=us-central1 \ - --throughput-capacity=2 + --location=us-central1 --throughput-capacity=2 POSITIONAL ARGUMENTS Reservation resource - Reservation to update. The arguments in this group diff --git a/gcloud/pubsub/lite-subscriptions/ack-up-to b/gcloud/pubsub/lite-subscriptions/ack-up-to index 5c5ac6cb8..b7713ab66 100644 --- a/gcloud/pubsub/lite-subscriptions/ack-up-to +++ b/gcloud/pubsub/lite-subscriptions/ack-up-to @@ -16,9 +16,7 @@ EXAMPLES To acknowledge messages on a Pub/Sub Lite subscription, run: $ gcloud pubsub lite-subscriptions ack-up-to mysubscription \ - --location=us-central1-a \ - --partition=0 \ - --offset=10 + --location=us-central1-a --partition=0 --offset=10 POSITIONAL ARGUMENTS Subscription resource - Subscription on which to acknowledge messages. The diff --git a/gcloud/pubsub/lite-subscriptions/create b/gcloud/pubsub/lite-subscriptions/create index a8c25d74d..80b95238e 100644 --- a/gcloud/pubsub/lite-subscriptions/create +++ b/gcloud/pubsub/lite-subscriptions/create @@ -16,16 +16,14 @@ EXAMPLES To create a Pub/Sub Lite subscription, run: $ gcloud pubsub lite-subscriptions create mysubscription \ - --location=us-central1-a \ - --topic=mytopic + --location=us-central1-a --topic=mytopic To create a Pub/Sub Lite subscription at the offset of the oldest retained message, run: $ gcloud pubsub lite-subscriptions create mysubscription \ - --location=us-central1-a \ - --topic=mytopic \ - --starting-offset=beginning + --location=us-central1-a --topic=mytopic \ + --starting-offset=beginning POSITIONAL ARGUMENTS SUBSCRIPTION diff --git a/gcloud/pubsub/lite-subscriptions/delete b/gcloud/pubsub/lite-subscriptions/delete index aeed173a6..78c5eb71d 100644 --- a/gcloud/pubsub/lite-subscriptions/delete +++ b/gcloud/pubsub/lite-subscriptions/delete @@ -13,7 +13,7 @@ EXAMPLES To delete a Pub/Sub Lite subscription, run: $ gcloud pubsub lite-subscriptions delete mysubscription \ - --location=us-central1-a + --location=us-central1-a POSITIONAL ARGUMENTS Subscription resource - Subscription to delete. The arguments in this diff --git a/gcloud/pubsub/lite-subscriptions/describe b/gcloud/pubsub/lite-subscriptions/describe index 230ed7757..ed1118564 100644 --- a/gcloud/pubsub/lite-subscriptions/describe +++ b/gcloud/pubsub/lite-subscriptions/describe @@ -13,7 +13,7 @@ EXAMPLES To describe a Pub/Sub Lite subscription, run: $ gcloud pubsub lite-subscriptions describe mysubscription \ - --location=us-central1-a + --location=us-central1-a POSITIONAL ARGUMENTS Subscription resource - Subscription to describe. The arguments in this diff --git a/gcloud/pubsub/lite-subscriptions/list b/gcloud/pubsub/lite-subscriptions/list index e51b52f7a..1accad2ad 100644 --- a/gcloud/pubsub/lite-subscriptions/list +++ b/gcloud/pubsub/lite-subscriptions/list @@ -13,7 +13,7 @@ EXAMPLES To list Pub/Sub Lite subscriptions, run: $ gcloud pubsub lite-subscriptions list --location=us-central1-a \ - --limit=5 + --limit=5 FLAGS Location resource - ID of the location or fully qualified identifier for diff --git a/gcloud/pubsub/lite-subscriptions/seek b/gcloud/pubsub/lite-subscriptions/seek index 3bf4a66da..96b3ef449 100644 --- a/gcloud/pubsub/lite-subscriptions/seek +++ b/gcloud/pubsub/lite-subscriptions/seek @@ -22,16 +22,14 @@ EXAMPLES backlog, run: $ gcloud pubsub lite-subscriptions seek mysubscription \ - --location=us-central1-a \ - --starting-offset=beginning + --location=us-central1-a --starting-offset=beginning To seek a Pub/Sub Lite subscription to a publish time without waiting for the operation to complete, run: $ gcloud pubsub lite-subscriptions seek mysubscription \ - --location=us-central1-a \ - --publish-time="2021-01-01T12:00:00Z" - --async + --location=us-central1-a --publish-time="2021-01-01T12:00:00Z" \ + --async POSITIONAL ARGUMENTS Subscription resource - Subscription to seek. The arguments in this group diff --git a/gcloud/pubsub/lite-subscriptions/update b/gcloud/pubsub/lite-subscriptions/update index d7b1cb1a7..e571597a5 100644 --- a/gcloud/pubsub/lite-subscriptions/update +++ b/gcloud/pubsub/lite-subscriptions/update @@ -14,8 +14,8 @@ EXAMPLES To update a Cloud Pub/Sub lite-subscription, run: $ gcloud pubsub lite-subscriptions update mysubscription \ - --location=us-central1-a \ - --delivery-requirement=DELIVER_IMMEDIATELY + --location=us-central1-a \ + --delivery-requirement=DELIVER_IMMEDIATELY POSITIONAL ARGUMENTS Subscription resource - Subscription to update. The arguments in this diff --git a/gcloud/pubsub/lite-topics/create b/gcloud/pubsub/lite-topics/create index 2e7d9f4d9..4d0e10e27 100644 --- a/gcloud/pubsub/lite-topics/create +++ b/gcloud/pubsub/lite-topics/create @@ -17,10 +17,8 @@ EXAMPLES To create a Pub/Sub lite-topic, run: $ gcloud pubsub lite-topics create mytopic \ - --location=us-central1-a \ - --partitions=1 \ - --per-partition-bytes=30GiB \ - --message-retention-period=2w + --location=us-central1-a --partitions=1 \ + --per-partition-bytes=30GiB --message-retention-period=2w POSITIONAL ARGUMENTS TOPIC diff --git a/gcloud/pubsub/lite-topics/delete b/gcloud/pubsub/lite-topics/delete index 986acc260..d2e851c6a 100644 --- a/gcloud/pubsub/lite-topics/delete +++ b/gcloud/pubsub/lite-topics/delete @@ -11,8 +11,7 @@ DESCRIPTION EXAMPLES To delete a Pub/Sub Lite topic, run: - $ gcloud pubsub lite-topics delete mytopic \ - --location=us-central1-a + $ gcloud pubsub lite-topics delete mytopic --location=us-central1-a POSITIONAL ARGUMENTS Topic resource - Topic to delete. The arguments in this group can be used diff --git a/gcloud/pubsub/lite-topics/describe b/gcloud/pubsub/lite-topics/describe index e38d0bf1b..0d1b03370 100644 --- a/gcloud/pubsub/lite-topics/describe +++ b/gcloud/pubsub/lite-topics/describe @@ -11,8 +11,7 @@ DESCRIPTION EXAMPLES To describe a Pub/Sub Lite topic, run: - $ gcloud pubsub lite-topics describe mytopic \ - --location=us-central1-a + $ gcloud pubsub lite-topics describe mytopic --location=us-central1-a POSITIONAL ARGUMENTS Topic resource - Topic to describe. The arguments in this group can be diff --git a/gcloud/pubsub/lite-topics/list b/gcloud/pubsub/lite-topics/list index 307b82d8d..660ddba46 100644 --- a/gcloud/pubsub/lite-topics/list +++ b/gcloud/pubsub/lite-topics/list @@ -12,8 +12,7 @@ DESCRIPTION EXAMPLES To list Pub/Sub Lite topics, run: - $ gcloud pubsub lite-topics list --location=us-central1-a \ - --limit=5 + $ gcloud pubsub lite-topics list --location=us-central1-a --limit=5 FLAGS Location resource - Zone to list topics for. This represents a Cloud diff --git a/gcloud/pubsub/lite-topics/list-subscriptions b/gcloud/pubsub/lite-topics/list-subscriptions index 8689e88ea..dec6b5a97 100644 --- a/gcloud/pubsub/lite-topics/list-subscriptions +++ b/gcloud/pubsub/lite-topics/list-subscriptions @@ -14,7 +14,7 @@ EXAMPLES To list Pub/Sub Lite subscriptions for a given Lite topic, run: $ gcloud pubsub lite-topics list-subscriptions mytopic \ - --location=us-central1-a + --location=us-central1-a POSITIONAL ARGUMENTS Topic resource - Topic to list subscriptions for. The arguments in this diff --git a/gcloud/pubsub/lite-topics/update b/gcloud/pubsub/lite-topics/update index 39be92edc..8f3046c5b 100644 --- a/gcloud/pubsub/lite-topics/update +++ b/gcloud/pubsub/lite-topics/update @@ -17,8 +17,7 @@ EXAMPLES To update a Pub/Sub Lite topic, run: $ gcloud pubsub lite-topics update mytopic \ - --location=us-central1-a \ - --per-partition-publish-mib=10 + --location=us-central1-a --per-partition-publish-mib=10 POSITIONAL ARGUMENTS Topic resource - Topic to update. The arguments in this group can be used diff --git a/gcloud/pubsub/subscriptions/add-iam-policy-binding b/gcloud/pubsub/subscriptions/add-iam-policy-binding index f5a0e161a..ad0ea386a 100644 --- a/gcloud/pubsub/subscriptions/add-iam-policy-binding +++ b/gcloud/pubsub/subscriptions/add-iam-policy-binding @@ -23,8 +23,8 @@ EXAMPLES $ gcloud pubsub subscriptions add-iam-policy-binding \ my-subscription \ - --member='serviceAccount:my-iam-account@my-project.iam.gserviceaccount.com' \ - --role='roles/editor' + --member='serviceAccount:my-iam-account@my-project.iam.gservicea\ + ccount.com' --role='roles/editor' See https://cloud.google.com/iam/docs/managing-policies for details of policy role and member types. diff --git a/gcloud/recommender/recommendations/describe b/gcloud/recommender/recommendations/describe index 9d97a13ce..3c9c7e688 100644 --- a/gcloud/recommender/recommendations/describe +++ b/gcloud/recommender/recommendations/describe @@ -17,8 +17,8 @@ EXAMPLES To describe a recommendation: $ gcloud recommender recommendations describe RECOMMENDATION_ID \ - --project=${PROJECT} --location=${LOCATION} - --recommender=${RECOMMENDER} + --project=${PROJECT} --location=${LOCATION} \ + --recommender=${RECOMMENDER} POSITIONAL ARGUMENTS RECOMMENDATION diff --git a/gcloud/recommender/recommendations/list b/gcloud/recommender/recommendations/list index 614451d76..5d8eb3ee0 100644 --- a/gcloud/recommender/recommendations/list +++ b/gcloud/recommender/recommendations/list @@ -11,7 +11,7 @@ SYNOPSIS [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - This command will list all recommendations for a give cloud_entity_id, + This command will list all recommendations for a given cloud_entity_id, location and recommender. Supported recommenders can be found here: https://cloud.google.com/recommender/docs/recommenders. Currently the following cloud_entity_types are supported: project, billing_account, diff --git a/gcloud/recommender/recommendations/mark-claimed b/gcloud/recommender/recommendations/mark-claimed index ecefac2f5..e804880e8 100644 --- a/gcloud/recommender/recommendations/mark-claimed +++ b/gcloud/recommender/recommendations/mark-claimed @@ -20,9 +20,9 @@ EXAMPLES To mark a recommendation as CLAIMED: $ gcloud recommender recommendations mark-claimed RECOMMENDATION \ - --project=project-name --location=global - --recommender=google.compute.instance.MachineTypeRecommender --etag=abc123 - --state-metadata=key1=value1,key2=value2 + --project=project-name --location=global \ + --recommender=google.compute.instance.MachineTypeRecommender \ + --etag=abc123 --state-metadata=key1=value1,key2=value2 POSITIONAL ARGUMENTS RECOMMENDATION diff --git a/gcloud/scc/bqexports/create b/gcloud/scc/bqexports/create new file mode 100644 index 000000000..add52e220 --- /dev/null +++ b/gcloud/scc/bqexports/create @@ -0,0 +1,111 @@ +NAME + gcloud scc bqexports create - create a Cloud Security Command Center + BigQuery export + +SYNOPSIS + gcloud scc bqexports create BIG_QUERY_EXPORT --dataset=DATASET + [--description=DESCRIPTION] [--filter=FILTER] + [--folder=FOLDER | --organization=ORGANIZATION | --project=PROJECT] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Create a Cloud Security Command Center BigQuery export. + +EXAMPLES + To create a BigQuery export my-bq-export given organization 123 with a + dataset abc in project 234 and filter on category that equals to + XSS_SCRIPTING, run: + + $ gcloud scc bqexports create my-bq-export \ + --organization=organizations/123 \ + --dataset=projects/234/datasets/abc \ + --description="This is a test BigQuery export" \ + --filter="category=\"XSS_SCRIPTING\"" + $ gcloud scc bqexports create my-bq-export --organization=123 \ + --dataset=projects/234/datasets/abc \ + --description="This is a test BigQuery export" \ + --filter="category=\"XSS_SCRIPTING\"" + $ gcloud scc bqexports create \ + organizations/123/bigQueryExports/my-bq-export \ + --dataset=projects/234/datasets/abc \ + --description="This is a test BigQuery export" \ + --filter="category=\"XSS_SCRIPTING\"" + + To create a BigQuery export my-bq-export given folder 456 with a dataset + abc in project 234 and filter on category that equals to XSS_SCRIPTING, + run: + + $ gcloud scc bqexports create my-bq-export --folder=folders/456 \ + --dataset=projects/234/datasets/abc \ + --description="This is a test BigQuery export" \ + --filter="category=\"XSS_SCRIPTING\"" + $ gcloud scc bqexports create my-bq-export --folder=456 \ + --dataset=projects/234/datasets/abc \ + --description="This is a test BigQuery export" \ + --filter="category=\"XSS_SCRIPTING\"" + $ gcloud scc bqexports create \ + folders/456/bigQueryExports/my-bq-export \ + --dataset=projects/234/datasets/abc \ + --description="This is a test BigQuery export" \ + --filter="category=\"XSS_SCRIPTING\"" + + To create a BigQuery export my-bq-export given project 789 with a dataset + abc in project 234 and filter on category that equals to XSS_SCRIPTING, + run: + + $ gcloud scc bqexports create my-bq-export --project=projects/789 \ + --dataset=projects/234/datasets/abc \ + --description="This is a test BigQuery export" \ + --filter="category=\"XSS_SCRIPTING\"" + $ gcloud scc bqexports create my-bq-export --project=789 \ + --dataset=projects/234/datasets/abc \ + --description="This is a test BigQuery export" \ + --filter="category=\"XSS_SCRIPTING\"" + $ gcloud scc bqexports create \ + projects/789/bigQueryExports/my-bq-export \ + --dataset=projects/234/datasets/abc \ + --description="This is a test BigQuery export" \ + --filter="category=\"XSS_SCRIPTING\"" + +POSITIONAL ARGUMENTS + BIG_QUERY_EXPORT + ID of the BigQuery export or the full resource name of the BigQuery + export. + +REQUIRED FLAGS + --dataset=DATASET + The dataset to write findings updates to. + +OPTIONAL FLAGS + --description=DESCRIPTION + The text that will be used to describe a BigQuery export. + + --filter=FILTER + The filter string which will applied to findings muted by a BigQuery + export. + + At most one of these can be specified: + + --folder=FOLDER + Folder where the BigQuery export resides. Formatted as folders/456 or + just 456. + + --organization=ORGANIZATION + Organization where the BigQuery export resides. Formatted as + organizations/123 or just 123. + + --project=PROJECT + Project (id or number) where the BigQuery export resides. Formatted + as projects/789 or just 789. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --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/v1 API. The full documentation for + this API can be found at: https://cloud.google.com/security-command-center diff --git a/gcloud/scc/bqexports/delete b/gcloud/scc/bqexports/delete new file mode 100644 index 000000000..ea91fee7d --- /dev/null +++ b/gcloud/scc/bqexports/delete @@ -0,0 +1,67 @@ +NAME + gcloud scc bqexports delete - delete a Cloud Security Command Center + BigQuery export + +SYNOPSIS + gcloud scc bqexports delete BIG_QUERY_EXPORT + [--folder=FOLDER | --organization=ORGANIZATION | --project=PROJECT] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Delete a Cloud Security Command Center BigQuery export. + +EXAMPLES + To delete a BigQuery export given organization 123 with id my-bq-export, + run: + + $ gcloud scc bqexports delete my-bq-export \ + --organization=organizations/123 + $ gcloud scc bqexports delete my-bq-export --organization=123 + $ gcloud scc bqexports delete \ + organizations/123/bigQueryExports/my-bq-export + + To delete a BigQuery export given folder 456 with id my-bq-export, run: + + $ gcloud scc bqexports delete my-bq-export --folder=folders/456 + $ gcloud scc bqexports delete my-bq-export --folder=456 + $ gcloud scc bqexports delete \ + folders/456/bigQueryExports/my-bq-export + + To delete a BigQuery export given project 789 with id my-bq-export, run: + + $ gcloud scc bqexports delete my-bq-export --project=projects/789 + $ gcloud scc bqexports delete my-bq-export --project=789 + $ gcloud scc bqexports delete \ + projects/789/bigQueryExports/my-bq-export + +POSITIONAL ARGUMENTS + BIG_QUERY_EXPORT + ID of the BigQuery export or the full resource name of the BigQuery + export. + +FLAGS + At most one of these can be specified: + + --folder=FOLDER + Folder where the BigQuery export resides. Formatted as folders/456 or + just 456. + + --organization=ORGANIZATION + Organization where the BigQuery export resides. Formatted as + organizations/123 or just 123. + + --project=PROJECT + Project (id or number) where the BigQuery export resides. Formatted + as projects/789 or just 789. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --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/v1 API. The full documentation for + this API can be found at: https://cloud.google.com/security-command-center diff --git a/gcloud/scc/bqexports/get b/gcloud/scc/bqexports/get new file mode 100644 index 000000000..cb09ffbe6 --- /dev/null +++ b/gcloud/scc/bqexports/get @@ -0,0 +1,65 @@ +NAME + gcloud scc bqexports get - get a Cloud Security Command Center BigQuery + export + +SYNOPSIS + gcloud scc bqexports get BIG_QUERY_EXPORT + [--folder=FOLDER | --organization=ORGANIZATION | --project=PROJECT] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Get a Cloud Security Command Center BigQuery export. + +EXAMPLES + To get a BigQuery export under given organization 123 with id my-bq-export, + run: + + $ gcloud scc bqexports get my-bq-export \ + --organization=organizations/123 + $ gcloud scc bqexports get my-bq-export --organization=123 + $ gcloud scc bqexports get \ + organizations/123/bigQueryExports/bq-export + + To get a BigQuery export under given folder 456 with id my-bq-export, run: + + $ gcloud scc bqexports get my-bq-export --folder=folders/456 + $ gcloud scc bqexports get my-bq-export --folder=456 + $ gcloud scc bqexports get folders/456/bigQueryExports/my-bq-export + + To get a BigQuery export under given project 789 with id my-bq-export, run: + + $ gcloud scc bqexports get my-bq-export --project=projects/789 + $ gcloud scc bqexports get my-bq-export --project=789 + $ gcloud scc bqexports get projects/789/bigQueryExports/my-bq-export + +POSITIONAL ARGUMENTS + BIG_QUERY_EXPORT + ID of the BigQuery export or the full resource name of the BigQuery + export. + +FLAGS + At most one of these can be specified: + + --folder=FOLDER + Folder where the BigQuery export resides. Formatted as folders/456 or + just 456. + + --organization=ORGANIZATION + Organization where the BigQuery export resides. Formatted as + organizations/123 or just 123. + + --project=PROJECT + Project (id or number) where the BigQuery export resides. Formatted + as projects/789 or just 789. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --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/v1 API. The full documentation for + this API can be found at: https://cloud.google.com/security-command-center diff --git a/gcloud/scc/bqexports/help b/gcloud/scc/bqexports/help new file mode 100644 index 000000000..1a4630c08 --- /dev/null +++ b/gcloud/scc/bqexports/help @@ -0,0 +1,29 @@ +NAME + gcloud scc bqexports - manage Cloud SCC (Security Command Center) BigQuery + exports + +SYNOPSIS + gcloud scc bqexports COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Manage Cloud SCC (Security Command Center) BigQuery exports. + +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 Cloud Security Command Center BigQuery export. + + delete + Delete a Cloud Security Command Center BigQuery export. + + get + Get a Cloud Security Command Center BigQuery export. + + list + List Cloud Security Command Center BigQuery exports. diff --git a/gcloud/scc/bqexports/list b/gcloud/scc/bqexports/list new file mode 100644 index 000000000..2603308ad --- /dev/null +++ b/gcloud/scc/bqexports/list @@ -0,0 +1,81 @@ +NAME + gcloud scc bqexports list - list Cloud Security Command Center BigQuery + exports + +SYNOPSIS + gcloud scc bqexports list + (--folder=FOLDER | --organization=ORGANIZATION | --project=PROJECT) + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + List Cloud Security Command Center BigQuery exports. + +EXAMPLES + List BigQuery exports under organization 123: + + $ gcloud scc bqexports list --organization=organizations/123 + $ gcloud scc bqexports list --organization=123 + + List BigQuery exports under folder 456: + + $ gcloud scc bqexports list --folder=folders/456 + $ gcloud scc bqexports list --folder=456 + + List BigQuery exports under project 789: + + $ gcloud scc bqexports list --project=projects/789 + $ gcloud scc bqexports list --project=789 + +REQUIRED FLAGS + Exactly one of these must be specified: + + --folder=FOLDER + Folder where the BigQuery export resides. Formatted as folders/456 or + just 456. + + --organization=ORGANIZATION + Organization where the BigQuery export resides. Formatted as + organizations/123 or just 123. + + --project=PROJECT + Project (id or number) where the BigQuery export resides. Formatted + as projects/789 or just 789. + +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/v1 API. The full documentation for + this API can be found at: https://cloud.google.com/security-command-center diff --git a/gcloud/scc/findings/list b/gcloud/scc/findings/list index 51b082959..cfb4b777e 100644 --- a/gcloud/scc/findings/list +++ b/gcloud/scc/findings/list @@ -33,7 +33,7 @@ EXAMPLES Only list category and resource_name of all ACTIVE findings under organization 123456 and source 5678: - $ gcloud scc findings list 123456 --source=5678 \ + $ gcloud scc findings list 123456 --source=5678 \ --filter="state=\"ACTIVE\"" \ --field-mask="finding.category,finding.resource_name" diff --git a/gcloud/scc/help b/gcloud/scc/help index 80b237a05..0641c5078 100644 --- a/gcloud/scc/help +++ b/gcloud/scc/help @@ -18,6 +18,9 @@ GROUPS assets Manage Cloud SCC (Security Command Center) assets. + bqexports + Manage Cloud SCC (Security Command Center) BigQuery exports. + findings Manage Cloud SCC (Security Command Center) findings. diff --git a/gcloud/scheduler/jobs/create/app-engine b/gcloud/scheduler/jobs/create/app-engine index 42763f789..fac15ec2b 100644 --- a/gcloud/scheduler/jobs/create/app-engine +++ b/gcloud/scheduler/jobs/create/app-engine @@ -26,8 +26,7 @@ EXAMPLES '/cron-handler' path in you App Engine app every 3 hours: $ gcloud scheduler jobs create app-engine my-job \ - --schedule="0 */3 * * *" - --relative-url="/cron-handler" + --schedule="0 */3 * * *" --relative-url="/cron-handler" POSITIONAL ARGUMENTS Job resource - Job to create. The arguments in this group can be used to diff --git a/gcloud/scheduler/jobs/create/http b/gcloud/scheduler/jobs/create/http index 26d2efc5e..1ae0a3fea 100644 --- a/gcloud/scheduler/jobs/create/http +++ b/gcloud/scheduler/jobs/create/http @@ -27,8 +27,9 @@ EXAMPLES The following command creates a job that sends a HTTP GET request to 'http://example.com/path' every 3 hours: - $ gcloud scheduler jobs create http my-job --schedule="0 */3 * * *" - --uri="http://example.com/path" --http-method=GET + $ gcloud scheduler jobs create http my-job \ + --schedule="0 */3 * * *" --uri="http://example.com/path" \ + --http-method=GET POSITIONAL ARGUMENTS Job resource - Job to create. The arguments in this group can be used to diff --git a/gcloud/scheduler/jobs/create/pubsub b/gcloud/scheduler/jobs/create/pubsub index e50603d40..4e98a3814 100644 --- a/gcloud/scheduler/jobs/create/pubsub +++ b/gcloud/scheduler/jobs/create/pubsub @@ -21,8 +21,9 @@ EXAMPLES The following command creates a job that publishes a message with the body 'Hello' to the Pub/Sub topic 'cron-topic' every 3 hours: - $ gcloud scheduler jobs create pubsub my-job --schedule="0 */3 * * *" - --topic=cron-topic --message-body="Hello" + $ gcloud scheduler jobs create pubsub my-job \ + --schedule="0 */3 * * *" --topic=cron-topic \ + --message-body="Hello" POSITIONAL ARGUMENTS Job resource - Job to create. The arguments in this group can be used to diff --git a/gcloud/secrets/create b/gcloud/secrets/create index d2d76cf68..1e31634da 100644 --- a/gcloud/secrets/create +++ b/gcloud/secrets/create @@ -30,23 +30,23 @@ EXAMPLES Create a new secret named 'my-secret' in 'us-central1' with data from a file: - $ gcloud secrets create my-secret --data-file=/tmp/secret - --replication-policy=user-managed \ - --locations=us-central1 + $ gcloud secrets create my-secret --data-file=/tmp/secret \ + --replication-policy=user-managed --locations=us-central1 Create a new secret named 'my-secret' in 'us-central1' and 'us-east1' with the value "s3cr3t": - $ printf "s3cr3t" | gcloud secrets create my-secret --data-file=- - --replication-policy=user-managed --locations=us-central1,us-east1 + $ printf "s3cr3t" | gcloud secrets create my-secret --data-file=- \ + --replication-policy=user-managed \ + --locations=us-central1,us-east1 Create a new secret named 'my-secret' in 'us-central1' and 'us-east1' with the value "s3cr3t" in PowerShell (Note: PowerShell will add a newline to the resulting secret): $ Write-Output "s3cr3t" | gcloud secrets create my-secret \ - --data-file=- - --replication-policy=user-managed --locations=us-central1,us-east1 + --data-file=- --replication-policy=user-managed \ + --locations=us-central1,us-east1 Create a secret with an automatic replication policy and a next rotation time: @@ -57,8 +57,8 @@ EXAMPLES Create a secret with an automatic replication policy and a rotation period: $ gcloud secrets create my-secret \ - --next-rotation-time="2030-01-01T15:30:00-05:00" - --rotation-period="7200s" + --next-rotation-time="2030-01-01T15:30:00-05:00" \ + --rotation-period="7200s" POSITIONAL ARGUMENTS Secret resource - The secret to create. This represents a Cloud resource. diff --git a/gcloud/secrets/update b/gcloud/secrets/update index 8e0a86a28..ba116b4f9 100644 --- a/gcloud/secrets/update +++ b/gcloud/secrets/update @@ -35,8 +35,8 @@ EXAMPLES Update a secret to have a next-rotation-time and rotation-period: $ gcloud secrets update my-secret \ - --next-rotation-time="2030-01-01T15:30:00-05:00" - --rotation-period="7200s" + --next-rotation-time="2030-01-01T15:30:00-05:00" \ + --rotation-period="7200s" Update a secret to remove the next-rotation-time: diff --git a/gcloud/service-directory/endpoints/create b/gcloud/service-directory/endpoints/create index 128b577df..12195048f 100644 --- a/gcloud/service-directory/endpoints/create +++ b/gcloud/service-directory/endpoints/create @@ -17,7 +17,7 @@ EXAMPLES $ gcloud service-directory endpoints create my-endpoint \ --service=my-service --namespace=my-namespace \ --location=us-east1 --address=1.2.3.4 --port=5 \ - --annotations=a=b,c=d \ + --annotations=a=b,c=d \ --network=projects/123456789/locations/global/networks/default POSITIONAL ARGUMENTS diff --git a/gcloud/services/api-keys/describe b/gcloud/services/api-keys/describe index d1deffadf..05f1757d1 100644 --- a/gcloud/services/api-keys/describe +++ b/gcloud/services/api-keys/describe @@ -12,12 +12,9 @@ EXAMPLES To describe an API key: $ gcloud services api-keys describe \ - projects/myproject/locations/global/keys/1234 - OR - $ gcloud services api-keys describe 1234 - OR - $ gcloud services api-keys describe 1234 --project=myproject - OR + projects/myproject/locations/global/keys/1234 OR + $ gcloud services api-keys describe 1234 OR + $ gcloud services api-keys describe 1234 --project=myproject OR $ gcloud services api-keys describe 1234 --project=myproject \ --location=global diff --git a/gcloud/services/peered-dns-domains/create b/gcloud/services/peered-dns-domains/create index 5369a6e19..031a934f6 100644 --- a/gcloud/services/peered-dns-domains/create +++ b/gcloud/services/peered-dns-domains/create @@ -20,15 +20,14 @@ EXAMPLES my-network in the current project, run: $ gcloud services peered-dns-domains create example-com \ - --network=my-network \ - --service=peering-service --dns-suffix=example.com. + --network=my-network --service=peering-service \ + --dns-suffix=example.com. To run the same command asynchronously (non-blocking), run: $ gcloud services peered-dns-domains create example-com \ - --network=my-network \ - --service=peering-service --dns-suffix=example.com. \ - --async + --network=my-network --service=peering-service \ + --dns-suffix=example.com. --async POSITIONAL ARGUMENTS NAME diff --git a/gcloud/services/peered-dns-domains/delete b/gcloud/services/peered-dns-domains/delete index 9d6df94b0..769ba1263 100644 --- a/gcloud/services/peered-dns-domains/delete +++ b/gcloud/services/peered-dns-domains/delete @@ -16,14 +16,12 @@ EXAMPLES my-network in the current project, run: $ gcloud services peered-dns-domains delete example-com \ - --network=my-network \ - --service=peering-service + --network=my-network --service=peering-service To run the same command asynchronously (non-blocking), run: $ gcloud services peered-dns-domains delete example-com \ - --network=my-network \ - --service=peering-service --async + --network=my-network --service=peering-service --async POSITIONAL ARGUMENTS NAME diff --git a/gcloud/services/vpc-peerings/connect b/gcloud/services/vpc-peerings/connect index 83b861360..6d685a9e2 100644 --- a/gcloud/services/vpc-peerings/connect +++ b/gcloud/services/vpc-peerings/connect @@ -18,14 +18,13 @@ EXAMPLES the service to use, run: $ gcloud services vpc-peerings connect --network=my-network \ - --service=your-service \ - --ranges=google-range-1,google-range-2 + --service=your-service --ranges=google-range-1,google-range-2 To run the same command asynchronously (non-blocking), run: $ gcloud services vpc-peerings connect --network=my-network \ - --service=your-service \ - --ranges=google-range-1,google-range-2 --async + --service=your-service --ranges=google-range-1,google-range-2 \ + --async REQUIRED FLAGS --network=NETWORK diff --git a/gcloud/services/vpc-peerings/update b/gcloud/services/vpc-peerings/update index 1ef10c1c1..7d648bbf6 100644 --- a/gcloud/services/vpc-peerings/update +++ b/gcloud/services/vpc-peerings/update @@ -18,14 +18,13 @@ EXAMPLES google-range-1,google-range-2 for the service to use, run: $ gcloud services vpc-peerings update --network=my-network \ - --service=your-service \ - --ranges=google-range-1,google-range-2 + --service=your-service --ranges=google-range-1,google-range-2 To run the same command asynchronously (non-blocking), run: $ gcloud services vpc-peerings update --network=my-network \ - --service=your-service \ - --ranges=google-range-1,google-range-2 --async + --service=your-service --ranges=google-range-1,google-range-2 \ + --async REQUIRED FLAGS --network=NETWORK diff --git a/gcloud/source/project-configs/update b/gcloud/source/project-configs/update index 61e129b1d..eddbc5be9 100644 --- a/gcloud/source/project-configs/update +++ b/gcloud/source/project-configs/update @@ -19,8 +19,7 @@ EXAMPLES notifications, run: $ gcloud source project-configs update --add-topic=TOPIC_NAME \ - --service-account=SERVICE_ACCOUNT_EMAIL \ - --message-format=json + --service-account=SERVICE_ACCOUNT_EMAIL --message-format=json REQUIRED FLAGS Exactly one of these must be specified: diff --git a/gcloud/source/repos/clone b/gcloud/source/repos/clone index d523713b5..434d291eb 100644 --- a/gcloud/source/repos/clone +++ b/gcloud/source/repos/clone @@ -26,8 +26,8 @@ EXAMPLES $ gcloud source repos clone REPOSITORY_NAME DIRECTORY_NAME - $ cd DIRECTORY_NAME - ... create/edit files and create one or more commits ... + $ cd DIRECTORY_NAME ... create/edit files and create one or more \ + commits ... $ git push origin master diff --git a/gcloud/source/repos/update b/gcloud/source/repos/update index 354da46fc..b86ca573c 100644 --- a/gcloud/source/repos/update +++ b/gcloud/source/repos/update @@ -14,8 +14,7 @@ EXAMPLES notifications, run: $ gcloud source repos update --add-topic=TOPIC_NAME \ - --service-account=SERVICE_ACCOUNT_EMAIL \ - --message-format=json + --service-account=SERVICE_ACCOUNT_EMAIL --message-format=json POSITIONAL ARGUMENTS Repo resource - Name of the Cloud Source repository to update. This diff --git a/gcloud/spanner/databases/create b/gcloud/spanner/databases/create index 6f8750fb6..85d186fe4 100644 --- a/gcloud/spanner/databases/create +++ b/gcloud/spanner/databases/create @@ -18,12 +18,12 @@ EXAMPLES To create a Cloud Spanner database with populated schema, run: - $ gcloud spanner databases create testdb --instance=my-instance-id + $ gcloud spanner databases create testdb --instance=my-instance-id \ --ddl='CREATE TABLE mytable (a INT64, b INT64) PRIMARY KEY(a)' To create a Cloud Spanner database with the PostgreSQL dialect, run: - $ gcloud spanner databases create testdb --instance=my-instance-id + $ gcloud spanner databases create testdb --instance=my-instance-id \ --database-dialect=POSTGRESQL POSITIONAL ARGUMENTS diff --git a/gcloud/spanner/databases/ddl/update b/gcloud/spanner/databases/ddl/update index c0a86ed81..00133867b 100644 --- a/gcloud/spanner/databases/ddl/update +++ b/gcloud/spanner/databases/ddl/update @@ -13,7 +13,7 @@ EXAMPLES To add a column to a table in the given Cloud Spanner database, run: $ gcloud spanner databases ddl update my-database-id \ - --instance=my-instance-id + --instance=my-instance-id \ --ddl='ALTER TABLE test_table ADD COLUMN a INT64' POSITIONAL ARGUMENTS diff --git a/gcloud/spanner/databases/sessions/delete b/gcloud/spanner/databases/sessions/delete index 1ae47fa03..a636b6535 100644 --- a/gcloud/spanner/databases/sessions/delete +++ b/gcloud/spanner/databases/sessions/delete @@ -13,8 +13,7 @@ EXAMPLES To delete a Cloud Spanner session, run: $ gcloud spanner databases sessions delete my-session-id \ - --instance=my-instance-id - --database=my-database-id + --instance=my-instance-id --database=my-database-id POSITIONAL ARGUMENTS Session resource - The Cloud Spanner session to delete. The arguments in diff --git a/gcloud/spanner/operations/cancel b/gcloud/spanner/operations/cancel index e5aa494e8..bc8e8977e 100644 --- a/gcloud/spanner/operations/cancel +++ b/gcloud/spanner/operations/cancel @@ -16,15 +16,13 @@ EXAMPLES To cancel a database operation with ID auto_12345, run: - $ gcloud spanner operations cancel _auto_12345 \ - --instance=my-instance-id - --database=my-database-id + $ gcloud spanner operations cancel _auto_12345 \ + --instance=my-instance-id --database=my-database-id To cancel a backup operation with ID auto_12345, run: - $ gcloud spanner operations cancel _auto_12345 \ - --instance=my-instance-id - --backup=my-backup-id + $ gcloud spanner operations cancel _auto_12345 \ + --instance=my-instance-id --backup=my-backup-id POSITIONAL ARGUMENTS OPERATION-ID diff --git a/gcloud/spanner/operations/describe b/gcloud/spanner/operations/describe index f0d2884c0..bd503f4ba 100644 --- a/gcloud/spanner/operations/describe +++ b/gcloud/spanner/operations/describe @@ -16,15 +16,13 @@ EXAMPLES To describe a Cloud Spanner database operation, run: - $ gcloud spanner operations describe _auto_12345 \ - --instance=my-instance-id - --database=my-database-id + $ gcloud spanner operations describe _auto_12345 \ + --instance=my-instance-id --database=my-database-id To describe a Cloud Spanner backup operation, run: - $ gcloud spanner operations describe _auto_12345 \ - --instance=my-instance-id - --backup=my-backup-id + $ gcloud spanner operations describe _auto_12345 \ + --instance=my-instance-id --backup=my-backup-id POSITIONAL ARGUMENTS OPERATION-ID diff --git a/gcloud/sql/import/sql b/gcloud/sql/import/sql index c86842548..76b31a130 100644 --- a/gcloud/sql/import/sql +++ b/gcloud/sql/import/sql @@ -17,7 +17,7 @@ EXAMPLES To import data from a SQL dump file into a database, testdb, on the specified Cloud SQL instance test-instance-1, run: - $ gcloud sql import sql test-instance-1 \ + $ gcloud sql import sql test-instance-1 \ gs://test-bucket/test-file.sql.gz --database=testdb POSITIONAL ARGUMENTS diff --git a/gcloud/tasks/create-http-task b/gcloud/tasks/create-http-task index b4a4470e9..2c765a27d 100644 --- a/gcloud/tasks/create-http-task +++ b/gcloud/tasks/create-http-task @@ -18,7 +18,7 @@ DESCRIPTION EXAMPLES To create a task: - $ gcloud tasks create-http-task --queue=my-queue + $ gcloud tasks create-http-task --queue=my-queue \ --url=http://example.com/handler-path my-task POSITIONAL ARGUMENTS diff --git a/gcloud/tasks/queues/create b/gcloud/tasks/queues/create index 1d095f22d..89142b166 100644 --- a/gcloud/tasks/queues/create +++ b/gcloud/tasks/queues/create @@ -18,13 +18,10 @@ DESCRIPTION EXAMPLES To create a Cloud Tasks queue: - $ gcloud tasks queues create my-queue - --max-attempts=10 --max-retry-duration=5s - --max-doublings=4 --min-backoff=1s - --max-backoff=10s - --max-dispatches-per-second=100 - --max-concurrent-dispatches=10 - --routing-override=service:abc + $ gcloud tasks queues create my-queue --max-attempts=10 \ + --max-retry-duration=5s --max-doublings=4 --min-backoff=1s \ + --max-backoff=10s --max-dispatches-per-second=100 \ + --max-concurrent-dispatches=10 --routing-override=service:abc POSITIONAL ARGUMENTS QUEUE diff --git a/gcloud/tasks/queues/update b/gcloud/tasks/queues/update index e2844bd07..874669fb4 100644 --- a/gcloud/tasks/queues/update +++ b/gcloud/tasks/queues/update @@ -23,13 +23,11 @@ DESCRIPTION EXAMPLES To update a Cloud Tasks queue: - $ gcloud tasks queues update my-queue - --clear-max-attempts --clear-max-retry-duration - --clear-max-doublings --clear-min-backoff - --clear-max-backoff - --clear-max-dispatches-per-second - --clear-max-concurrent-dispatches - --clear-routing-override + $ gcloud tasks queues update my-queue --clear-max-attempts \ + --clear-max-retry-duration --clear-max-doublings \ + --clear-min-backoff --clear-max-backoff \ + --clear-max-dispatches-per-second \ + --clear-max-concurrent-dispatches --clear-routing-override POSITIONAL ARGUMENTS QUEUE