From 5fec13c692129ef9c1aa4144cd7388a329bb5bed Mon Sep 17 00:00:00 2001 From: Automated Date: Wed, 10 Jan 2024 10:17:49 +0000 Subject: [PATCH] gcloud: Wed Jan 10 10:17:49 UTC 2024 --- gcloud/_version | 8 +- gcloud/ai/model-monitoring-jobs/create | 5 + gcloud/ai/model-monitoring-jobs/update | 5 + gcloud/alpha/access-context-manager/help | 3 + .../supported-services/describe | 52 +++ .../supported-services/help | 45 +++ .../supported-services/list | 69 ++++ gcloud/alpha/anthos/config/controller/create | 9 +- gcloud/alpha/anthos/config/controller/delete | 9 +- .../alpha/anthos/config/controller/describe | 9 +- gcloud/alpha/anthos/config/controller/update | 9 +- .../alpha/anthos/config/operations/describe | 9 +- .../workloads/enable-resource-monitoring | 4 +- gcloud/alpha/builds/worker-pools/create | 83 ++-- gcloud/alpha/builds/worker-pools/delete | 9 +- gcloud/alpha/builds/worker-pools/help | 6 +- gcloud/alpha/builds/worker-pools/update | 54 +-- gcloud/alpha/composer/environments/create | 11 +- gcloud/alpha/composer/environments/update | 11 +- gcloud/alpha/compute/copy-files | 10 +- gcloud/alpha/compute/help | 4 +- .../alpha/compute/instance-templates/create | 21 +- .../instance-templates/create-with-container | 14 +- gcloud/alpha/compute/instances/bulk/create | 6 +- gcloud/alpha/compute/instances/create | 31 +- .../compute/instances/create-with-container | 24 +- .../instances/network-interfaces/delete | 65 ++++ .../compute/instances/network-interfaces/help | 3 + gcloud/alpha/compute/instances/update | 6 +- gcloud/alpha/compute/networks/subnets/create | 2 + gcloud/alpha/compute/queued-resources/create | 6 +- .../container/binauthz/attestations/create | 106 ++++-- .../alpha/container/binauthz/attestors/create | 4 +- gcloud/alpha/container/clusters/create | 24 +- gcloud/alpha/container/clusters/create-auto | 41 +- gcloud/alpha/container/clusters/update | 23 +- gcloud/alpha/dataproc/jobs/submit/pyspark | 2 +- gcloud/alpha/dataproc/jobs/submit/spark | 2 +- gcloud/alpha/dataproc/jobs/submit/spark-r | 2 +- .../workflow-templates/add-job/pyspark | 2 +- .../dataproc/workflow-templates/add-job/spark | 2 +- .../workflow-templates/add-job/spark-r | 2 +- gcloud/alpha/datastore/indexes/create | 7 +- .../edge-cloud/container/clusters/create | 3 +- .../edge-cloud/container/clusters/update | 3 +- .../alpha/firestore/backups/schedules/create | 2 +- .../alpha/firestore/backups/schedules/delete | 2 +- .../firestore/backups/schedules/describe | 2 +- gcloud/alpha/firestore/backups/schedules/list | 2 +- .../alpha/firestore/backups/schedules/update | 2 +- gcloud/alpha/firestore/databases/create | 2 +- gcloud/alpha/firestore/databases/delete | 4 +- gcloud/alpha/functions/deploy | 22 +- .../create-cred-config | 2 +- gcloud/alpha/logging/copy | 9 +- gcloud/alpha/logging/operations/list | 18 +- gcloud/alpha/monitoring/uptime/create | 8 +- gcloud/alpha/monitoring/uptime/update | 7 +- gcloud/alpha/run/deploy | 3 +- gcloud/alpha/run/jobs/deploy | 5 +- gcloud/alpha/run/jobs/update | 5 +- gcloud/alpha/run/services/update | 3 +- .../vpc-peerings/get-vpc-service-controls | 4 +- gcloud/alpha/sql/backups/restore | 7 +- gcloud/alpha/sql/instances/create | 7 - gcloud/alpha/sql/instances/patch | 7 - .../storage/buckets/anywhere-caches/create | 66 ++++ .../storage/buckets/anywhere-caches/describe | 42 +++ .../storage/buckets/anywhere-caches/disable | 45 +++ .../storage/buckets/anywhere-caches/help | 45 +++ .../storage/buckets/anywhere-caches}/list | 36 +- .../storage/buckets/anywhere-caches/pause | 39 ++ .../storage/buckets/anywhere-caches/resume | 40 ++ .../storage/buckets/anywhere-caches/update | 57 +++ gcloud/alpha/storage/buckets/help | 3 + gcloud/alpha/telco-automation/help | 4 +- .../telco-automation/operations/describe | 4 +- gcloud/alpha/telco-automation/operations/help | 4 +- gcloud/alpha/telco-automation/operations/wait | 4 +- .../orchestration-cluster/create | 4 +- .../orchestration-cluster/delete | 4 +- .../orchestration-cluster/describe | 4 +- .../orchestration-cluster/help | 4 +- .../orchestration-cluster/list | 4 +- gcloud/anthos/config/controller/create | 9 +- gcloud/anthos/config/controller/delete | 9 +- gcloud/anthos/config/controller/describe | 9 +- gcloud/anthos/config/operations/describe | 9 +- .../workloads/enable-resource-monitoring | 67 ++++ gcloud/assured/workloads/help | 3 + gcloud/beta/access-context-manager/help | 3 + .../supported-services/describe | 50 +++ .../supported-services/help | 43 +++ .../supported-services/list | 67 ++++ .../workloads/enable-resource-monitoring | 6 +- gcloud/beta/composer/environments/create | 11 +- gcloud/beta/composer/environments/update | 11 +- gcloud/beta/compute/copy-files | 10 +- gcloud/beta/compute/disks/create | 3 +- gcloud/beta/compute/help | 4 +- gcloud/beta/compute/images/create | 3 +- gcloud/beta/compute/instance-templates/create | 14 +- .../instance-templates/create-with-container | 14 +- gcloud/beta/compute/instances/bulk/create | 6 +- gcloud/beta/compute/instances/create | 24 +- .../compute/instances/create-with-container | 24 +- gcloud/beta/compute/instances/update | 6 +- .../networks/vpc-access/connectors/create | 8 +- .../beta/compute/target-https-proxies/create | 25 +- .../beta/compute/target-https-proxies/update | 29 ++ .../container/binauthz/attestations/create | 106 ++++-- .../beta/container/binauthz/attestors/create | 4 +- gcloud/beta/container/clusters/create | 24 +- gcloud/beta/container/clusters/create-auto | 41 +- gcloud/beta/container/clusters/update | 23 +- gcloud/beta/dataproc/jobs/submit/pyspark | 2 +- gcloud/beta/dataproc/jobs/submit/spark | 2 +- gcloud/beta/dataproc/jobs/submit/spark-r | 2 +- .../workflow-templates/add-job/pyspark | 2 +- .../dataproc/workflow-templates/add-job/spark | 2 +- .../workflow-templates/add-job/spark-r | 2 +- gcloud/beta/datastore/indexes/create | 12 +- gcloud/beta/firestore/databases/create | 2 +- gcloud/beta/firestore/databases/delete | 6 +- gcloud/beta/firestore/databases/update | 9 +- gcloud/beta/functions/deploy | 21 +- .../create-cred-config | 2 +- gcloud/beta/logging/copy | 9 +- gcloud/beta/logging/operations/list | 18 +- gcloud/beta/privateca/certificates/create | 212 ----------- gcloud/beta/privateca/certificates/describe | 84 ----- gcloud/beta/privateca/certificates/export | 103 ----- gcloud/beta/privateca/certificates/help | 41 -- gcloud/beta/privateca/certificates/list | 114 ------ gcloud/beta/privateca/certificates/revoke | 114 ------ gcloud/beta/privateca/certificates/update | 101 ----- gcloud/beta/privateca/help | 40 -- gcloud/beta/privateca/locations/help | 26 -- .../beta/privateca/reusable-configs/describe | 59 --- gcloud/beta/privateca/reusable-configs/help | 26 -- .../privateca/roots/add-iam-policy-binding | 94 ----- gcloud/beta/privateca/roots/create | 305 --------------- gcloud/beta/privateca/roots/delete | 92 ----- gcloud/beta/privateca/roots/describe | 73 ---- gcloud/beta/privateca/roots/disable | 64 ---- gcloud/beta/privateca/roots/enable | 63 ---- gcloud/beta/privateca/roots/help | 59 --- gcloud/beta/privateca/roots/list | 54 --- .../privateca/roots/remove-iam-policy-binding | 95 ----- gcloud/beta/privateca/roots/restore | 62 --- gcloud/beta/privateca/roots/set-iam-policy | 79 ---- gcloud/beta/privateca/roots/update | 137 ------- gcloud/beta/privateca/subordinates/activate | 68 ---- .../subordinates/add-iam-policy-binding | 95 ----- gcloud/beta/privateca/subordinates/create | 354 ------------------ gcloud/beta/privateca/subordinates/delete | 96 ----- gcloud/beta/privateca/subordinates/describe | 76 ---- gcloud/beta/privateca/subordinates/disable | 66 ---- gcloud/beta/privateca/subordinates/enable | 65 ---- gcloud/beta/privateca/subordinates/get-csr | 68 ---- .../privateca/subordinates/get-iam-policy | 96 ----- gcloud/beta/privateca/subordinates/help | 68 ---- gcloud/beta/privateca/subordinates/list | 54 --- .../subordinates/remove-iam-policy-binding | 96 ----- gcloud/beta/privateca/subordinates/restore | 64 ---- .../privateca/subordinates/set-iam-policy | 79 ---- gcloud/beta/privateca/subordinates/update | 142 ------- gcloud/beta/run/deploy | 60 ++- gcloud/beta/run/jobs/deploy | 50 +++ gcloud/beta/run/jobs/update | 50 +++ gcloud/beta/run/services/update | 60 ++- .../vpc-peerings/get-vpc-service-controls | 6 +- gcloud/beta/sql/backups/restore | 7 +- gcloud/beta/sql/instances/create | 7 - gcloud/beta/sql/instances/patch | 7 - gcloud/builds/worker-pools/create | 6 +- gcloud/builds/worker-pools/help | 2 +- gcloud/composer/environments/create | 11 +- gcloud/composer/environments/update | 11 +- gcloud/compute/copy-files | 4 - gcloud/compute/help | 3 +- gcloud/compute/instance-templates/create | 14 +- .../instance-templates/create-with-container | 14 +- gcloud/compute/instances/bulk/create | 6 +- gcloud/compute/instances/create | 24 +- .../compute/instances/create-with-container | 24 +- gcloud/compute/instances/update | 6 +- .../networks/vpc-access/connectors/create | 8 +- gcloud/container/binauthz/attestations/create | 104 +++-- gcloud/container/binauthz/attestors/create | 4 +- gcloud/container/clusters/create | 11 +- gcloud/container/clusters/create-auto | 18 +- gcloud/container/clusters/update | 9 +- gcloud/dataproc/jobs/submit/pyspark | 2 +- gcloud/dataproc/jobs/submit/spark | 2 +- gcloud/dataproc/jobs/submit/spark-r | 2 +- .../workflow-templates/add-job/pyspark | 2 +- .../dataproc/workflow-templates/add-job/spark | 2 +- .../workflow-templates/add-job/spark-r | 2 +- gcloud/datastore/indexes/create | 12 +- gcloud/edge-cloud/container/clusters/create | 3 +- gcloud/edge-cloud/container/clusters/update | 3 +- gcloud/firestore/databases/create | 19 +- gcloud/firestore/databases/delete | 46 +++ gcloud/firestore/databases/help | 3 + gcloud/firestore/databases/update | 9 +- gcloud/functions/deploy | 3 +- .../create-cred-config | 2 +- gcloud/infra-manager/deployments/apply | 4 +- gcloud/infra-manager/help | 3 + gcloud/infra-manager/previews/create | 239 ++++++++++++ gcloud/infra-manager/previews/delete | 63 ++++ gcloud/infra-manager/previews/describe | 58 +++ gcloud/infra-manager/previews/export | 55 +++ gcloud/infra-manager/previews/help | 31 ++ .../previews}/list | 58 ++- gcloud/logging/copy | 7 +- gcloud/logging/operations/list | 18 +- gcloud/org-policies/delete | 8 +- gcloud/privateca/certificates/create | 6 - gcloud/privateca/certificates/describe | 6 - gcloud/privateca/certificates/export | 6 - gcloud/privateca/certificates/help | 6 - gcloud/privateca/certificates/list | 6 - gcloud/privateca/certificates/revoke | 6 - gcloud/privateca/certificates/update | 6 - gcloud/privateca/help | 6 - gcloud/privateca/locations/help | 6 - gcloud/privateca/locations/list | 6 - gcloud/privateca/roots/create | 6 - gcloud/privateca/roots/delete | 6 - gcloud/privateca/roots/describe | 6 - gcloud/privateca/roots/disable | 6 - gcloud/privateca/roots/enable | 6 - gcloud/privateca/roots/help | 6 - gcloud/privateca/roots/list | 6 - gcloud/privateca/roots/update | 6 - gcloud/privateca/subordinates/activate | 6 - gcloud/privateca/subordinates/create | 6 - gcloud/privateca/subordinates/delete | 6 - gcloud/privateca/subordinates/describe | 6 - gcloud/privateca/subordinates/disable | 6 - gcloud/privateca/subordinates/enable | 6 - gcloud/privateca/subordinates/get-csr | 6 - gcloud/privateca/subordinates/help | 6 - gcloud/privateca/subordinates/list | 6 - gcloud/privateca/subordinates/update | 6 - .../vpc-peerings/get-vpc-service-controls | 69 ++++ gcloud/services/vpc-peerings/help | 3 + gcloud/sql/backups/restore | 6 +- gcloud/sql/instances/create | 7 - gcloud/sql/instances/patch | 7 - gcloud/telco-automation/help | 28 ++ gcloud/telco-automation/operations/describe | 67 ++++ gcloud/telco-automation/operations/help | 29 ++ gcloud/telco-automation/operations/wait | 69 ++++ .../orchestration-cluster/create | 125 +++++++ .../orchestration-cluster/delete | 74 ++++ .../orchestration-cluster/describe | 68 ++++ .../orchestration-cluster/help | 36 ++ .../orchestration-cluster/list} | 69 ++-- gcloud/workstations/clusters/create | 8 +- 262 files changed, 3211 insertions(+), 4501 deletions(-) create mode 100644 gcloud/alpha/access-context-manager/supported-services/describe create mode 100644 gcloud/alpha/access-context-manager/supported-services/help create mode 100644 gcloud/alpha/access-context-manager/supported-services/list create mode 100644 gcloud/alpha/compute/instances/network-interfaces/delete create mode 100644 gcloud/alpha/storage/buckets/anywhere-caches/create create mode 100644 gcloud/alpha/storage/buckets/anywhere-caches/describe create mode 100644 gcloud/alpha/storage/buckets/anywhere-caches/disable create mode 100644 gcloud/alpha/storage/buckets/anywhere-caches/help rename gcloud/{beta/privateca/locations => alpha/storage/buckets/anywhere-caches}/list (66%) create mode 100644 gcloud/alpha/storage/buckets/anywhere-caches/pause create mode 100644 gcloud/alpha/storage/buckets/anywhere-caches/resume create mode 100644 gcloud/alpha/storage/buckets/anywhere-caches/update create mode 100644 gcloud/assured/workloads/enable-resource-monitoring create mode 100644 gcloud/beta/access-context-manager/supported-services/describe create mode 100644 gcloud/beta/access-context-manager/supported-services/help create mode 100644 gcloud/beta/access-context-manager/supported-services/list delete mode 100644 gcloud/beta/privateca/certificates/create delete mode 100644 gcloud/beta/privateca/certificates/describe delete mode 100644 gcloud/beta/privateca/certificates/export delete mode 100644 gcloud/beta/privateca/certificates/help delete mode 100644 gcloud/beta/privateca/certificates/list delete mode 100644 gcloud/beta/privateca/certificates/revoke delete mode 100644 gcloud/beta/privateca/certificates/update delete mode 100644 gcloud/beta/privateca/help delete mode 100644 gcloud/beta/privateca/locations/help delete mode 100644 gcloud/beta/privateca/reusable-configs/describe delete mode 100644 gcloud/beta/privateca/reusable-configs/help delete mode 100644 gcloud/beta/privateca/roots/add-iam-policy-binding delete mode 100644 gcloud/beta/privateca/roots/create delete mode 100644 gcloud/beta/privateca/roots/delete delete mode 100644 gcloud/beta/privateca/roots/describe delete mode 100644 gcloud/beta/privateca/roots/disable delete mode 100644 gcloud/beta/privateca/roots/enable delete mode 100644 gcloud/beta/privateca/roots/help delete mode 100644 gcloud/beta/privateca/roots/list delete mode 100644 gcloud/beta/privateca/roots/remove-iam-policy-binding delete mode 100644 gcloud/beta/privateca/roots/restore delete mode 100644 gcloud/beta/privateca/roots/set-iam-policy delete mode 100644 gcloud/beta/privateca/roots/update delete mode 100644 gcloud/beta/privateca/subordinates/activate delete mode 100644 gcloud/beta/privateca/subordinates/add-iam-policy-binding delete mode 100644 gcloud/beta/privateca/subordinates/create delete mode 100644 gcloud/beta/privateca/subordinates/delete delete mode 100644 gcloud/beta/privateca/subordinates/describe delete mode 100644 gcloud/beta/privateca/subordinates/disable delete mode 100644 gcloud/beta/privateca/subordinates/enable delete mode 100644 gcloud/beta/privateca/subordinates/get-csr delete mode 100644 gcloud/beta/privateca/subordinates/get-iam-policy delete mode 100644 gcloud/beta/privateca/subordinates/help delete mode 100644 gcloud/beta/privateca/subordinates/list delete mode 100644 gcloud/beta/privateca/subordinates/remove-iam-policy-binding delete mode 100644 gcloud/beta/privateca/subordinates/restore delete mode 100644 gcloud/beta/privateca/subordinates/set-iam-policy delete mode 100644 gcloud/beta/privateca/subordinates/update create mode 100644 gcloud/firestore/databases/delete create mode 100644 gcloud/infra-manager/previews/create create mode 100644 gcloud/infra-manager/previews/delete create mode 100644 gcloud/infra-manager/previews/describe create mode 100644 gcloud/infra-manager/previews/export create mode 100644 gcloud/infra-manager/previews/help rename gcloud/{beta/privateca/reusable-configs => infra-manager/previews}/list (53%) create mode 100644 gcloud/services/vpc-peerings/get-vpc-service-controls create mode 100644 gcloud/telco-automation/help create mode 100644 gcloud/telco-automation/operations/describe create mode 100644 gcloud/telco-automation/operations/help create mode 100644 gcloud/telco-automation/operations/wait create mode 100644 gcloud/telco-automation/orchestration-cluster/create create mode 100644 gcloud/telco-automation/orchestration-cluster/delete create mode 100644 gcloud/telco-automation/orchestration-cluster/describe create mode 100644 gcloud/telco-automation/orchestration-cluster/help rename gcloud/{beta/privateca/roots/get-iam-policy => telco-automation/orchestration-cluster/list} (51%) diff --git a/gcloud/_version b/gcloud/_version index ef27dd7c2..7729c7c9c 100644 --- a/gcloud/_version +++ b/gcloud/_version @@ -1,8 +1,8 @@ -Google Cloud SDK 458.0.1 -alpha 2023.12.20 -beta 2023.12.20 +Google Cloud SDK 459.0.0 +alpha 2024.01.06 +beta 2024.01.06 bq 2.0.101 bundled-python3-unix 3.11.6 -core 2023.12.20 +core 2024.01.06 gcloud-crc32c 1.0.0 gsutil 5.27 diff --git a/gcloud/ai/model-monitoring-jobs/create b/gcloud/ai/model-monitoring-jobs/create index f2a18468d..e5adca785 100644 --- a/gcloud/ai/model-monitoring-jobs/create +++ b/gcloud/ai/model-monitoring-jobs/create @@ -10,6 +10,7 @@ SYNOPSIS [--[no-]anomaly-cloud-logging] [--labels=[KEY=VALUE,...]] [--log-ttl=LOG_TTL] [--monitoring-frequency=MONITORING_FREQUENCY; default=24] + [--notification-channels=[NOTIFICATION_CHANNELS,...]] [--predict-instance-schema=PREDICT_INSTANCE_SCHEMA] [--region=REGION] [--sample-predict-request=SAMPLE_PREDICT_REQUEST] [--kms-key=KMS_KEY : --kms-keyring=KMS_KEYRING @@ -119,6 +120,10 @@ OPTIONAL FLAGS --monitoring-frequency=MONITORING_FREQUENCY; default=24 Monitoring frequency, unit is 1 hour. + --notification-channels=[NOTIFICATION_CHANNELS,...] + Comma-separated notification channel list. e.g. + --notification-channels=projects/fake-project/notificationChannels/123,projects/fake-project/notificationChannels/456 + --predict-instance-schema=PREDICT_INSTANCE_SCHEMA YAML schema file uri(Google Cloud Storage) describing the format of a single instance, which are given to format this Endpoint's prediction. diff --git a/gcloud/ai/model-monitoring-jobs/update b/gcloud/ai/model-monitoring-jobs/update index 9fe9c3efb..366242072 100644 --- a/gcloud/ai/model-monitoring-jobs/update +++ b/gcloud/ai/model-monitoring-jobs/update @@ -8,6 +8,7 @@ SYNOPSIS [--[no-]anomaly-cloud-logging] [--display-name=DISPLAY_NAME] [--emails=[EMAILS,...]] [--log-ttl=LOG_TTL] [--monitoring-frequency=MONITORING_FREQUENCY] + [--notification-channels=[NOTIFICATION_CHANNELS,...]] [--prediction-sampling-rate=PREDICTION_SAMPLING_RATE] [--update-labels=[KEY=VALUE,...]] [--clear-labels | --remove-labels=[KEY,...]] @@ -84,6 +85,10 @@ FLAGS --monitoring-frequency=MONITORING_FREQUENCY Monitoring frequency, unit is 1 hour. + --notification-channels=[NOTIFICATION_CHANNELS,...] + Comma-separated notification channel list. e.g. + --notification-channels=projects/fake-project/notificationChannels/123,projects/fake-project/notificationChannels/456 + --prediction-sampling-rate=PREDICTION_SAMPLING_RATE Prediction sampling rate. diff --git a/gcloud/alpha/access-context-manager/help b/gcloud/alpha/access-context-manager/help index 2233b45e0..23dd4e8b9 100644 --- a/gcloud/alpha/access-context-manager/help +++ b/gcloud/alpha/access-context-manager/help @@ -33,6 +33,9 @@ GROUPS policies (ALPHA) Manage Access Context Manager policies. + supported-services + (ALPHA) Retrieve VPC-SC Supported Services. + NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct diff --git a/gcloud/alpha/access-context-manager/supported-services/describe b/gcloud/alpha/access-context-manager/supported-services/describe new file mode 100644 index 000000000..bb71a3060 --- /dev/null +++ b/gcloud/alpha/access-context-manager/supported-services/describe @@ -0,0 +1,52 @@ +NAME + gcloud alpha access-context-manager supported-services describe - get a VPC + Service Controls Supported Service] + +SYNOPSIS + gcloud alpha access-context-manager supported-services describe + SERVICE_NAME [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Get service information allowed in an access policy object. + +EXAMPLES + To get VPC Service Controls support information for + bigquery.googleapis.com, run: + + $ gcloud alpha access-context-manager supported-services describe \ + bigquery.googleapis.com + +POSITIONAL ARGUMENTS + Supported service resource - VPC Service Controls supported service. This + represents a Cloud resource. + + This must be specified. + + SERVICE_NAME + ID of the supported-service or fully qualified identifier for the + supported-service. + + To set the service_name attribute: + ▸ provide the argument service_name on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the accesscontextmanager/v1alpha API. The full + documentation for this API can be found at: + https://cloud.google.com/access-context-manager/docs/reference/rest/ + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta access-context-manager supported-services describe + diff --git a/gcloud/alpha/access-context-manager/supported-services/help b/gcloud/alpha/access-context-manager/supported-services/help new file mode 100644 index 000000000..88d3b2ed8 --- /dev/null +++ b/gcloud/alpha/access-context-manager/supported-services/help @@ -0,0 +1,45 @@ +NAME + gcloud alpha access-context-manager supported-services - retrieve VPC-SC + Supported Services + +SYNOPSIS + gcloud alpha access-context-manager supported-services COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) The gcloud alpha access-context-manager supported-services command + group lets you list VPC Service Controls supported services and its + properties. + +EXAMPLES + To see all VPC-SC supportedservices: + + $ gcloud alpha access-context-manager supported-services list + + To see support information about VPC-SC supported service: + + $ gcloud alpha access-context-manager supported-services describe \ + SERVICE_NAME + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + describe + (ALPHA) Get a VPC Service Controls Supported Service]. + + list + (ALPHA) Lists all VPC Service Controls supported services. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta access-context-manager supported-services + diff --git a/gcloud/alpha/access-context-manager/supported-services/list b/gcloud/alpha/access-context-manager/supported-services/list new file mode 100644 index 000000000..72244106f --- /dev/null +++ b/gcloud/alpha/access-context-manager/supported-services/list @@ -0,0 +1,69 @@ +NAME + gcloud alpha access-context-manager supported-services list - lists all VPC + Service Controls supported services + +SYNOPSIS + gcloud alpha access-context-manager supported-services list + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Lists the services that VPC Service Controls supports. The services + that are in this list either fully support VPC Service Controls or the + integration of this service with VPC Service Controls is in Preview stage + (https://cloud.google.com/products#product-launch-stages). Services that + aren't in this list don't support VPC Service Controls and aren't + guaranteed to function properly in a VPC Service Controls environment. + +EXAMPLES + To list VPC Service Controls supported services, run: + + $ gcloud alpha access-context-manager supported-services list + + This command prints out a list of all supported services in a tabular form: + + NAME TITLE SUPPORT_STAGE AVAILABLE_ON_RESTRICTED_VIP KNOWN_LIMITATIONS + vpcsc_supported_service VPC-SC Supported API GA True False + +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 access-context-manager supported-services list + diff --git a/gcloud/alpha/anthos/config/controller/create b/gcloud/alpha/anthos/config/controller/create index 8e862964e..f25f34a60 100644 --- a/gcloud/alpha/anthos/config/controller/create +++ b/gcloud/alpha/anthos/config/controller/create @@ -48,10 +48,11 @@ POSITIONAL ARGUMENTS --location=LOCATION The name of the Config Controller instance location. Currently, only - us-central1, us-east1, northamerica-northeast1, - northamerica-northeast2, europe-north1, europe-west1, europe-west3, - australia-southeast1, australia-southeast2, asia-northeast1, and - asia-northeast2 are supported. + us-central1, us-east1, us-east4, us-east5, us-west2, + northamerica-northeast1, northamerica-northeast2, europe-north1, + europe-west1, europe-west3, europe-west6, australia-southeast1, + australia-southeast2, asia-northeast1, asia-northeast2 and + asia-southeast1 are supported. To set the location attribute: ▸ provide the argument name on the command line with a fully diff --git a/gcloud/alpha/anthos/config/controller/delete b/gcloud/alpha/anthos/config/controller/delete index a284802af..bc96b757d 100644 --- a/gcloud/alpha/anthos/config/controller/delete +++ b/gcloud/alpha/anthos/config/controller/delete @@ -40,10 +40,11 @@ POSITIONAL ARGUMENTS --location=LOCATION The name of the Anthos Config Controller instance location. - Currently, only us-central1, us-east1, northamerica-northeast1, - northamerica-northeast2, europe-north1, europe-west1, europe-west3, - australia-southeast1, australia-southeast2, asia-northeast1 and - asia-northeast2 are supported. + Currently, only us-central1, us-east1, us-east4, us-east5, us-west2, + northamerica-northeast1, northamerica-northeast2, europe-north1, + europe-west1, europe-west3, europe-west6, australia-southeast1, + australia-southeast2, asia-northeast1, asia-northeast2 and + asia-southeast1 are supported. To set the location attribute: ▸ provide the argument name on the command line with a fully diff --git a/gcloud/alpha/anthos/config/controller/describe b/gcloud/alpha/anthos/config/controller/describe index 357ad10d7..a5c81614c 100644 --- a/gcloud/alpha/anthos/config/controller/describe +++ b/gcloud/alpha/anthos/config/controller/describe @@ -41,10 +41,11 @@ POSITIONAL ARGUMENTS --location=LOCATION The name of the Anthos Config Controller instance location. - Currently, only us-central1, us-east1, northamerica-northeast1, - northamerica-northeast2, europe-north1, europe-west1, europe-west3, - australia-southeast1, australia-southeast2, asia-northeast1 and - asia-northeast2 are supported. + Currently, only us-central1, us-east1, us-east4, us-east5, us-west2, + northamerica-northeast1, northamerica-northeast2, europe-north1, + europe-west1, europe-west3, europe-west6, australia-southeast1, + australia-southeast2, asia-northeast1, asia-northeast2 and + asia-southeast1 are supported. To set the location attribute: ▸ provide the argument name on the command line with a fully diff --git a/gcloud/alpha/anthos/config/controller/update b/gcloud/alpha/anthos/config/controller/update index b699ddd63..fab9a53c3 100644 --- a/gcloud/alpha/anthos/config/controller/update +++ b/gcloud/alpha/anthos/config/controller/update @@ -42,10 +42,11 @@ POSITIONAL ARGUMENTS --location=LOCATION The name of the Config Controller instance location. Currently, only - us-central1, us-east1, northamerica-northeast1, - northamerica-northeast2, europe-north1, europe-west1, europe-west3, - australia-southeast1, australia-southeast2, asia-northeast1, and - asia-northeast2 are supported. + us-central1, us-east1, us-east4, us-east5, us-west2, + northamerica-northeast1, northamerica-northeast2, europe-north1, + europe-west1, europe-west3, europe-west6, australia-southeast1, + australia-southeast2, asia-northeast1, asia-northeast2 and + asia-southeast1 are supported. To set the location attribute: ▸ provide the argument name on the command line with a fully diff --git a/gcloud/alpha/anthos/config/operations/describe b/gcloud/alpha/anthos/config/operations/describe index b4927ca4f..5c22e8543 100644 --- a/gcloud/alpha/anthos/config/operations/describe +++ b/gcloud/alpha/anthos/config/operations/describe @@ -41,10 +41,11 @@ POSITIONAL ARGUMENTS --location=LOCATION The name of the Anthos Config Controller instance location. - Currently, only us-central1, us-east1, northamerica-northeast1, - northamerica-northeast2, europe-north1, europe-west1, europe-west3, - australia-southeast1, australia-southeast2, asia-northeast1 and - asia-northeast2 are supported. + Currently, only us-central1, us-east1, us-east4, us-east5, us-west2, + northamerica-northeast1, northamerica-northeast2, europe-north1, + europe-west1, europe-west3, europe-west6, australia-southeast1, + australia-southeast2, asia-northeast1, asia-northeast2 and + asia-southeast1 are supported. To set the location attribute: ▸ provide the argument operation on the command line with a fully diff --git a/gcloud/alpha/assured/workloads/enable-resource-monitoring b/gcloud/alpha/assured/workloads/enable-resource-monitoring index b29e0ba96..33142c43d 100644 --- a/gcloud/alpha/assured/workloads/enable-resource-monitoring +++ b/gcloud/alpha/assured/workloads/enable-resource-monitoring @@ -62,7 +62,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud assured workloads enable-resource-monitoring $ gcloud beta assured workloads enable-resource-monitoring diff --git a/gcloud/alpha/builds/worker-pools/create b/gcloud/alpha/builds/worker-pools/create index aacd3631c..7865d03a0 100644 --- a/gcloud/alpha/builds/worker-pools/create +++ b/gcloud/alpha/builds/worker-pools/create @@ -1,6 +1,6 @@ NAME - gcloud alpha builds worker-pools create - create a private or hybrid pool - for use by Cloud Build + gcloud alpha builds worker-pools create - create a private pool for use by + Cloud Build SYNOPSIS gcloud alpha builds worker-pools create WORKER_POOL --region=REGION @@ -10,7 +10,7 @@ SYNOPSIS --worker-machine-type=WORKER_MACHINE_TYPE] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Create a private or hybrid pool for use by Cloud Build. + (ALPHA) Create a private pool for use by Cloud Build. EXAMPLES ▪ Private pools @@ -30,21 +30,6 @@ EXAMPLES --peered-network-ip-range=192.168.0.0/28 \ --worker-machine-type=e2-standard-2 --worker-disk-size=64GB - ▪ Hybrid pools - - To create a hybrid pool named hwp1 out of Hub member named foo in region - us-west4, run: - - $ gcloud alpha builds worker-pools create hwp1 --region=us-west4 \ - --membership=projects/123/locations/global/memberships/foo - - To create a hybrid pool in project p1 in region us-west4 that requires 60 - GB of disk size per build by default, run: - - $ gcloud alpha builds worker-pools create hwp1 --region=us-west4 \ - --membership=projects/123/locations/global/memberships/foo \ - --default-build-disk-size=60GB - POSITIONAL ARGUMENTS WORKER_POOL Unique identifier for the worker pool to create. This value should be @@ -66,52 +51,46 @@ OPTIONAL FLAGS https://cloud.google.com/build/docs/private-pools/worker-pool-config-file-schema - Hybrid pool options: + Command-line flags to configure the private pool: - https://cloud.google.com/build/docs/hybrid/hybrid-pool-config-file-schema + --peered-network=PEERED_NETWORK + Existing network to which workers are peered. The network is + specified in resource URL format + projects/{network_project}/global/networks/{network_name}. - At most one of these can be specified: + If not specified, the workers are not peered to any network. - Command-line flags to configure the private pool: + --peered-network-ip-range=PEERED_NETWORK_IP_RANGE + An IP range for your peered network. Specify the IP range using + Classless Inter-Domain Routing (CIDR) notation with a slash and the + subnet prefix size, such as /29. - --peered-network=PEERED_NETWORK - Existing network to which workers are peered. The network is - specified in resource URL format - projects/{network_project}/global/networks/{network_name}. + Your subnet prefix size must be between 1 and 29. Optional: you can + specify an IP address before the subnet prefix value - for example + 192.168.0.0/24. - If not specified, the workers are not peered to any network. + If no IP address is specified, your VPC automatically determines + the starting IP for the range. If no IP range is specified, Cloud + Build uses /24 as the default network IP range. - --peered-network-ip-range=PEERED_NETWORK_IP_RANGE - An IP range for your peered network. Specify the IP range using - Classless Inter-Domain Routing (CIDR) notation with a slash and - the subnet prefix size, such as /29. + --no-public-egress + If set, workers in the worker pool are created without an external + IP address. - Your subnet prefix size must be between 1 and 29. Optional: you - can specify an IP address before the subnet prefix value - for - example 192.168.0.0/24. + If the worker pool is within a VPC Service Control perimeter, use + this flag. - If no IP address is specified, your VPC automatically determines - the starting IP for the range. If no IP range is specified, Cloud - Build uses /24 as the default network IP range. + Configuration to be used for creating workers in the worker pool: - --no-public-egress - If set, workers in the worker pool are created without an - external IP address. + --worker-disk-size=WORKER_DISK_SIZE + Size of the disk attached to the worker. - If the worker pool is within a VPC Service Control perimeter, use - this flag. + If not given, Cloud Build will use a standard disk size. - Configuration to be used for creating workers in the worker pool: + --worker-machine-type=WORKER_MACHINE_TYPE + Compute Engine machine type for a worker pool. - --worker-disk-size=WORKER_DISK_SIZE - Size of the disk attached to the worker. - - If not given, Cloud Build will use a standard disk size. - - --worker-machine-type=WORKER_MACHINE_TYPE - Compute Engine machine type for a worker pool. - - If unspecified, Cloud Build uses a standard machine type. + If unspecified, Cloud Build uses a standard machine type. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/builds/worker-pools/delete b/gcloud/alpha/builds/worker-pools/delete index 676eaeb49..ec71e544b 100644 --- a/gcloud/alpha/builds/worker-pools/delete +++ b/gcloud/alpha/builds/worker-pools/delete @@ -1,17 +1,16 @@ NAME - gcloud alpha builds worker-pools delete - delete a private or hybrid worker - pool from Google Cloud Build + gcloud alpha builds worker-pools delete - delete a private worker pool from + Google Cloud Build SYNOPSIS gcloud alpha builds worker-pools delete WORKER_POOL --region=REGION [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Delete a private or hybrid worker pool from Google Cloud Build. + (ALPHA) Delete a private worker pool from Google Cloud Build. EXAMPLES - To delete a private or hybrid worker pool named wp1 in region us-central1, - run: + To delete a private worker pool named wp1 in region us-central1, run: $ gcloud alpha builds worker-pools delete wp1 --region=us-central1 diff --git a/gcloud/alpha/builds/worker-pools/help b/gcloud/alpha/builds/worker-pools/help index d1212fa0b..e797ff8f3 100644 --- a/gcloud/alpha/builds/worker-pools/help +++ b/gcloud/alpha/builds/worker-pools/help @@ -17,10 +17,10 @@ COMMANDS COMMAND is one of the following: create - (ALPHA) Create a private or hybrid pool for use by Cloud Build. + (ALPHA) Create a private pool for use by Cloud Build. delete - (ALPHA) Delete a private or hybrid worker pool from Google Cloud Build. + (ALPHA) Delete a private worker pool from Google Cloud Build. describe (ALPHA) Describe a private or hybrid worker pool used by Cloud Build. @@ -30,7 +30,7 @@ COMMANDS project. update - (ALPHA) Update a private or hybrid pool used by Cloud Build. + (ALPHA) Update a private pool used by Cloud Build. NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/builds/worker-pools/update b/gcloud/alpha/builds/worker-pools/update index 78fe5d125..804a54c88 100644 --- a/gcloud/alpha/builds/worker-pools/update +++ b/gcloud/alpha/builds/worker-pools/update @@ -1,6 +1,6 @@ NAME - gcloud alpha builds worker-pools update - update a private or hybrid pool - used by Cloud Build + gcloud alpha builds worker-pools update - update a private pool used by + Cloud Build SYNOPSIS gcloud alpha builds worker-pools update WORKER_POOL --region=REGION @@ -9,7 +9,7 @@ SYNOPSIS --worker-machine-type=WORKER_MACHINE_TYPE) [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Update a private or hybrid pool used by Cloud Build. + (ALPHA) Update a private pool used by Cloud Build. EXAMPLES ▪ Private pools @@ -20,14 +20,6 @@ EXAMPLES --region=us-central1 --worker-machine-type=e2-standard-2 \ --worker-disk-size=64GB - ▪ Hybrid pools - - To change the default build disk size and default build vcpu count of a - hybrid pool named hwp1, run: - - $ gcloud alpha builds worker-pools update hwp1 --region=us-west4 \ - --default-build-disk-size=100GB --default-build-vcpu-count=3.5 - POSITIONAL ARGUMENTS WORKER_POOL Unique identifier for the worker pool to update. This value should be @@ -48,38 +40,32 @@ REQUIRED FLAGS https://cloud.google.com/build/docs/private-pools/worker-pool-config-file-schema - Hybrid pool options: + Command-line flags to configure the private pool: - https://cloud.google.com/build/docs/hybrid/hybrid-pool-config-file-schema + At most one of these can be specified: - At most one of these can be specified: + --public-egress + If set, workers in the worker pool are created with an external + IP address. - Command-line flags to configure the private pool: + --no-public-egress + If set, workers in the worker pool are created without an + external IP address. - At most one of these can be specified: + If the worker pool is within a VPC Service Control perimeter, use + this flag. - --public-egress - If set, workers in the worker pool are created with an external - IP address. + Configuration to be used for creating workers in the worker pool: - --no-public-egress - If set, workers in the worker pool are created without an - external IP address. + --worker-disk-size=WORKER_DISK_SIZE + Size of the disk attached to the worker. - If the worker pool is within a VPC Service Control perimeter, - use this flag. + If not given, Cloud Build will use a standard disk size. - Configuration to be used for creating workers in the worker pool: + --worker-machine-type=WORKER_MACHINE_TYPE + Compute Engine machine type for a worker pool. - --worker-disk-size=WORKER_DISK_SIZE - Size of the disk attached to the worker. - - If not given, Cloud Build will use a standard disk size. - - --worker-machine-type=WORKER_MACHINE_TYPE - Compute Engine machine type for a worker pool. - - If unspecified, Cloud Build uses a standard machine type. + If unspecified, Cloud Build uses a standard machine type. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/composer/environments/create b/gcloud/alpha/composer/environments/create index 50e697271..c1d459b52 100644 --- a/gcloud/alpha/composer/environments/create +++ b/gcloud/alpha/composer/environments/create @@ -7,7 +7,8 @@ SYNOPSIS (ENVIRONMENT : --location=LOCATION) [--airflow-configs=[KEY=VALUE,...]] [--async] [--cloud-sql-machine-type=CLOUD_SQL_MACHINE_TYPE] [--cloud-sql-preferred-zone=CLOUD_SQL_PREFERRED_ZONE] - [--disk-size=DISK_SIZE] [--enable-high-resilience] + [--disable-logs-in-cloud-logging-only] [--disk-size=DISK_SIZE] + [--enable-high-resilience] [--enable-logs-in-cloud-logging-only] [--env-variables=[NAME=VALUE,...]] [--environment-size=ENVIRONMENT_SIZE] [--labels=[KEY=VALUE,...]] [--machine-type=MACHINE_TYPE] [--node-count=NODE_COUNT] @@ -127,6 +128,10 @@ FLAGS --cloud-sql-preferred-zone=CLOUD_SQL_PREFERRED_ZONE Select cloud sql preferred zone, supported for Composer 2 Environments. + --disable-logs-in-cloud-logging-only + Disable logs in cloud logging only, supported for Composer 2 + Environments. + --disk-size=DISK_SIZE The disk size for each VM node in the environment. The minimum size is 20GB, and the maximum is 64TB. Specified value must be an integer @@ -136,6 +141,10 @@ FLAGS --enable-high-resilience Enable high resilience, supported for Composer 2 Environments. + --enable-logs-in-cloud-logging-only + Enable logs in cloud logging only, supported for Composer 2 + Environments. + --env-variables=[NAME=VALUE,...] A comma-delimited list of environment variable NAME=VALUE pairs to provide to the Airflow scheduler, worker, and webserver processes. NAME diff --git a/gcloud/alpha/composer/environments/update b/gcloud/alpha/composer/environments/update index 5294279a2..71db57847 100644 --- a/gcloud/alpha/composer/environments/update +++ b/gcloud/alpha/composer/environments/update @@ -6,7 +6,8 @@ SYNOPSIS gcloud alpha composer environments update (ENVIRONMENT : --location=LOCATION) (--cloud-sql-machine-type=CLOUD_SQL_MACHINE_TYPE - | --disable-high-resilience | --enable-high-resilience + | --disable-high-resilience | --disable-logs-in-cloud-logging-only + | --enable-high-resilience | --enable-logs-in-cloud-logging-only | --environment-size=ENVIRONMENT_SIZE | --node-count=NODE_COUNT | --web-server-machine-type=WEB_SERVER_MACHINE_TYPE | --airflow-version=AIRFLOW_VERSION | --image-version=IMAGE_VERSION @@ -103,9 +104,17 @@ REQUIRED FLAGS --disable-high-resilience Disable high resilience, supported for Composer 2 Environments. + --disable-logs-in-cloud-logging-only + Disable logs in cloud logging only, supported for Composer 2 + Environments. + --enable-high-resilience Enable high resilience, supported for Composer 2 Environments. + --enable-logs-in-cloud-logging-only + Enable logs in cloud logging only, supported for Composer 2 + Environments. + --environment-size=ENVIRONMENT_SIZE Size of the environment. Unspecified means that the default option will be chosen. ENVIRONMENT_SIZE must be one of: large, medium, diff --git a/gcloud/alpha/compute/copy-files b/gcloud/alpha/compute/copy-files index 8bb60943f..47fac1860 100644 --- a/gcloud/alpha/compute/copy-files +++ b/gcloud/alpha/compute/copy-files @@ -11,13 +11,9 @@ SYNOPSIS | --ssh-key-expire-after=SSH_KEY_EXPIRE_AFTER] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) (DEPRECATED) gcloud compute copy-files is deprecated. Please use - gcloud compute scp instead. Note that gcloud compute scp does not have - recursive copy on by default. To turn on recursion, use the --recurse flag. - - gcloud alpha compute copy-files copies files between a virtual machine - instance and your local machine using the scp command. This command does - not work for Windows VMs. + (ALPHA) gcloud alpha compute copy-files copies files between a virtual + machine instance and your local machine using the scp command. This command + does not work for Windows VMs. To denote a remote file, prefix the file name with the virtual machine instance name (e.g., example-instance:~/FILE). To denote a local file, do diff --git a/gcloud/alpha/compute/help b/gcloud/alpha/compute/help index 35fb4d422..3d79c5db5 100644 --- a/gcloud/alpha/compute/help +++ b/gcloud/alpha/compute/help @@ -234,8 +234,8 @@ COMMANDS (ALPHA) Connect to the serial port of an instance. copy-files - (ALPHA) (DEPRECATED) Copy files to and from Google Compute Engine - virtual machines via scp. + (ALPHA) Copy files to and from Google Compute Engine virtual machines + via scp. reset-windows-password (ALPHA) Reset and return a password for a Windows machine instance. diff --git a/gcloud/alpha/compute/instance-templates/create b/gcloud/alpha/compute/instance-templates/create index da5f7cc9a..dddccbd17 100644 --- a/gcloud/alpha/compute/instance-templates/create +++ b/gcloud/alpha/compute/instance-templates/create @@ -16,7 +16,7 @@ SYNOPSIS [--[no-]enable-nested-virtualization] [--[no-]enable-uefi-networking] [--external-ipv6-address=EXTERNAL_IPV6_ADDRESS] [--external-ipv6-prefix-length=EXTERNAL_IPV6_PREFIX_LENGTH] - [--[no-]graceful-shutdown] + [--graceful-shutdown] [--graceful-shutdown-max-duration=GRACEFUL_SHUTDOWN_MAX_DURATION] [--host-error-timeout-seconds=HOST_ERROR_TIMEOUT_SECONDS] [--instance-template-region=INSTANCE_TEMPLATE_REGION] @@ -396,9 +396,8 @@ FLAGS be used together with --external-ipv6-address. Only the /96 IP address range is supported, and the default value is 96. - --[no-]graceful-shutdown - If set to true, enables graceful shutdown for the instance. Use - --graceful-shutdown to enable and --no-graceful-shutdown to disable. + --graceful-shutdown + Enables graceful shutdown for the instance. --graceful-shutdown-max-duration=GRACEFUL_SHUTDOWN_MAX_DURATION Specifies time needed to gracefully shutdown the instance. After that @@ -693,13 +692,13 @@ FLAGS --aliases="10.128.1.0/24;range1:/32" - Each IP alias range consists of a range name and a CIDR netmask - (e.g. `/24`) separated by a colon or just the netmask. - The range name is the name of the range within the network - interface's subnet from which to allocate an IP alias range. If - unspecified, it defaults to the primary IP range of the subnet. - The IP allocator will pick an available range with the specified - netmask and allocate it to this network interface. + Each IP alias range consists of a range name and a CIDR netmask + (e.g. /24) separated by a colon or just the netmask. The range name + is the name of the range within the network interface's subnet from + which to allocate an IP alias range. If unspecified, it defaults to + the primary IP range of the subnet. The IP allocator will pick an + available range with the specified netmask and allocate it to this + network interface. network-attachment Specifies the network attachment that this interface should connect diff --git a/gcloud/alpha/compute/instance-templates/create-with-container b/gcloud/alpha/compute/instance-templates/create-with-container index bfd56470d..4a709bab4 100644 --- a/gcloud/alpha/compute/instance-templates/create-with-container +++ b/gcloud/alpha/compute/instance-templates/create-with-container @@ -599,13 +599,13 @@ FLAGS --aliases="10.128.1.0/24;range1:/32" - Each IP alias range consists of a range name and a CIDR netmask - (e.g. `/24`) separated by a colon or just the netmask. - The range name is the name of the range within the network - interface's subnet from which to allocate an IP alias range. If - unspecified, it defaults to the primary IP range of the subnet. - The IP allocator will pick an available range with the specified - netmask and allocate it to this network interface. + Each IP alias range consists of a range name and a CIDR netmask + (e.g. /24) separated by a colon or just the netmask. The range name + is the name of the range within the network interface's subnet from + which to allocate an IP alias range. If unspecified, it defaults to + the primary IP range of the subnet. The IP allocator will pick an + available range with the specified netmask and allocate it to this + network interface. --network-tier=NETWORK_TIER Specifies the network tier that will be used to configure the instance. diff --git a/gcloud/alpha/compute/instances/bulk/create b/gcloud/alpha/compute/instances/bulk/create index 04746f6f0..0dc181ef0 100644 --- a/gcloud/alpha/compute/instances/bulk/create +++ b/gcloud/alpha/compute/instances/bulk/create @@ -637,9 +637,9 @@ OPTIONAL FLAGS queue-count Specifies the networking queue count for this interface. Both Rx and Tx queues will be set to this number. If it's not specified, a - default queue count will be assigned. For Virtio-net, each - interface will get min(floor(#vCPU / #vNIC), 32) queues. For gVNIC, - each interface will get min(floor(#vCPU / #vNIC / 2), 16) qeueus. + default queue count will be assigned. See + https://cloud.google.com/compute/docs/network-bandwidth#rx-tx for + more details. --network-performance-configs=[PROPERTY=VALUE,...] Configures network performance settings for the instance. If this flag diff --git a/gcloud/alpha/compute/instances/create b/gcloud/alpha/compute/instances/create index 10f672f09..15f90f600 100644 --- a/gcloud/alpha/compute/instances/create +++ b/gcloud/alpha/compute/instances/create @@ -20,7 +20,7 @@ SYNOPSIS [--[no-]enable-uefi-networking] [--erase-windows-vss-signature] [--external-ipv6-address=EXTERNAL_IPV6_ADDRESS] [--external-ipv6-prefix-length=EXTERNAL_IPV6_PREFIX_LENGTH] - [--[no-]graceful-shutdown] + [--graceful-shutdown] [--graceful-shutdown-max-duration=GRACEFUL_SHUTDOWN_MAX_DURATION] [--host-error-timeout-seconds=HOST_ERROR_TIMEOUT_SECONDS] [--hostname=HOSTNAME] @@ -514,9 +514,8 @@ FLAGS be used together with --external-ipv6-address. Only the /96 IP address range is supported, and the default value is 96. - --[no-]graceful-shutdown - If set to true, enables graceful shutdown for the instance. Use - --graceful-shutdown to enable and --no-graceful-shutdown to disable. + --graceful-shutdown + Enables graceful shutdown for the instance. --graceful-shutdown-max-duration=GRACEFUL_SHUTDOWN_MAX_DURATION Specifies time needed to gracefully shutdown the instance. After that @@ -1309,18 +1308,18 @@ FLAGS --aliases="10.128.1.0/24;range1:/32" - Each IP alias range consists of a range name and an IP range - separated by a colon, or just the IP range. - The range name is the name of the range within the network - interface's subnet from which to allocate an IP alias range. If - unspecified, it defaults to the primary IP range of the subnet. - The IP range can be a CIDR range (e.g. `192.168.100.0/24`), a single - IP address (e.g. `192.168.100.1`), or a netmask in CIDR format (e.g. - `/24`). If the IP range is specified by CIDR range or single IP - address, it must belong to the CIDR range specified by the range - name on the subnet. If the IP range is specified by netmask, the - IP allocator will pick an available range with the specified netmask - and allocate it to this network interface. + Each IP alias range consists of a range name and an IP range + separated by a colon, or just the IP range. The range name is the + name of the range within the network interface's subnet from + which to allocate an IP alias range. If unspecified, it defaults + to the primary IP range of the subnet. The IP range can be a CIDR + range (e.g. 192.168.100.0/24), a single IP address (e.g. + 192.168.100.1), or a netmask in CIDR format (e.g. /24). If the IP + range is specified by CIDR range or single IP address, it must + belong to the CIDR range specified by the range name on the + subnet. If the IP range is specified by netmask, the IP allocator + will pick an available range with the specified netmask and + allocate it to this network interface. network-attachment Specifies the network attachment that this interface should diff --git a/gcloud/alpha/compute/instances/create-with-container b/gcloud/alpha/compute/instances/create-with-container index 54f6d5029..d1b146e61 100644 --- a/gcloud/alpha/compute/instances/create-with-container +++ b/gcloud/alpha/compute/instances/create-with-container @@ -644,18 +644,18 @@ FLAGS --aliases="10.128.1.0/24;range1:/32" - Each IP alias range consists of a range name and an IP range - separated by a colon, or just the IP range. - The range name is the name of the range within the network - interface's subnet from which to allocate an IP alias range. If - unspecified, it defaults to the primary IP range of the subnet. - The IP range can be a CIDR range (e.g. `192.168.100.0/24`), a single - IP address (e.g. `192.168.100.1`), or a netmask in CIDR format (e.g. - `/24`). If the IP range is specified by CIDR range or single IP - address, it must belong to the CIDR range specified by the range - name on the subnet. If the IP range is specified by netmask, the - IP allocator will pick an available range with the specified netmask - and allocate it to this network interface. + Each IP alias range consists of a range name and an IP range + separated by a colon, or just the IP range. The range name is the + name of the range within the network interface's subnet from which + to allocate an IP alias range. If unspecified, it defaults to the + primary IP range of the subnet. The IP range can be a CIDR range + (e.g. 192.168.100.0/24), a single IP address (e.g. 192.168.100.1), + or a netmask in CIDR format (e.g. /24). If the IP range is + specified by CIDR range or single IP address, it must belong to the + CIDR range specified by the range name on the subnet. If the IP + range is specified by netmask, the IP allocator will pick an + available range with the specified netmask and allocate it to this + network interface. --network-performance-configs=[PROPERTY=VALUE,...] Configures network performance settings for the instance. If this flag diff --git a/gcloud/alpha/compute/instances/network-interfaces/delete b/gcloud/alpha/compute/instances/network-interfaces/delete new file mode 100644 index 000000000..3ca5333b9 --- /dev/null +++ b/gcloud/alpha/compute/instances/network-interfaces/delete @@ -0,0 +1,65 @@ +NAME + gcloud alpha compute instances network-interfaces delete - delete a Compute + Engine virtual machine network interface + +SYNOPSIS + gcloud alpha compute instances network-interfaces delete INSTANCE_NAME + --network-interface=NETWORK_INTERFACE [--zone=ZONE] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) gcloud alpha compute instances network-interfaces delete deletes + network interface of a Compute Engine virtual machine. For example: + + $ gcloud alpha compute instances network-interfaces delete \ + instance-name --network-interface nic1.2 + +POSITIONAL ARGUMENTS + INSTANCE_NAME + Name of the instance to operate on. For details on valid instance + names, refer to the criteria documented under the field 'name' at: + https://cloud.google.com/compute/docs/reference/rest/v1/instances + +REQUIRED FLAGS + --network-interface=NETWORK_INTERFACE + The name of the network interface to delete, e.g. nic1.2 + +OPTIONAL FLAGS + --zone=ZONE + Zone of the instance to operate on. If not specified, you might be + prompted to select a zone (interactive mode only). gcloud attempts to + identify the appropriate zone by searching for resources in your + currently active project. If the zone cannot be determined, gcloud + prompts you for a selection with all available Google Cloud Platform + zones. + + To avoid prompting when this flag is omitted, the user can set the + compute/zone property: + + $ gcloud config set compute/zone ZONE + + A list of zones can be fetched by running: + + $ gcloud compute zones list + + To unset the property, run: + + $ gcloud config unset compute/zone + + Alternatively, the zone can be stored in the environment variable + CLOUDSDK_COMPUTE_ZONE. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/compute/instances/network-interfaces/help b/gcloud/alpha/compute/instances/network-interfaces/help index 81ba3ac73..06284ca2f 100644 --- a/gcloud/alpha/compute/instances/network-interfaces/help +++ b/gcloud/alpha/compute/instances/network-interfaces/help @@ -24,6 +24,9 @@ GCLOUD WIDE FLAGS COMMANDS COMMAND is one of the following: + delete + (ALPHA) Delete a Compute Engine virtual machine network interface. + get-effective-firewalls (ALPHA) Get the effective firewalls for a Compute Engine virtual machine network interface. diff --git a/gcloud/alpha/compute/instances/update b/gcloud/alpha/compute/instances/update index ff113f279..eb5509107 100644 --- a/gcloud/alpha/compute/instances/update +++ b/gcloud/alpha/compute/instances/update @@ -30,15 +30,15 @@ EXAMPLES --zone=us-central1-a --update-labels=k0=value1,k1=value2 \ --remove-labels=k3 - Labels can be used to identify the disk. To list disks with the 'k1:value2' - label, run: + Labels can be used to identify the instance. To list instances with the + 'k1:value2' label, run: $ gcloud alpha compute instances list --filter='labels.k1:value2' To list only the labels when describing a resource, use --format to filter the result: - $ gcloud alpha compute instances describe example-disk \ + $ gcloud alpha compute instances describe example-instance \ --format="default(labels)" POSITIONAL ARGUMENTS diff --git a/gcloud/alpha/compute/networks/subnets/create b/gcloud/alpha/compute/networks/subnets/create index 884cd3beb..5694622da 100644 --- a/gcloud/alpha/compute/networks/subnets/create +++ b/gcloud/alpha/compute/networks/subnets/create @@ -227,6 +227,8 @@ OPTIONAL FLAGS New VMs in this subnet can have both IPv4 and IPv6 addresses IPV4_ONLY New VMs in this subnet will only be assigned IPv4 addresses + IPV6_ONLY + New VMs in this subnet will only be assigned IPv6 addresses L2 networking specifications. diff --git a/gcloud/alpha/compute/queued-resources/create b/gcloud/alpha/compute/queued-resources/create index 151c74f03..c97d22e2c 100644 --- a/gcloud/alpha/compute/queued-resources/create +++ b/gcloud/alpha/compute/queued-resources/create @@ -606,9 +606,9 @@ OPTIONAL FLAGS queue-count Specifies the networking queue count for this interface. Both Rx and Tx queues will be set to this number. If it's not specified, a - default queue count will be assigned. For Virtio-net, each - interface will get min(floor(#vCPU / #vNIC), 32) queues. For gVNIC, - each interface will get min(floor(#vCPU / #vNIC / 2), 16) qeueus. + default queue count will be assigned. See + https://cloud.google.com/compute/docs/network-bandwidth#rx-tx for + more details. --network-performance-configs=[PROPERTY=VALUE,...] Configures network performance settings for the instance. If this flag diff --git a/gcloud/alpha/container/binauthz/attestations/create b/gcloud/alpha/container/binauthz/attestations/create index 059e8d588..d422b0a36 100644 --- a/gcloud/alpha/container/binauthz/attestations/create +++ b/gcloud/alpha/container/binauthz/attestations/create @@ -5,9 +5,10 @@ NAME SYNOPSIS gcloud alpha container binauthz attestations create --artifact-url=ARTIFACT_URL --public-key-id=PUBLIC_KEY_ID - --signature-file=SIGNATURE_FILE - (--attestor=ATTESTOR : --attestor-project=ATTESTOR_PROJECT) - [--payload-file=PAYLOAD_FILE] [--validate] [GCLOUD_WIDE_FLAG ...] + --signature-file=SIGNATURE_FILE [--payload-file=PAYLOAD_FILE] + [[--note=NOTE : --note-project=NOTE_PROJECT] + | --validate [--attestor=ATTESTOR + : --attestor-project=ATTESTOR_PROJECT]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) This command creates a Binary Authorization attestation for your @@ -26,6 +27,16 @@ EXAMPLES --signature-file=signed_artifact_attestation.pgp.sig \ --public-key-id=AAAA0000000000000000FFFFFFFFFFFFFFFFFFFF + To create an attestation in the project "my_proj" in note + "projects/foo/notes/bar", run: + + $ gcloud alpha container binauthz attestations create \ + --project=my_proj \ + --artifact-url='gcr.io/example-project/example-image@sha256:abcd\ + ' --note=projects/foo/notes/bar \ + --signature-file=signed_artifact_attestation.pgp.sig \ + --public-key-id=AAAA0000000000000000FFFFFFFFFFFFFFFFFFFF + REQUIRED FLAGS --artifact-url=ARTIFACT_URL Container URL. May be in the gcr.io/repository/image format, or may @@ -47,35 +58,6 @@ REQUIRED FLAGS Path to file containing the signature to store, or - to read signature from stdin. - Attestor resource - The Attestor whose Container Analysis Note will be - used to host the created attestation. In order to successfully attach the - attestation, the active gcloud account (core/account) must be able to read - this attestor and must have the containeranalysis.notes.attachOccurrence - permission for the Attestor's underlying Note resource (usually via the - containeranalysis.notes.attacher role). The arguments in this group can be - used to specify the attributes of this resource. - - This must be specified. - - --attestor=ATTESTOR - ID of the attestor or fully qualified identifier for the attestor. - - To set the name attribute: - ▸ provide the argument --attestor on the command line. - - This flag argument must be specified if any of the other arguments in - this group are specified. - - --attestor-project=ATTESTOR_PROJECT - Project ID of the Google Cloud project for the attestor. - - To set the project attribute: - ▸ provide the argument --attestor on the command line with a fully - specified name; - ▸ provide the argument --attestor-project on the command line; - ▸ provide the argument --project on the command line; - ▸ set the property core/project. - OPTIONAL FLAGS --payload-file=PAYLOAD_FILE Path to file containing the payload over which the signature was @@ -89,9 +71,63 @@ OPTIONAL FLAGS formatting, you must explicitly provide the payload content via this flag. - --validate - Whether to validate that the Attestation can be verified by the - provided Attestor. + At most one of these can be specified: + + Note resource - The Container Analysis Note which will be used to host + the created attestation. In order to successfully attach the + attestation, the active gcloud account (core/account) must have the + containeranalysis.notes.attachOccurrence permission for the Note + (usually via the containeranalysis.notes.attacher role). The arguments + in this group can be used to specify the attributes of this resource. + + --note=NOTE + ID of the note or fully qualified identifier for the note. + + To set the note attribute: + ▫ provide the argument --note on the command line. + + This flag argument must be specified if any of the other arguments + in this group are specified. + + --note-project=NOTE_PROJECT + The Container Analysis project for the note. + + To set the project attribute: + ▫ provide the argument --note on the command line with a fully + specified name; + ▫ provide the argument --note-project on the command line. + + --validate + Whether to validate that the Attestation can be verified by the + provided Attestor. + + Attestor resource - The Attestor whose Container Analysis Note will be + used to host the created attestation. In order to successfully attach + the attestation, the active gcloud account (core/account) must be able + to read this attestor and must have the + containeranalysis.notes.attachOccurrence permission for the Attestor's + underlying Note resource (usually via the + containeranalysis.notes.attacher role). The arguments in this group can + be used to specify the attributes of this resource. + + --attestor=ATTESTOR + ID of the attestor or fully qualified identifier for the attestor. + + To set the name attribute: + ▫ provide the argument --attestor on the command line. + + This flag argument must be specified if any of the other arguments + in this group are specified. + + --attestor-project=ATTESTOR_PROJECT + Project ID of the Google Cloud project for the attestor. + + To set the project attribute: + ▫ provide the argument --attestor on the command line with a + fully specified name; + ▫ provide the argument --attestor-project on the command line; + ▫ provide the argument --project on the command line; + ▫ set the property core/project. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/container/binauthz/attestors/create b/gcloud/alpha/container/binauthz/attestors/create index 0d1dc88bc..6ade9d1a3 100644 --- a/gcloud/alpha/container/binauthz/attestors/create +++ b/gcloud/alpha/container/binauthz/attestors/create @@ -34,8 +34,8 @@ POSITIONAL ARGUMENTS ▸ provide the argument ATTESTOR on the command line. REQUIRED FLAGS - Note resource - The Container Analysis ATTESTATION_AUTHORITY Note to which - the created attestor will be bound. + Note resource - The Container Analysis Note to which the created attestor + will be bound. For the attestor to be able to access and use the Note, the Note must exist and the active gcloud account (core/account) must have the diff --git a/gcloud/alpha/container/clusters/create b/gcloud/alpha/container/clusters/create index 9d558e317..6c03980ba 100644 --- a/gcloud/alpha/container/clusters/create +++ b/gcloud/alpha/container/clusters/create @@ -37,8 +37,9 @@ SYNOPSIS [--enable-logging-monitoring-system-only] [--enable-managed-prometheus] [--enable-master-global-access] [--enable-multi-networking] [--enable-network-policy] [--enable-pod-security-policy] - [--enable-service-externalips] [--enable-shielded-nodes] - [--enable-stackdriver-kubernetes] [--enable-vertical-pod-autoscaling] + [--enable-secret-manager] [--enable-service-externalips] + [--enable-shielded-nodes] [--enable-stackdriver-kubernetes] + [--enable-vertical-pod-autoscaling] [--fleet-project=PROJECT_ID_OR_NUMBER] [--gateway-api=GATEWAY_API] [--identity-provider=IDENTITY_PROVIDER] [--image-type=IMAGE_TYPE] [--in-transit-encryption=IN_TRANSIT_ENCRYPTION] @@ -596,6 +597,14 @@ FLAGS API objects. For more information, see https://cloud.google.com/kubernetes-engine/docs/how-to/pod-security-policies. + --enable-secret-manager + Enables the Secret Manager CSI driver provider component. See + https://secrets-store-csi-driver.sigs.k8s.io/introduction + https://github.com/GoogleCloudPlatform/secrets-store-csi-driver-provider-gcp + + To disable in an existing cluster, explicitly set flag to + --no-enable-secret-manager + --enable-service-externalips Enables use of services with externalIPs field. @@ -759,7 +768,7 @@ FLAGS The maximum number of nodes to allocate per default initial node pool. Kubernetes Engine will automatically create enough nodes pools such that each node pool contains less than --max-nodes-per-pool nodes. - Defaults to 1000 nodes, but can be set as low as 100 nodes per pool on + Defaults to 2000 nodes, but can be set as low as 100 nodes per pool on initial create. --max-pods-per-node=MAX_PODS_PER_NODE @@ -1399,8 +1408,8 @@ FLAGS At most one of these can be specified: --dataplane-v2-observability-mode=DATAPLANE_V2_OBSERVABILITY_MODE - Select Advanced Datapath Observability mode for the cluster. Defaults - to DISABLED. + (DEPRECATED) Select Advanced Datapath Observability mode for the + cluster. Defaults to DISABLED. Advanced Datapath Observability allows for a real-time view into pod-to-pod traffic within your cluster. @@ -1416,6 +1425,11 @@ FLAGS $ gcloud alpha container clusters create \ --dataplane-v2-observability-mode=EXTERNAL_LB + The --dataplane-v2-observability-mode flag is deprecated and will be + removed in an upcoming release. Please use + --enable-dataplane-v2-flow-observability or + --disable-dataplane-v2-flow-observability. + DATAPLANE_V2_OBSERVABILITY_MODE must be one of: DISABLED diff --git a/gcloud/alpha/container/clusters/create-auto b/gcloud/alpha/container/clusters/create-auto index 33a4c69e3..629820aa0 100644 --- a/gcloud/alpha/container/clusters/create-auto +++ b/gcloud/alpha/container/clusters/create-auto @@ -15,13 +15,14 @@ SYNOPSIS [--enable-backup-restore] [--enable-fleet] [--enable-google-cloud-access] [--enable-kubernetes-unstable-apis=API,[API,...]] - [--enable-master-global-access] [--fleet-project=PROJECT_ID_OR_NUMBER] - [--labels=[KEY=VALUE,...]] [--logging=[COMPONENT,...]] - [--monitoring=[COMPONENT,...]] [--network=NETWORK] - [--private-endpoint-subnetwork=NAME] [--release-channel=CHANNEL] - [--security-group=SECURITY_GROUP] [--security-posture=SECURITY_POSTURE] - [--services-ipv4-cidr=CIDR] [--services-secondary-range-name=NAME] - [--subnetwork=SUBNETWORK] [--workload-policies=WORKLOAD_POLICIES] + [--enable-master-global-access] [--enable-secret-manager] + [--fleet-project=PROJECT_ID_OR_NUMBER] [--labels=[KEY=VALUE,...]] + [--logging=[COMPONENT,...]] [--monitoring=[COMPONENT,...]] + [--network=NETWORK] [--private-endpoint-subnetwork=NAME] + [--release-channel=CHANNEL] [--security-group=SECURITY_GROUP] + [--security-posture=SECURITY_POSTURE] [--services-ipv4-cidr=CIDR] + [--services-secondary-range-name=NAME] [--subnetwork=SUBNETWORK] + [--workload-policies=WORKLOAD_POLICIES] [--workload-vulnerability-scanning=WORKLOAD_VULNERABILITY_SCANNING] [--binauthz-evaluation-mode=BINAUTHZ_EVALUATION_MODE --binauthz-policy-bindings=[name=BINAUTHZ_POLICY]] @@ -211,6 +212,14 @@ FLAGS endpoint from any Google Cloud region or on-premises environment regardless of the private cluster's region. + --enable-secret-manager + Enables the Secret Manager CSI driver provider component. See + https://secrets-store-csi-driver.sigs.k8s.io/introduction + https://github.com/GoogleCloudPlatform/secrets-store-csi-driver-provider-gcp + + To disable in an existing cluster, explicitly set flag to + --no-enable-secret-manager + --fleet-project=PROJECT_ID_OR_NUMBER Sets fleet host project for the cluster. If specified, the current cluster will be registered as a fleet membership under the fleet host @@ -230,17 +239,22 @@ FLAGS --logging=[COMPONENT,...] Set the components that have logging enabled. Valid component values - are: SYSTEM, WORKLOAD, API_SERVER, CONTROLLER_MANAGER, SCHEDULER, NONE + are: SYSTEM, WORKLOAD, API_SERVER, CONTROLLER_MANAGER, SCHEDULER + + The default is SYSTEM,WORKLOAD. If this flag is set, then SYSTEM must + be included. For more information, see https://cloud.google.com/stackdriver/docs/solutions/gke/installing#available-logs Examples: + $ gcloud alpha container clusters create-auto --logging=SYSTEM $ gcloud alpha container clusters create-auto \ --logging=SYSTEM,WORKLOAD $ gcloud alpha container clusters create-auto \ - --logging=SYSTEM,API_SERVER,WORKLOAD + --logging=SYSTEM,WORKLOAD,API_SERVER,CONTROLLER_MANAGER,\ + SCHEDULER --monitoring=[COMPONENT,...] Set the components that have monitoring enabled. Valid component values @@ -391,8 +405,8 @@ FLAGS At most one of these can be specified: --dataplane-v2-observability-mode=DATAPLANE_V2_OBSERVABILITY_MODE - Select Advanced Datapath Observability mode for the cluster. Defaults - to DISABLED. + (DEPRECATED) Select Advanced Datapath Observability mode for the + cluster. Defaults to DISABLED. Advanced Datapath Observability allows for a real-time view into pod-to-pod traffic within your cluster. @@ -408,6 +422,11 @@ FLAGS $ gcloud alpha container clusters create-auto \ --dataplane-v2-observability-mode=EXTERNAL_LB + The --dataplane-v2-observability-mode flag is deprecated and will be + removed in an upcoming release. Please use + --enable-dataplane-v2-flow-observability or + --disable-dataplane-v2-flow-observability. + DATAPLANE_V2_OBSERVABILITY_MODE must be one of: DISABLED diff --git a/gcloud/alpha/container/clusters/update b/gcloud/alpha/container/clusters/update index 3cc43c6a5..4e7624075 100644 --- a/gcloud/alpha/container/clusters/update +++ b/gcloud/alpha/container/clusters/update @@ -20,9 +20,9 @@ SYNOPSIS | --enable-logging-monitoring-system-only | --enable-master-authorized-networks | --enable-master-global-access | --enable-network-policy | --enable-pod-security-policy - | --enable-private-endpoint | --enable-service-externalips - | --enable-shielded-nodes | --enable-stackdriver-kubernetes - | --enable-vertical-pod-autoscaling + | --enable-private-endpoint | --enable-secret-manager + | --enable-service-externalips | --enable-shielded-nodes + | --enable-stackdriver-kubernetes | --enable-vertical-pod-autoscaling | --fleet-project=PROJECT_ID_OR_NUMBER | --gateway-api=GATEWAY_API | --generate-password | --identity-provider=IDENTITY_PROVIDER | --in-transit-encryption=IN_TRANSIT_ENCRYPTION @@ -370,6 +370,14 @@ REQUIRED FLAGS Enables cluster's control plane to be accessible using private IP address only. + --enable-secret-manager + Enables the Secret Manager CSI driver provider component. See + https://secrets-store-csi-driver.sigs.k8s.io/introduction + https://github.com/GoogleCloudPlatform/secrets-store-csi-driver-provider-gcp + + To disable in an existing cluster, explicitly set flag to + --no-enable-secret-manager + --enable-service-externalips Enables use of services with externalIPs field. @@ -952,8 +960,8 @@ REQUIRED FLAGS At most one of these can be specified: --dataplane-v2-observability-mode=DATAPLANE_V2_OBSERVABILITY_MODE - Select Advanced Datapath Observability mode for the cluster. - Defaults to DISABLED. + (DEPRECATED) Select Advanced Datapath Observability mode for the + cluster. Defaults to DISABLED. Advanced Datapath Observability allows for a real-time view into pod-to-pod traffic within your cluster. @@ -969,6 +977,11 @@ REQUIRED FLAGS $ gcloud alpha container clusters update \ --dataplane-v2-observability-mode=EXTERNAL_LB + The --dataplane-v2-observability-mode flag is deprecated and will + be removed in an upcoming release. Please use + --enable-dataplane-v2-flow-observability or + --disable-dataplane-v2-flow-observability. + DATAPLANE_V2_OBSERVABILITY_MODE must be one of: DISABLED diff --git a/gcloud/alpha/dataproc/jobs/submit/pyspark b/gcloud/alpha/dataproc/jobs/submit/pyspark index 215a211b6..2c8ae15ae 100644 --- a/gcloud/alpha/dataproc/jobs/submit/pyspark +++ b/gcloud/alpha/dataproc/jobs/submit/pyspark @@ -88,7 +88,7 @@ OPTIONAL FLAGS --files=[FILE,...] Comma separated list of files to be placed in the working directory of - both the app master and executors. + both the app driver and executors. --jars=[JAR,...] Comma separated list of jar files to be provided to the executor and diff --git a/gcloud/alpha/dataproc/jobs/submit/spark b/gcloud/alpha/dataproc/jobs/submit/spark index 2ae9392d1..c64baa0fe 100644 --- a/gcloud/alpha/dataproc/jobs/submit/spark +++ b/gcloud/alpha/dataproc/jobs/submit/spark @@ -99,7 +99,7 @@ OPTIONAL FLAGS --files=[FILE,...] Comma separated list of files to be placed in the working directory of - both the app master and executors. + both the app driver and executors. --jars=[JAR,...] Comma separated list of jar files to be provided to the executor and diff --git a/gcloud/alpha/dataproc/jobs/submit/spark-r b/gcloud/alpha/dataproc/jobs/submit/spark-r index bc9264906..d7bc3b76f 100644 --- a/gcloud/alpha/dataproc/jobs/submit/spark-r +++ b/gcloud/alpha/dataproc/jobs/submit/spark-r @@ -86,7 +86,7 @@ OPTIONAL FLAGS --files=[FILE,...] Comma separated list of files to be placed in the working directory of - both the app master and executors. + both the app driver and executors. --labels=[KEY=VALUE,...] List of label KEY=VALUE pairs to add. diff --git a/gcloud/alpha/dataproc/workflow-templates/add-job/pyspark b/gcloud/alpha/dataproc/workflow-templates/add-job/pyspark index 405f0701e..a016562fb 100644 --- a/gcloud/alpha/dataproc/workflow-templates/add-job/pyspark +++ b/gcloud/alpha/dataproc/workflow-templates/add-job/pyspark @@ -85,7 +85,7 @@ OPTIONAL FLAGS --files=[FILE,...] Comma separated list of files to be placed in the working directory of - both the app master and executors. + both the app driver and executors. --jars=[JAR,...] Comma separated list of jar files to be provided to the executor and diff --git a/gcloud/alpha/dataproc/workflow-templates/add-job/spark b/gcloud/alpha/dataproc/workflow-templates/add-job/spark index 99875ab95..2847dc4fc 100644 --- a/gcloud/alpha/dataproc/workflow-templates/add-job/spark +++ b/gcloud/alpha/dataproc/workflow-templates/add-job/spark @@ -81,7 +81,7 @@ OPTIONAL FLAGS --files=[FILE,...] Comma separated list of files to be placed in the working directory of - both the app master and executors. + both the app driver and executors. --jars=[JAR,...] Comma separated list of jar files to be provided to the executor and diff --git a/gcloud/alpha/dataproc/workflow-templates/add-job/spark-r b/gcloud/alpha/dataproc/workflow-templates/add-job/spark-r index 1535ab614..98462b991 100644 --- a/gcloud/alpha/dataproc/workflow-templates/add-job/spark-r +++ b/gcloud/alpha/dataproc/workflow-templates/add-job/spark-r @@ -85,7 +85,7 @@ OPTIONAL FLAGS --files=[FILE,...] Comma separated list of files to be placed in the working directory of - both the app master and executors. + both the app driver and executors. --labels=[KEY=VALUE,...] List of label KEY=VALUE pairs to add. diff --git a/gcloud/alpha/datastore/indexes/create b/gcloud/alpha/datastore/indexes/create index 16f841eb0..fac8f0fbe 100644 --- a/gcloud/alpha/datastore/indexes/create +++ b/gcloud/alpha/datastore/indexes/create @@ -28,7 +28,12 @@ POSITIONAL ARGUMENTS FLAGS --database=DATABASE - The database to operate on. + The database to operate on. If not specified, the CLI refers the + (default) database by default. + + For example, to operate on database testdb: + + $ gcloud alpha datastore indexes create --database='testdb' GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/edge-cloud/container/clusters/create b/gcloud/alpha/edge-cloud/container/clusters/create index a5faa17a7..be7dfb1ff 100644 --- a/gcloud/alpha/edge-cloud/container/clusters/create +++ b/gcloud/alpha/edge-cloud/container/clusters/create @@ -164,7 +164,8 @@ FLAGS --maintenance-window-recurrence=MAINTENANCE_WINDOW_RECURRENCE An RFC 5545 (https://tools.ietf.org/html/rfc5545#section-3.8.5.3) recurrence rule for how the cluster maintenance window recurs. They go - on for the span of time between the start and the end time. + on for the span of time between the start and the end time. E.g. + FREQ=WEEKLY;BYDAY=SU. --maintenance-window-start=MAINTENANCE_WINDOW_START Start time of the recurring cluster maintenance window in the RFC 3339 diff --git a/gcloud/alpha/edge-cloud/container/clusters/update b/gcloud/alpha/edge-cloud/container/clusters/update index dcb8456f0..e02626c89 100644 --- a/gcloud/alpha/edge-cloud/container/clusters/update +++ b/gcloud/alpha/edge-cloud/container/clusters/update @@ -75,7 +75,8 @@ FLAGS --maintenance-window-recurrence=MAINTENANCE_WINDOW_RECURRENCE An RFC 5545 (https://tools.ietf.org/html/rfc5545#section-3.8.5.3) recurrence rule for how the cluster maintenance window recurs. They - go on for the span of time between the start and the end time. + go on for the span of time between the start and the end time. E.g. + FREQ=WEEKLY;BYDAY=SU. --maintenance-window-start=MAINTENANCE_WINDOW_START Start time of the recurring cluster maintenance window in the RFC diff --git a/gcloud/alpha/firestore/backups/schedules/create b/gcloud/alpha/firestore/backups/schedules/create index a0e624f51..1dad049eb 100644 --- a/gcloud/alpha/firestore/backups/schedules/create +++ b/gcloud/alpha/firestore/backups/schedules/create @@ -24,7 +24,7 @@ EXAMPLES REQUIRED FLAGS --database=DATABASE - The database to operate on. The default value is (default). + The database to operate on. For example, to operate on database foo: diff --git a/gcloud/alpha/firestore/backups/schedules/delete b/gcloud/alpha/firestore/backups/schedules/delete index c1f441a0c..52f9abfad 100644 --- a/gcloud/alpha/firestore/backups/schedules/delete +++ b/gcloud/alpha/firestore/backups/schedules/delete @@ -26,7 +26,7 @@ REQUIRED FLAGS --backup-schedule='091a49a0-223f-4c98-8c69-a284abbdb26b' --database=DATABASE - The database to operate on. The default value is (default). + The database to operate on. For example, to operate on database foo: diff --git a/gcloud/alpha/firestore/backups/schedules/describe b/gcloud/alpha/firestore/backups/schedules/describe index 8c2be5b59..b243762cc 100644 --- a/gcloud/alpha/firestore/backups/schedules/describe +++ b/gcloud/alpha/firestore/backups/schedules/describe @@ -26,7 +26,7 @@ REQUIRED FLAGS --backup-schedule='091a49a0-223f-4c98-8c69-a284abbdb26b' --database=DATABASE - The database to operate on. The default value is (default). + The database to operate on. For example, to operate on database foo: diff --git a/gcloud/alpha/firestore/backups/schedules/list b/gcloud/alpha/firestore/backups/schedules/list index 53aef3360..aa27fbb39 100644 --- a/gcloud/alpha/firestore/backups/schedules/list +++ b/gcloud/alpha/firestore/backups/schedules/list @@ -14,7 +14,7 @@ EXAMPLES REQUIRED FLAGS --database=DATABASE - The database to operate on. The default value is (default). + The database to operate on. For example, to operate on database foo: diff --git a/gcloud/alpha/firestore/backups/schedules/update b/gcloud/alpha/firestore/backups/schedules/update index e6acbfad3..043910d8a 100644 --- a/gcloud/alpha/firestore/backups/schedules/update +++ b/gcloud/alpha/firestore/backups/schedules/update @@ -27,7 +27,7 @@ REQUIRED FLAGS --backup-schedule='091a49a0-223f-4c98-8c69-a284abbdb26b' --database=DATABASE - The database to operate on. The default value is (default). + The database to operate on. For example, to operate on database foo: diff --git a/gcloud/alpha/firestore/databases/create b/gcloud/alpha/firestore/databases/create index 982aec463..8caceaafd 100644 --- a/gcloud/alpha/firestore/databases/create +++ b/gcloud/alpha/firestore/databases/create @@ -18,7 +18,7 @@ EXAMPLES $ gcloud alpha firestore databases create --location=us-east1 \ --type=datastore-mode - To create a Datastore Mode database in us-east1 with a database ID foo. + To create a Datastore Mode database in us-east1 with a databaseId foo. $ gcloud alpha firestore databases create --database=foo \ --location=us-east1 --type=datastore-mode diff --git a/gcloud/alpha/firestore/databases/delete b/gcloud/alpha/firestore/databases/delete index fd6685427..3d7ab57b0 100644 --- a/gcloud/alpha/firestore/databases/delete +++ b/gcloud/alpha/firestore/databases/delete @@ -41,7 +41,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud firestore databases delete $ gcloud beta firestore databases delete diff --git a/gcloud/alpha/functions/deploy b/gcloud/alpha/functions/deploy index eca2a4e64..b11e42a43 100644 --- a/gcloud/alpha/functions/deploy +++ b/gcloud/alpha/functions/deploy @@ -3,10 +3,11 @@ NAME SYNOPSIS gcloud alpha functions deploy (NAME : --region=REGION) - [--[no-]allow-unauthenticated] [--buildpack-stack=BUILDPACK_STACK] - [--concurrency=CONCURRENCY] [--docker-registry=DOCKER_REGISTRY] - [--egress-settings=EGRESS_SETTINGS] [--entry-point=ENTRY_POINT] - [--gen2] [--ignore-file=IGNORE_FILE] + [--[no-]allow-unauthenticated] + [--build-service-account=BUILD_SERVICE_ACCOUNT] + [--buildpack-stack=BUILDPACK_STACK] [--concurrency=CONCURRENCY] + [--docker-registry=DOCKER_REGISTRY] [--egress-settings=EGRESS_SETTINGS] + [--entry-point=ENTRY_POINT] [--gen2] [--ignore-file=IGNORE_FILE] [--ingress-settings=INGRESS_SETTINGS] [--retry] [--run-service-account=RUN_SERVICE_ACCOUNT] [--runtime=RUNTIME] [--runtime-update-policy=RUNTIME_UPDATE_POLICY] @@ -103,6 +104,16 @@ FLAGS without checking authentication. Use --allow-unauthenticated to enable and --no-allow-unauthenticated to disable. + --build-service-account=BUILD_SERVICE_ACCOUNT + IAM service account whose credentials will be used for the build step. + Must be of the format + projects/${PROJECT_ID}/serviceAccounts/${ACCOUNT_EMAIL_ADDRESS}. + + If not provided, the function will use the project's default service + account for Cloud Build. + + Only applicable when the --gen2 flag is provided. + --buildpack-stack=BUILDPACK_STACK Specifies one of the Google provided buildpack stacks. @@ -543,7 +554,8 @@ FLAGS To set the region attribute: ▸ provide the argument --vpc-connector on the command line with a fully specified name; - ▸ provide the argument --region on the command line. + ▸ provide the argument --region on the command line; + ▸ set the property functions/region. --vpc-connector=VPC_CONNECTOR ID of the connector or fully qualified identifier for the diff --git a/gcloud/alpha/iam/workload-identity-pools/create-cred-config b/gcloud/alpha/iam/workload-identity-pools/create-cred-config index edde593a5..ea795e7b2 100644 --- a/gcloud/alpha/iam/workload-identity-pools/create-cred-config +++ b/gcloud/alpha/iam/workload-identity-pools/create-cred-config @@ -75,7 +75,7 @@ EXAMPLES POSITIONAL ARGUMENTS AUDIENCE - The workload identity pool provider resource ID. + The workload identity pool provider fully qualified identifier. REQUIRED FLAGS --output-file=OUTPUT_FILE diff --git a/gcloud/alpha/logging/copy b/gcloud/alpha/logging/copy index 4d1665042..e2738b1a1 100644 --- a/gcloud/alpha/logging/copy +++ b/gcloud/alpha/logging/copy @@ -15,14 +15,13 @@ DESCRIPTION EXAMPLES To start a copy log entries operation, run: - $ gcloud alpha logging copy \ - "BUCKET_ID DESTINATION --location=LOCATION" + $ gcloud alpha logging copy BUCKET_ID DESTINATION --location=LOCATION To copy log entries in a specific time window, run: - $ gcloud alpha logging copy \ - 'BUCKET_ID DESTINATION --location=LOCATION - --log-filter=timestamp<="2021-05-31T23:59:59Z" AND + $ gcloud alpha logging copy BUCKET_ID DESTINATION \ + --location=LOCATION \ + --log-filter='timestamp<="2021-05-31T23:59:59Z" AND timestamp>="2021-05-31T00:00:00Z"' POSITIONAL ARGUMENTS diff --git a/gcloud/alpha/logging/operations/list b/gcloud/alpha/logging/operations/list index 6f5099cb1..c19e77c8c 100644 --- a/gcloud/alpha/logging/operations/list +++ b/gcloud/alpha/logging/operations/list @@ -24,32 +24,32 @@ EXAMPLES To list CopyLogEntries operations, run: $ gcloud alpha logging operations list --location=LOCATION \ - --operation-filter=request_type=CopyLogEntries + --operation-filter='request_type=CopyLogEntries' To list CopyLogEntries operations that started after a specified time, run: $ gcloud alpha logging operations list --location=LOCATION \ - --operation-filter=request_type=CopyLogEntries AND \ - operation_start_time>TIMESTAMP + --operation-filter='request_type=CopyLogEntries AND + operation_start_time>="2023-11-20T00:00:00Z"' To list CopyLogEntries operations that finished before a specified time, run: $ gcloud alpha logging operations list --location=LOCATION \ - --operation-filter=request_type=CopyLogEntries AND \ - operation_finish_timeTIMESTAMP + --operation-filter='request_type=CopyLogEntries AND + operation_start_time>="2023-11-20T00:00:00Z"' To list CopyLogEntries operations that finished before a specified time, run: $ gcloud beta logging operations list --location=LOCATION \ - --operation-filter=request_type=CopyLogEntries AND \ - operation_finish_time ./frontend-server-tls.crt - -POSITIONAL ARGUMENTS - CERTIFICATE resource - The certificate for which to obtain metadata. The - arguments in this group can be used to specify the attributes of this - resource. (NOTE) Some attributes are not given arguments in this group but - can be set in other ways. - - To set the project attribute: - ◆ provide the argument certificate on the command line with a fully - specified name; - ◆ set the property core/project; - ◆ provide the argument --project on the command line. - - This must be specified. - - CERTIFICATE - ID of the CERTIFICATE or fully qualified identifier for the - CERTIFICATE. - - To set the certificate attribute: - ▸ provide the argument certificate on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --issuer=ISSUER - The ID of the issuing certificate authority. - - To set the issuer attribute: - ▸ provide the argument certificate on the command line with a fully - specified name; - ▸ provide the argument --issuer on the command line. - - --issuer-location=ISSUER_LOCATION - The location of the CERTIFICATE. - - To set the issuer-location attribute: - ▸ provide the argument certificate on the command line with a fully - specified name; - ▸ provide the argument --issuer-location on the command line; - ▸ set the property privateca/location. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -API REFERENCE - This command uses the privateca/v1beta1 API. The full documentation for - this API can be found at: https://cloud.google.com/ - -NOTES - This command is currently in beta and might change without notice. This - variant is also available: - - $ gcloud privateca certificates describe - diff --git a/gcloud/beta/privateca/certificates/export b/gcloud/beta/privateca/certificates/export deleted file mode 100644 index 451ddbd7f..000000000 --- a/gcloud/beta/privateca/certificates/export +++ /dev/null @@ -1,103 +0,0 @@ -NAME - gcloud beta privateca certificates export - export a pem-encoded - certificate to a file - -SYNOPSIS - gcloud beta privateca certificates export - (CERTIFICATE : --issuer=ISSUER --issuer-location=ISSUER_LOCATION) - --output-file=OUTPUT_FILE [--include-chain] [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (BETA) Export a pem-encoded certificate to a file. - -EXAMPLES - To export a single pem-encoded certificate to a file, run the following: - - $ gcloud beta privateca certificates export my-cert --issuer=my-ca \ - --issuer-location=us-west1 --output-file=cert.pem - - To export a pem-encoded certificate along with its issuing chain in the - same file, run the following: - - $ gcloud beta privateca certificates export my-cert --issuer=my-ca \ - --issuer-location=us-west1 --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: - - $ gcloud config set privateca/location us-west1 - - # The following is equivalent to the first example above. - $ gcloud beta privateca certificates export my-cert --issuer=my-ca \ - --output-file=cert.pem - - # The following is equivalent to the second example above. - $ gcloud beta privateca certificates export my-cert --issuer=my-ca \ - --include-chain --output-file=chain.pem - -POSITIONAL ARGUMENTS - CERTIFICATE resource - The certificate to export. The arguments in this - group can be used to specify the attributes of this resource. (NOTE) Some - attributes are not given arguments in this group but can be set in other - ways. - - To set the project attribute: - ◆ provide the argument CERTIFICATE on the command line with a fully - specified name; - ◆ provide the argument --project on the command line; - ◆ set the property core/project. - - This must be specified. - - CERTIFICATE - ID of the CERTIFICATE or fully qualified identifier for the - CERTIFICATE. - - To set the certificate attribute: - ▸ provide the argument CERTIFICATE on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --issuer=ISSUER - The issuing certificate authority of the CERTIFICATE. - - To set the issuer attribute: - ▸ provide the argument CERTIFICATE on the command line with a fully - specified name; - ▸ provide the argument --issuer on the command line. - - --issuer-location=ISSUER_LOCATION - The location of the CERTIFICATE. - - To set the issuer-location attribute: - ▸ provide the argument CERTIFICATE on the command line with a fully - specified name; - ▸ provide the argument --issuer-location on the command line; - ▸ set the property privateca/location. - -REQUIRED FLAGS - --output-file=OUTPUT_FILE - The path where the resulting PEM-encoded certificate will be written. - -OPTIONAL FLAGS - --include-chain - Whether to include the certificate's issuer chain in the exported file. - If this is set, the resulting file will contain the pem-encoded - certificate and its issuing chain, ordered from leaf to root. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -NOTES - This command is currently in beta and might change without notice. This - variant is also available: - - $ gcloud privateca certificates export - diff --git a/gcloud/beta/privateca/certificates/help b/gcloud/beta/privateca/certificates/help deleted file mode 100644 index 3d1c6a703..000000000 --- a/gcloud/beta/privateca/certificates/help +++ /dev/null @@ -1,41 +0,0 @@ -NAME - gcloud beta privateca certificates - manage certificates - -SYNOPSIS - gcloud beta privateca certificates COMMAND [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (BETA) Manage certificates. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --help. - - Run $ gcloud help for details. - -COMMANDS - COMMAND is one of the following: - - create - (BETA) Create a new certificate. - - describe - (BETA) Get metadata for a certificate. - - export - (BETA) Export a pem-encoded certificate to a file. - - list - (BETA) List certificates within a project. - - revoke - (BETA) Revoke a certificate. - - update - (BETA) Update an existing certificate. - -NOTES - This command is currently in beta and might change without notice. This - variant is also available: - - $ gcloud privateca certificates - diff --git a/gcloud/beta/privateca/certificates/list b/gcloud/beta/privateca/certificates/list deleted file mode 100644 index 2a79d2ec4..000000000 --- a/gcloud/beta/privateca/certificates/list +++ /dev/null @@ -1,114 +0,0 @@ -NAME - gcloud beta privateca certificates list - list certificates within a - project - -SYNOPSIS - gcloud beta privateca certificates list - [--issuer=ISSUER --location=LOCATION] [--filter=EXPRESSION] - [--limit=LIMIT] [--page-size=PAGE_SIZE; default=100] - [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (BETA) List certificates within a project. - -EXAMPLES - To list all Certificates issued by a given Certificate Authority, run: - - $ gcloud beta privateca certificates list --issuer=my-ca \ - --location=us-west1 - - To list all Certificates issued by all Certificate Authorities in a - location, run: - - $ gcloud beta privateca certificates list --location=us-west1 - - You can omit the --location flag in both of the above examples if you've - already set the privateca/location property. For example: - - $ gcloud config set privateca/location us-west1 - - # The following is equivalent to the first example above. - $ gcloud beta privateca certificates list --issuer=my-ca - - # The following is equivalent to the second example above. - $ gcloud beta privateca certificates list - -FLAGS - CERTIFICATE AUTHORITY resource - The issuing Certificate Authority. If - this is omitted, Certificates issued by all Certificate Authorities in the - given location will be listed. The arguments in this group can be used to - specify the attributes of this resource. (NOTE) Some attributes are not - given arguments in this group but can be set in other ways. - - To set the project attribute: - ◆ provide the argument --issuer on the command line with a fully - specified name; - ◆ defaults to all Certificate Authorities in the given location with a - fully specified name; - ◆ provide the argument --project on the command line; - ◆ set the property core/project. - - --issuer=ISSUER - ID of the CERTIFICATE_AUTHORITY or fully qualified identifier for the - CERTIFICATE_AUTHORITY. - - To set the certificate_authority attribute: - ▸ provide the argument --issuer on the command line; - ▸ defaults to all Certificate Authorities in the given location. - - --location=LOCATION - The location of the CERTIFICATE_AUTHORITY. - - To set the location attribute: - ▸ provide the argument --issuer on the command line with a fully - specified name; - ▸ defaults to all Certificate Authorities in the given location - with a fully specified name; - ▸ provide the argument --location on the command line; - ▸ set the property privateca/location. - -LIST COMMAND FLAGS - --filter=EXPRESSION - Apply a Boolean filter EXPRESSION to each resource item to be listed. - If the expression evaluates True, then that item is listed. For more - details and examples of filter expressions, run $ gcloud topic filters. - This flag interacts with other flags that are applied in this order: - --flatten, --sort-by, --filter, --limit. - - --limit=LIMIT - Maximum number of resources to list. The default is unlimited. This - flag interacts with other flags that are applied in this order: - --flatten, --sort-by, --filter, --limit. - - --page-size=PAGE_SIZE; default=100 - Some services group resource list output into pages. This flag - specifies the maximum number of resources per page. The default is 100. - Paging may be applied before or after --filter and --limit depending on - the service. - - --sort-by=[FIELD,...] - Comma-separated list of resource field key names to sort by. The - default order is ascending. Prefix a field with ``~'' for descending - order on that field. This flag interacts with other flags that are - applied in this order: --flatten, --sort-by, --filter, --limit. - - --uri - Print a list of resource URIs instead of the default output, and change - the command output to a list of URIs. If this flag is used with - --format, the formatting is applied on this URI list. To display URIs - alongside other keys instead, use the uri() transform. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -NOTES - This command is currently in beta and might change without notice. This - variant is also available: - - $ gcloud privateca certificates list - diff --git a/gcloud/beta/privateca/certificates/revoke b/gcloud/beta/privateca/certificates/revoke deleted file mode 100644 index 593282057..000000000 --- a/gcloud/beta/privateca/certificates/revoke +++ /dev/null @@ -1,114 +0,0 @@ -NAME - gcloud beta privateca certificates revoke - revoke a certificate - -SYNOPSIS - gcloud beta privateca certificates revoke - (--certificate=CERTIFICATE | --serial-number=SERIAL_NUMBER) - [--reason=REASON; default="unspecified"] - [--issuer=ISSUER : --issuer-location=ISSUER_LOCATION] - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (BETA) Revokes the given certificate for the given reason. - -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 - - 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 - -REQUIRED FLAGS - The certificate identifier. - - Exactly one of these must be specified: - - Certificate resource - The certificate to revoke. 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 --certificate on the command line with a fully - specified name; - ▸ provide the argument --project on the command line; - ▸ set the property core/project. - - To set the issuer-location attribute: - ▸ provide the argument --certificate on the command line with a fully - specified name; - ▸ set the property privateca/location. - - To set the issuer attribute: - ▸ provide the argument --certificate on the command line with a fully - specified name. - - --certificate=CERTIFICATE - ID of the certificate or fully qualified identifier for the - certificate. - - To set the certificate attribute: - ▫ provide the argument --certificate on the command line. - - --serial-number=SERIAL_NUMBER - The serial number of the certificate. - -OPTIONAL FLAGS - --reason=REASON; default="unspecified" - Revocation reason to include in the CRL. REASON must be one of: - affiliation-changed, attribute-authority-compromise, - certificate-authority-compromise, certificate-hold, - cessation-of-operation, key-compromise, privilege-withdrawn, - unspecified, superseded. - - Issuing CA resource - The issuing certificate authority of the certificate - to revoke. The arguments in this group can be used to specify the - attributes of this resource. (NOTE) Some attributes are not given - arguments in this group but can be set in other ways. - - To set the project attribute: - ◆ provide the argument --issuer on the command line with a fully - specified name; - ◆ provide the argument --project on the command line; - ◆ set the property core/project. - - --issuer=ISSUER - ID of the Issuing CA or fully qualified identifier for the Issuing - CA. - - To set the issuer attribute: - ▸ provide the argument --issuer on the command line. - - This flag argument must be specified if any of the other arguments in - this group are specified. - - --issuer-location=ISSUER_LOCATION - The location of the Issuing CA. - - To set the issuer-location attribute: - ▸ provide the argument --issuer on the command line with a fully - specified name; - ▸ provide the argument --issuer-location on the command line; - ▸ set the property privateca/location. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -NOTES - This command is currently in beta and might change without notice. This - variant is also available: - - $ gcloud privateca certificates revoke - diff --git a/gcloud/beta/privateca/certificates/update b/gcloud/beta/privateca/certificates/update deleted file mode 100644 index 159ba9ff5..000000000 --- a/gcloud/beta/privateca/certificates/update +++ /dev/null @@ -1,101 +0,0 @@ -NAME - gcloud beta privateca certificates update - update an existing certificate - -SYNOPSIS - gcloud beta privateca certificates update - (CERTIFICATE : --issuer=ISSUER --issuer-location=ISSUER_LOCATION) - [--update-labels=[KEY=VALUE,...]] - [--clear-labels | --remove-labels=[KEY,...]] [GCLOUD_WIDE_FLAG ...] - -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 - -POSITIONAL ARGUMENTS - CERTIFICATE resource - The certificate to update. The arguments in this - group can be used to specify the attributes of this resource. (NOTE) Some - attributes are not given arguments in this group but can be set in other - ways. - - To set the project attribute: - ◆ provide the argument CERTIFICATE on the command line with a fully - specified name; - ◆ provide the argument --project on the command line; - ◆ set the property core/project. - - This must be specified. - - CERTIFICATE - ID of the CERTIFICATE or fully qualified identifier for the - CERTIFICATE. - - To set the certificate attribute: - ▸ provide the argument CERTIFICATE on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --issuer=ISSUER - The issuing certificate authority of the CERTIFICATE. - - To set the issuer attribute: - ▸ provide the argument CERTIFICATE on the command line with a fully - specified name; - ▸ provide the argument --issuer on the command line. - - --issuer-location=ISSUER_LOCATION - The location of the CERTIFICATE. - - To set the issuer-location attribute: - ▸ provide the argument CERTIFICATE on the command line with a fully - specified name; - ▸ provide the argument --issuer-location on the command line; - ▸ set the property privateca/location. - -FLAGS - --update-labels=[KEY=VALUE,...] - List of label KEY=VALUE pairs to update. If a label exists, its value - is modified. Otherwise, a new label is created. - - Keys must start with a lowercase character and contain only hyphens - (-), underscores (_), lowercase characters, and numbers. Values must - contain only hyphens (-), underscores (_), lowercase characters, and - numbers. - - At most one of these can be specified: - - --clear-labels - Remove all labels. If --update-labels is also specified then - --clear-labels is applied first. - - For example, to remove all labels: - - $ gcloud beta privateca certificates update --clear-labels - - To remove all existing labels and create two new labels, foo and baz: - - $ gcloud beta privateca certificates update --clear-labels \ - --update-labels foo=bar,baz=qux - - --remove-labels=[KEY,...] - List of label keys to remove. If a label does not exist it is - silently ignored. If --update-labels is also specified then - --update-labels is applied first. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -NOTES - This command is currently in beta and might change without notice. This - variant is also available: - - $ gcloud privateca certificates update - diff --git a/gcloud/beta/privateca/help b/gcloud/beta/privateca/help deleted file mode 100644 index 24914fee6..000000000 --- a/gcloud/beta/privateca/help +++ /dev/null @@ -1,40 +0,0 @@ -NAME - gcloud beta privateca - manage private Certificate Authorities on Google - Cloud - -SYNOPSIS - gcloud beta privateca GROUP [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (BETA) The privateca command group lets you create and manage private - certificate authorities and certificates. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --help. - - Run $ gcloud help for details. - -GROUPS - GROUP is one of the following: - - certificates - (BETA) Manage certificates. - - locations - (BETA) Manage locations. - - reusable-configs - (BETA) Manage reusable configs. - - roots - (BETA) Manage root certificate authorities. - - subordinates - (BETA) Manage subordinate certificate authorities. - -NOTES - This command is currently in beta and might change without notice. This - variant is also available: - - $ gcloud privateca - diff --git a/gcloud/beta/privateca/locations/help b/gcloud/beta/privateca/locations/help deleted file mode 100644 index 6b30a943f..000000000 --- a/gcloud/beta/privateca/locations/help +++ /dev/null @@ -1,26 +0,0 @@ -NAME - gcloud beta privateca locations - manage locations - -SYNOPSIS - gcloud beta privateca locations COMMAND [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (BETA) Manage locations. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --help. - - Run $ gcloud help for details. - -COMMANDS - COMMAND is one of the following: - - list - (BETA) List supported locations for the Private CA preview API. - -NOTES - This command is currently in beta and might change without notice. This - variant is also available: - - $ gcloud privateca locations - diff --git a/gcloud/beta/privateca/reusable-configs/describe b/gcloud/beta/privateca/reusable-configs/describe deleted file mode 100644 index 806c7db36..000000000 --- a/gcloud/beta/privateca/reusable-configs/describe +++ /dev/null @@ -1,59 +0,0 @@ -NAME - gcloud beta privateca reusable-configs describe - show details about a - reusable config - -SYNOPSIS - gcloud beta privateca reusable-configs describe - (REUSABLE_CONFIG : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (BETA) Show details about a reusable config. - -EXAMPLES - To show details about a reusable config, run: - - $ gcloud beta privateca reusable-configs describe leaf-server-tls - -POSITIONAL ARGUMENTS - Reusable config resource - The reusable config to describe. The arguments - in this group can be used to specify the attributes of this resource. - (NOTE) Some attributes are not given arguments in this group but can be - set in other ways. - - To set the project attribute: - ◆ provide the argument REUSABLE_CONFIG on the command line with a fully - specified name; - ◆ project will default to privateca-data. - - This must be specified. - - REUSABLE_CONFIG - ID of the reusable config or fully qualified identifier for the - reusable config. - - To set the reusable_config attribute: - ▸ provide the argument REUSABLE_CONFIG on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --location=LOCATION - The location of the reusable config. - - To set the location attribute: - ▸ provide the argument REUSABLE_CONFIG on the command line with a - fully specified name; - ▸ provide the argument --location on the command line; - ▸ set the property privateca/location. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -NOTES - This command is currently in beta and might change without notice. - diff --git a/gcloud/beta/privateca/reusable-configs/help b/gcloud/beta/privateca/reusable-configs/help deleted file mode 100644 index 0797bedba..000000000 --- a/gcloud/beta/privateca/reusable-configs/help +++ /dev/null @@ -1,26 +0,0 @@ -NAME - gcloud beta privateca reusable-configs - manage reusable configs - -SYNOPSIS - gcloud beta privateca reusable-configs COMMAND [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (BETA) Manage reusable configs. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --help. - - Run $ gcloud help for details. - -COMMANDS - COMMAND is one of the following: - - describe - (BETA) Show details about a reusable config. - - list - (BETA) List reusable configs. - -NOTES - This command is currently in beta and might change without notice. - diff --git a/gcloud/beta/privateca/roots/add-iam-policy-binding b/gcloud/beta/privateca/roots/add-iam-policy-binding deleted file mode 100644 index bbabe1870..000000000 --- a/gcloud/beta/privateca/roots/add-iam-policy-binding +++ /dev/null @@ -1,94 +0,0 @@ -NAME - gcloud beta privateca roots add-iam-policy-binding - add IAM policy binding - for a root Certificate Authority - -SYNOPSIS - gcloud beta privateca roots add-iam-policy-binding - (CERTIFICATE_AUTHORITY : --location=LOCATION) --member=PRINCIPAL - --role=ROLE [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (BETA) Adds a policy binding to the IAM policy of a root Certificate - Authority. One binding consists of a member and a role. - - See https://cloud.google.com/iam/docs/managing-policies for details of - policy role and member types. - -EXAMPLES - To add an IAM policy binding for the role of - 'roles/privateca.certificateManager' for the user 'test-user@gmail.com' on - 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' - -POSITIONAL ARGUMENTS - Certificate Authority resource - The certificate authority for which to - add the IAM policy binding. The arguments in this group can be used to - specify the attributes of this resource. (NOTE) Some attributes are not - given arguments in this group but can be set in other ways. - - To set the project attribute: - ◆ provide the argument certificate_authority on the command line with a - fully specified name; - ◆ set the property core/project; - ◆ provide the argument --project on the command line. - - This must be specified. - - CERTIFICATE_AUTHORITY - ID of the Certificate Authority or fully qualified identifier for the - Certificate Authority. - - To set the certificate_authority attribute: - ▸ provide the argument certificate_authority on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --location=LOCATION - The location of the Certificate Authority. - - To set the location attribute: - ▸ provide the argument certificate_authority on the command line - with a fully specified name; - ▸ provide the argument --location on the command line; - ▸ set the property privateca/location. - -REQUIRED FLAGS - --member=PRINCIPAL - The principal to add the binding for. Should be of the form - user|group|serviceAccount:email or domain:domain. - - Examples: user:test-user@gmail.com, group:admins@example.com, - serviceAccount:test123@example.domain.com, or - domain:example.domain.com. - - Some resources also accept the following special values: - ◆ allUsers - Special identifier that represents anyone who is on the - internet, with or without a Google account. - ◆ allAuthenticatedUsers - Special identifier that represents anyone - who is authenticated with a Google account or a service account. - - --role=ROLE - Role name to assign to the principal. The role name is the complete - path of a predefined role, such as roles/logging.viewer, or the role ID - for a custom role, such as - organizations/{ORGANIZATION_ID}/roles/logging.viewer. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -API REFERENCE - This command uses the privateca/v1beta1 API. The full documentation for - this API can be found at: https://cloud.google.com/ - -NOTES - This command is currently in beta and might change without notice. - diff --git a/gcloud/beta/privateca/roots/create b/gcloud/beta/privateca/roots/create deleted file mode 100644 index 636c4090e..000000000 --- a/gcloud/beta/privateca/roots/create +++ /dev/null @@ -1,305 +0,0 @@ -NAME - gcloud beta privateca roots create - create a new root certificate - authority - -SYNOPSIS - gcloud beta privateca roots create - (CERTIFICATE_AUTHORITY : --location=LOCATION) [--bucket=BUCKET] - [--dns-san=[DNS_SAN,...]] [--email-san=[EMAIL_SAN,...]] - [--ip-san=[IP_SAN,...]] [--issuance-policy=ISSUANCE_POLICY] - [--labels=[KEY=VALUE,...]] [--no-publish-ca-cert] [--no-publish-crl] - [--subject=[SUBJECT,...]] [--tier=TIER; default="enterprise"] - [--uri-san=[URI_SAN,...]] [--validity=VALIDITY; default="P10Y"] - [--from-ca=FROM_CA : --from-ca-location=FROM_CA_LOCATION - --from-ca-project=FROM_CA_PROJECT] - [--key-algorithm=KEY_ALGORITHM; default="rsa-pkcs1-4096-sha256" - | [--kms-key-version=KMS_KEY_VERSION : --kms-key=KMS_KEY - --kms-keyring=KMS_KEYRING - --kms-location=KMS_LOCATION --kms-project=KMS_PROJECT]] - [--reusable-config=REUSABLE_CONFIG - | --extended-key-usages=[EXTENDED_KEY_USAGES,...] - --key-usages=[KEY_USAGES,...] --max-chain-length=MAX_CHAIN_LENGTH] - [GCLOUD_WIDE_FLAG ...] - -EXAMPLES - To create a root CA that supports one layer of subordinates: - - $ gcloud beta privateca roots create prod-root \ - --kms-key-version="projects/my-project-pki/locations/us-west1/ke\ - yRings/kr1/cryptoKeys/k1/cryptoKeyVersions/1" \ - --subject="CN=Example 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/my-project-pki/locations/us-west1/ke\ - yRings/kr1/cryptoKeys/k1/cryptoKeyVersions/1" \ - --subject="CN=Example 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/my-project-pki/locations/us-west1/ke\ - yRings/kr1/cryptoKeys/k1/cryptoKeyVersions/1" \ - --subject="CN=Example 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/my-project-pki/locations/us-west1/ke\ - yRings/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 - arguments in this group can be used to specify the attributes of this - resource. (NOTE) Some attributes are not given arguments in this group but - can be set in other ways. - - To set the project attribute: - ◆ provide the argument CERTIFICATE_AUTHORITY on the command line with a - fully specified name; - ◆ provide the argument --project on the command line; - ◆ set the property core/project. - - This must be specified. - - CERTIFICATE_AUTHORITY - ID of the Certificate Authority or fully qualified identifier for the - Certificate Authority. - - To set the certificate_authority attribute: - ▸ provide the argument CERTIFICATE_AUTHORITY on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --location=LOCATION - The location of the Certificate Authority. - - To set the location attribute: - ▸ provide the argument CERTIFICATE_AUTHORITY on the command line - with a fully specified name; - ▸ provide the argument --location on the command line; - ▸ set the property privateca/location. - -FLAGS - --bucket=BUCKET - The name of an existing storage bucket to use for storing the CA - certificate and CRLs. If omitted, a new bucket will be created and - managed by the service on your behalf. - - --dns-san=[DNS_SAN,...] - One or more comma-separated DNS Subject Alternative Names. - - --email-san=[EMAIL_SAN,...] - One or more comma-separated email Subject Alternative Names. - - --ip-san=[IP_SAN,...] - One or more comma-separated IP Subject Alternative Names. - - --issuance-policy=ISSUANCE_POLICY - A YAML file describing this Certificate Authority's issuance policy. - - --labels=[KEY=VALUE,...] - List of label KEY=VALUE pairs to add. - - Keys must start with a lowercase character and contain only hyphens - (-), underscores (_), lowercase characters, and numbers. Values must - contain only hyphens (-), underscores (_), lowercase characters, and - numbers. - - --publish-ca-cert - If this is enabled, the following will happen: 1) The CA certificate - will be written to a known location within the CA distribution point. - 2) The AIA extension in all issued certificates will point to the CA - cert URL in that distribition point. - - Note that the same bucket may be used for the CRLs if --publish-crl is - set. - - Enabled by default, use --no-publish-ca-cert to disable. - - --publish-crl - If this gets enabled, the following will happen: 1) CRLs will be - written to a known location within the CA distribution point. 2) The - CDP extension in all future issued certificates will point to the CRL - URL in that distribution point. - - Note that the same bucket may be used for the CA cert if - --publish-ca-cert is set. - - CRL publication is not supported for CAs in the DevOps tier. - - Enabled by default, use --no-publish-crl to disable. - - --subject=[SUBJECT,...] - X.501 name of the certificate subject. Example: --subject - "C=US,ST=California,L=Mountain View,O=Google LLC,CN=google.com" - - --tier=TIER; default="enterprise" - The tier for the Certificate Authority. TIER must be one of: devops, - enterprise. - - --uri-san=[URI_SAN,...] - One or more comma-separated URI Subject Alternative Names. - - --validity=VALIDITY; default="P10Y" - The validity of this CA, as an ISO8601 duration. Defaults to 10 years. - - Source CA resource - An existing CA from which to copy configuration - values for the new CA. You can still override any of those values by - explicitly providing the appropriate flags. The arguments in this group - can be used to specify the attributes of this resource. - - --from-ca=FROM_CA - ID of the source CA or fully qualified identifier for the source CA. - - To set the certificate_authority attribute: - ▸ provide the argument --from-ca on the command line. - - This flag argument must be specified if any of the other arguments in - this group are specified. - - --from-ca-location=FROM_CA_LOCATION - The location of the source CA. - - To set the location attribute: - ▸ provide the argument --from-ca on the command line with a fully - specified name; - ▸ provide the argument --from-ca-location on the command line; - ▸ set the property privateca/location. - - --from-ca-project=FROM_CA_PROJECT - Project ID of the Google Cloud project for the source CA. - - To set the project attribute: - ▸ provide the argument --from-ca on the command line with a fully - specified name; - ▸ provide the argument --from-ca-project on the command line; - ▸ provide the argument --project on the command line; - ▸ set the property core/project. - - The key configuration used for the CA certificate. Defaults to a managed - key if not specified. - - At most one of these can be specified: - - --key-algorithm=KEY_ALGORITHM; default="rsa-pkcs1-4096-sha256" - The crypto algorithm to use for creating a managed KMS key for the - Certificate Authority. The default is rsa-pkcs1-4096-sha256. - KEY_ALGORITHM must be one of: ec-p256-sha256, ec-p384-sha384, - rsa-pkcs1-2048-sha256, rsa-pkcs1-3072-sha256, rsa-pkcs1-4096-sha256, - rsa-pss-2048-sha256, rsa-pss-3078-sha256, rsa-pss-4096-sha256. - - Key version resource - An existing KMS key version to back this CA. The - arguments in this group can be used to specify the attributes of this - resource. - - --kms-key-version=KMS_KEY_VERSION - ID of the key version or fully qualified identifier for the key - version. - - To set the kms-key-version attribute: - ▫ provide the argument --kms-key-version on the command line. - - This flag argument must be specified if any of the other arguments - in this group are specified. - - --kms-key=KMS_KEY - The KMS key of the key version. - - To set the kms-key attribute: - ▫ provide the argument --kms-key-version on the command line with - a fully specified name; - ▫ provide the argument --kms-key on the command line. - - --kms-keyring=KMS_KEYRING - The KMS keyring of the key version. - - To set the kms-keyring attribute: - ▫ provide the argument --kms-key-version on the command line with - a fully specified name; - ▫ provide the argument --kms-keyring on the command line. - - --kms-location=KMS_LOCATION - The location of the key version. - - To set the kms-location attribute: - ▫ provide the argument --kms-key-version on the command line with - a fully specified name; - ▫ provide the argument --kms-location on the command line; - ▫ provide the argument location on the command line; - ▫ set the property privateca/location. - - --kms-project=KMS_PROJECT - The project containing the key version. - - To set the kms-project attribute: - ▫ provide the argument --kms-key-version on the command line with - a fully specified name; - ▫ provide the argument --kms-project on the command line; - ▫ provide the argument project on the command line; - ▫ set the property core/project. - - The X.509 configuration used for the CA certificate. - - At most one of these can be specified: - - Reusable config resource - The Reusable Config containing X.509 values - for this CA. 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 --reusable-config on the command line with a - fully specified name; - ▸ project will default to privateca-data. - - To set the location attribute: - ▸ provide the argument --reusable-config on the command line with a - fully specified name; - ▸ location will default to the same location as the CA. - - --reusable-config=REUSABLE_CONFIG - ID of the reusable config or fully qualified identifier for the - reusable config. - - To set the reusable_config attribute: - ▫ provide the argument --reusable-config on the command line. - - --extended-key-usages=[EXTENDED_KEY_USAGES,...] - The list of extended key usages for this CA. This can only be - provided if --reusable-config is not provided. EXTENDED_KEY_USAGES - must be one of: server_auth, client_auth, code_signing, - email_protection, time_stamping, ocsp_signing. - - --key-usages=[KEY_USAGES,...] - The list of key usages for this CA. This can only be provided if - --reusable-config is not provided. KEY_USAGES must be one of: - digital_signature, content_commitment, key_encipherment, - data_encipherment, key_agreement, cert_sign, crl_sign, encipher_only, - decipher_only. - - --max-chain-length=MAX_CHAIN_LENGTH - Maximum depth of subordinate CAs allowed under this CA for a CA - certificate. This can only be provided if --reusable-config is not - provided. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --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 privateca roots create - diff --git a/gcloud/beta/privateca/roots/delete b/gcloud/beta/privateca/roots/delete deleted file mode 100644 index f4b493187..000000000 --- a/gcloud/beta/privateca/roots/delete +++ /dev/null @@ -1,92 +0,0 @@ -NAME - gcloud beta privateca roots delete - schedule a root certificate authority - for deletion - -SYNOPSIS - gcloud beta privateca roots delete - (CERTIFICATE_AUTHORITY : --location=LOCATION) - [--ignore-active-certificates] [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (BETA) Schedule a root certificate authority for deletion in 30 days. - - Note that any user-managed KMS keys or Google Cloud Storage buckets will - not be affected by this operation. You will need to delete the user- - managed resources separately once the CA is deleted. Any Google-managed - resources will be cleaned up. - - The CA specified in this command MUST: - - 1) be disabled. - 2) have no un-revoked or un-expired certificates. Use the revoke command - to revoke any active certificates. - - You can use the restore command to halt this process. - -EXAMPLES - To schedule a root CA for deletion: - - $ gcloud beta privateca roots delete prod-root --location='us-west1' - - To schedule a root CA for deletion while skipping the confirmation input: - - $ gcloud beta privateca roots delete prod-root \ - --location='us-west1' --quiet - - To un-do the scheduled deletion for a root CA: - - $ gcloud beta privateca roots restore prod-root --location='us-west1' - -POSITIONAL ARGUMENTS - CERTIFICATE AUTHORITY resource - The certificate authority to schedule - deletion for. The arguments in this group can be used to specify the - attributes of this resource. (NOTE) Some attributes are not given - arguments in this group but can be set in other ways. - - To set the project attribute: - ◆ provide the argument CERTIFICATE_AUTHORITY on the command line with a - fully specified name; - ◆ provide the argument --project on the command line; - ◆ set the property core/project. - - This must be specified. - - CERTIFICATE_AUTHORITY - ID of the CERTIFICATE_AUTHORITY or fully qualified identifier for the - CERTIFICATE_AUTHORITY. - - To set the certificate_authority attribute: - ▸ provide the argument CERTIFICATE_AUTHORITY on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --location=LOCATION - The location of the CERTIFICATE_AUTHORITY. - - To set the location attribute: - ▸ provide the argument CERTIFICATE_AUTHORITY on the command line - with a fully specified name; - ▸ provide the argument --location on the command line; - ▸ set the property privateca/location. - -FLAGS - --ignore-active-certificates - If this flag is set, the Certificate Authority will be scheduled for - deletion even if the Certificate Authority has un-revoked or un-expired - certificates. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --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 privateca roots delete - diff --git a/gcloud/beta/privateca/roots/describe b/gcloud/beta/privateca/roots/describe deleted file mode 100644 index b7ca213ec..000000000 --- a/gcloud/beta/privateca/roots/describe +++ /dev/null @@ -1,73 +0,0 @@ -NAME - gcloud beta privateca roots describe - get metadata for a root Certificate - Authority - -SYNOPSIS - gcloud beta privateca roots describe - (CERTIFICATE_AUTHORITY : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (BETA) Returns metadata for the given Certificate Authority. - -EXAMPLES - To get metadata for the root CA 'prod-root' in location 'us-west1': - - $ 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 - -POSITIONAL ARGUMENTS - Certificate Authority resource - The certificate authority for which to - obtain metadata. The arguments in this group can be used to specify the - attributes of this resource. (NOTE) Some attributes are not given - arguments in this group but can be set in other ways. - - To set the project attribute: - ◆ provide the argument certificate_authority on the command line with a - fully specified name; - ◆ set the property core/project; - ◆ provide the argument --project on the command line. - - This must be specified. - - CERTIFICATE_AUTHORITY - ID of the Certificate Authority or fully qualified identifier for the - Certificate Authority. - - To set the certificate_authority attribute: - ▸ provide the argument certificate_authority on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --location=LOCATION - The location of the Certificate Authority. - - To set the location attribute: - ▸ provide the argument certificate_authority on the command line - with a fully specified name; - ▸ provide the argument --location on the command line; - ▸ set the property privateca/location. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -API REFERENCE - This command uses the privateca/v1beta1 API. The full documentation for - this API can be found at: https://cloud.google.com/ - -NOTES - This command is currently in beta and might change without notice. This - variant is also available: - - $ gcloud privateca roots describe - diff --git a/gcloud/beta/privateca/roots/disable b/gcloud/beta/privateca/roots/disable deleted file mode 100644 index 633da46ba..000000000 --- a/gcloud/beta/privateca/roots/disable +++ /dev/null @@ -1,64 +0,0 @@ -NAME - gcloud beta privateca roots disable - disable a root certificate authority - -SYNOPSIS - gcloud beta privateca roots disable - (CERTIFICATE_AUTHORITY : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (BETA) Disables a root certificate authority. The root certificate - authority will not be allowed to issue certificates once disabled. It may - still revoke certificates and/or generate CRLs. - -EXAMPLES - To disable a root CA: - - $ gcloud beta privateca roots disable prod-root --location=us-west1 - -POSITIONAL ARGUMENTS - CERTIFICATE AUTHORITY resource - The certificate authority to disable. The - arguments in this group can be used to specify the attributes of this - resource. (NOTE) Some attributes are not given arguments in this group but - can be set in other ways. - - To set the project attribute: - ◆ provide the argument CERTIFICATE_AUTHORITY on the command line with a - fully specified name; - ◆ provide the argument --project on the command line; - ◆ set the property core/project. - - This must be specified. - - CERTIFICATE_AUTHORITY - ID of the CERTIFICATE_AUTHORITY or fully qualified identifier for the - CERTIFICATE_AUTHORITY. - - To set the certificate_authority attribute: - ▸ provide the argument CERTIFICATE_AUTHORITY on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --location=LOCATION - The location of the CERTIFICATE_AUTHORITY. - - To set the location attribute: - ▸ provide the argument CERTIFICATE_AUTHORITY on the command line - with a fully specified name; - ▸ provide the argument --location on the command line; - ▸ set the property privateca/location. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -NOTES - This command is currently in beta and might change without notice. This - variant is also available: - - $ gcloud privateca roots disable - diff --git a/gcloud/beta/privateca/roots/enable b/gcloud/beta/privateca/roots/enable deleted file mode 100644 index 000572e08..000000000 --- a/gcloud/beta/privateca/roots/enable +++ /dev/null @@ -1,63 +0,0 @@ -NAME - gcloud beta privateca roots enable - enable a root certificate authority - -SYNOPSIS - gcloud beta privateca roots enable - (CERTIFICATE_AUTHORITY : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (BETA) Enables a root certificate authority. The root certificate authority - will be allowed to issue certificates once enabled. - -EXAMPLES - To enable a root CA: - - $ gcloud beta privateca roots enable prod-root --location=us-west1 - -POSITIONAL ARGUMENTS - CERTIFICATE AUTHORITY resource - The certificate authority to enable. The - arguments in this group can be used to specify the attributes of this - resource. (NOTE) Some attributes are not given arguments in this group but - can be set in other ways. - - To set the project attribute: - ◆ provide the argument CERTIFICATE_AUTHORITY on the command line with a - fully specified name; - ◆ provide the argument --project on the command line; - ◆ set the property core/project. - - This must be specified. - - CERTIFICATE_AUTHORITY - ID of the CERTIFICATE_AUTHORITY or fully qualified identifier for the - CERTIFICATE_AUTHORITY. - - To set the certificate_authority attribute: - ▸ provide the argument CERTIFICATE_AUTHORITY on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --location=LOCATION - The location of the CERTIFICATE_AUTHORITY. - - To set the location attribute: - ▸ provide the argument CERTIFICATE_AUTHORITY on the command line - with a fully specified name; - ▸ provide the argument --location on the command line; - ▸ set the property privateca/location. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -NOTES - This command is currently in beta and might change without notice. This - variant is also available: - - $ gcloud privateca roots enable - diff --git a/gcloud/beta/privateca/roots/help b/gcloud/beta/privateca/roots/help deleted file mode 100644 index e6e7c61db..000000000 --- a/gcloud/beta/privateca/roots/help +++ /dev/null @@ -1,59 +0,0 @@ -NAME - gcloud beta privateca roots - manage root certificate authorities - -SYNOPSIS - gcloud beta privateca roots COMMAND [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (BETA) Manage root certificate authorities. - -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 - (BETA) Add IAM policy binding for a root Certificate Authority. - - create - (BETA) Create a new root certificate authority. - - delete - (BETA) Schedule a root certificate authority for deletion. - - describe - (BETA) Get metadata for a root Certificate Authority. - - disable - (BETA) Disable a root certificate authority. - - enable - (BETA) Enable a root certificate authority. - - get-iam-policy - (BETA) Get the IAM policy for a root certificate authority. - - list - (BETA) List the root certificate authorities within a project. - - remove-iam-policy-binding - (BETA) Remove IAM policy binding for a root Certificate Authority. - - restore - (BETA) Restore a root Certificate Authority. - - set-iam-policy - (BETA) Set the IAM policy for a root Certificate Authority. - - update - (BETA) Update an existing root certificate authority. - -NOTES - This command is currently in beta and might change without notice. This - variant is also available: - - $ gcloud privateca roots - diff --git a/gcloud/beta/privateca/roots/list b/gcloud/beta/privateca/roots/list deleted file mode 100644 index 9f2fce112..000000000 --- a/gcloud/beta/privateca/roots/list +++ /dev/null @@ -1,54 +0,0 @@ -NAME - gcloud beta privateca roots list - list the root certificate authorities - within a project - -SYNOPSIS - gcloud beta privateca roots list [--location=LOCATION] [--limit=LIMIT] - [--page-size=PAGE_SIZE; default=100] [--sort-by=[FIELD,...]] [--uri] - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (BETA) List the root certificate authorities within a project. - -FLAGS - --location=LOCATION - Location of the certificate authorities. - -LIST COMMAND FLAGS - --limit=LIMIT - Maximum number of resources to list. The default is unlimited. This - flag interacts with other flags that are applied in this order: - --flatten, --sort-by, --filter, --limit. - - --page-size=PAGE_SIZE; default=100 - Some services group resource list output into pages. This flag - specifies the maximum number of resources per page. The default is 100. - Paging may be applied before or after --filter and --limit depending on - the service. - - --sort-by=[FIELD,...] - Comma-separated list of resource field key names to sort by. The - default order is ascending. Prefix a field with ``~'' for descending - order on that field. This flag interacts with other flags that are - applied in this order: --flatten, --sort-by, --filter, --limit. - - --uri - Print a list of resource URIs instead of the default output, and change - the command output to a list of URIs. If this flag is used with - --format, the formatting is applied on this URI list. To display URIs - alongside other keys instead, use the uri() transform. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -NOTES - This command is currently in beta and might change without notice. This - variant is also available: - - $ gcloud privateca roots list - diff --git a/gcloud/beta/privateca/roots/remove-iam-policy-binding b/gcloud/beta/privateca/roots/remove-iam-policy-binding deleted file mode 100644 index f4c37aaaa..000000000 --- a/gcloud/beta/privateca/roots/remove-iam-policy-binding +++ /dev/null @@ -1,95 +0,0 @@ -NAME - gcloud beta privateca roots remove-iam-policy-binding - remove IAM policy - binding for a root Certificate Authority - -SYNOPSIS - gcloud beta privateca roots remove-iam-policy-binding - (CERTIFICATE_AUTHORITY : --location=LOCATION) --member=PRINCIPAL - --role=ROLE [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (BETA) Removes a policy binding from the IAM policy of a root Certificate - Authority. One binding consists of a member and a role. - - See https://cloud.google.com/iam/docs/managing-policies for details of - policy role and member types. - -EXAMPLES - To remove an IAM policy binding for the role of - 'roles/privateca.certificateManager' for the user 'test-user@gmail.com' on - 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' - -POSITIONAL ARGUMENTS - Certificate Authority resource - The certificate authority for which to - update the IAM policy. The arguments in this group can be used to specify - the attributes of this resource. (NOTE) Some attributes are not given - arguments in this group but can be set in other ways. - - To set the project attribute: - ◆ provide the argument certificate_authority on the command line with a - fully specified name; - ◆ set the property core/project; - ◆ provide the argument --project on the command line. - - This must be specified. - - CERTIFICATE_AUTHORITY - ID of the Certificate Authority or fully qualified identifier for the - Certificate Authority. - - To set the certificate_authority attribute: - ▸ provide the argument certificate_authority on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --location=LOCATION - The location of the Certificate Authority. - - To set the location attribute: - ▸ provide the argument certificate_authority on the command line - with a fully specified name; - ▸ provide the argument --location on the command line; - ▸ set the property privateca/location. - -REQUIRED FLAGS - --member=PRINCIPAL - The principal to remove the binding for. Should be of the form - user|group|serviceAccount:email or domain:domain. - - Examples: user:test-user@gmail.com, group:admins@example.com, - serviceAccount:test123@example.domain.com, or - domain:example.domain.com. - - Deleted principals have an additional deleted: prefix and a ?uid=UID - suffix, where UID is a unique identifier for the principal. Example: - deleted:user:test-user@gmail.com?uid=123456789012345678901. - - Some resources also accept the following special values: - ◆ allUsers - Special identifier that represents anyone who is on the - internet, with or without a Google account. - ◆ allAuthenticatedUsers - Special identifier that represents anyone - who is authenticated with a Google account or a service account. - - --role=ROLE - The role to remove the principal from. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -API REFERENCE - This command uses the privateca/v1beta1 API. The full documentation for - this API can be found at: https://cloud.google.com/ - -NOTES - This command is currently in beta and might change without notice. - diff --git a/gcloud/beta/privateca/roots/restore b/gcloud/beta/privateca/roots/restore deleted file mode 100644 index 74f1dceaf..000000000 --- a/gcloud/beta/privateca/roots/restore +++ /dev/null @@ -1,62 +0,0 @@ -NAME - gcloud beta privateca roots restore - restore a root Certificate Authority - -SYNOPSIS - gcloud beta privateca roots restore - (CERTIFICATE_AUTHORITY : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (BETA) Restores a root Certificate Authority that has been marked for - deletion. A Certificate Authority can be restored within 30 days of being - scheduled for deletion. Use this command to halt the deletion process. A - restored CA will move to DISABLED state. - -EXAMPLES - To restore a root CA: - - $ gcloud beta privateca roots restore prod-root --location=us-west1 - -POSITIONAL ARGUMENTS - CERTIFICATE AUTHORITY resource - The certificate authority to restore. The - arguments in this group can be used to specify the attributes of this - resource. (NOTE) Some attributes are not given arguments in this group but - can be set in other ways. - - To set the project attribute: - ◆ provide the argument CERTIFICATE_AUTHORITY on the command line with a - fully specified name; - ◆ provide the argument --project on the command line; - ◆ set the property core/project. - - This must be specified. - - CERTIFICATE_AUTHORITY - ID of the CERTIFICATE_AUTHORITY or fully qualified identifier for the - CERTIFICATE_AUTHORITY. - - To set the certificate_authority attribute: - ▸ provide the argument CERTIFICATE_AUTHORITY on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --location=LOCATION - The location of the CERTIFICATE_AUTHORITY. - - To set the location attribute: - ▸ provide the argument CERTIFICATE_AUTHORITY on the command line - with a fully specified name; - ▸ provide the argument --location on the command line; - ▸ set the property privateca/location. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -NOTES - This command is currently in beta and might change without notice. - diff --git a/gcloud/beta/privateca/roots/set-iam-policy b/gcloud/beta/privateca/roots/set-iam-policy deleted file mode 100644 index 2f47ea851..000000000 --- a/gcloud/beta/privateca/roots/set-iam-policy +++ /dev/null @@ -1,79 +0,0 @@ -NAME - gcloud beta privateca roots set-iam-policy - set the IAM policy for a root - Certificate Authority - -SYNOPSIS - gcloud beta privateca roots set-iam-policy - (CERTIFICATE_AUTHORITY : --location=LOCATION) POLICY_FILE - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (BETA) Sets the IAM policy for the given root Certificate Authority 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 am IAM policy defined in a JSON file - 'policy.json' and set it for the CA 'prod-root' with the location - 'us-west1': - - $ gcloud beta privateca roots set-iam-policy prod-root policy.json \ - --location=us-west1 - -POSITIONAL ARGUMENTS - Certificate Authority resource - The certificate authority for which to - update the IAM policy. The arguments in this group can be used to specify - the attributes of this resource. (NOTE) Some attributes are not given - arguments in this group but can be set in other ways. - - To set the project attribute: - ◆ provide the argument certificate_authority on the command line with a - fully specified name; - ◆ set the property core/project; - ◆ provide the argument --project on the command line. - - This must be specified. - - CERTIFICATE_AUTHORITY - ID of the Certificate Authority or fully qualified identifier for the - Certificate Authority. - - To set the certificate_authority attribute: - ▸ provide the argument certificate_authority on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --location=LOCATION - The location of the Certificate Authority. - - To set the location attribute: - ▸ provide the argument certificate_authority on the command line - with a fully specified name; - ▸ provide the argument --location on the command line; - ▸ set the property privateca/location. - - POLICY_FILE - Path to a local JSON or YAML formatted file containing a valid policy. - - The output of the get-iam-policy command is a valid file, as is any - JSON or YAML file conforming to the structure of a Policy - (https://cloud.google.com/iam/reference/rest/v1/Policy). - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -API REFERENCE - This command uses the privateca/v1beta1 API. The full documentation for - this API can be found at: https://cloud.google.com/ - -NOTES - This command is currently in beta and might change without notice. - diff --git a/gcloud/beta/privateca/roots/update b/gcloud/beta/privateca/roots/update deleted file mode 100644 index 5a86e8659..000000000 --- a/gcloud/beta/privateca/roots/update +++ /dev/null @@ -1,137 +0,0 @@ -NAME - gcloud beta privateca roots update - update an existing root certificate - authority - -SYNOPSIS - gcloud beta privateca roots update - (CERTIFICATE_AUTHORITY : --location=LOCATION) - [--issuance-policy=ISSUANCE_POLICY] [--no-publish-ca-cert] - [--no-publish-crl] [--update-labels=[KEY=VALUE,...]] - [--clear-labels | --remove-labels=[KEY,...]] [GCLOUD_WIDE_FLAG ...] - -EXAMPLES - To update labels on a root CA: - - $ 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 - -POSITIONAL ARGUMENTS - CERTIFICATE AUTHORITY resource - The certificate authority to update. The - arguments in this group can be used to specify the attributes of this - resource. (NOTE) Some attributes are not given arguments in this group but - can be set in other ways. - - To set the project attribute: - ◆ provide the argument CERTIFICATE_AUTHORITY on the command line with a - fully specified name; - ◆ provide the argument --project on the command line; - ◆ set the property core/project. - - This must be specified. - - CERTIFICATE_AUTHORITY - ID of the CERTIFICATE_AUTHORITY or fully qualified identifier for the - CERTIFICATE_AUTHORITY. - - To set the certificate_authority attribute: - ▸ provide the argument CERTIFICATE_AUTHORITY on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --location=LOCATION - The location of the CERTIFICATE_AUTHORITY. - - To set the location attribute: - ▸ provide the argument CERTIFICATE_AUTHORITY on the command line - with a fully specified name; - ▸ provide the argument --location on the command line; - ▸ set the property privateca/location. - -FLAGS - --issuance-policy=ISSUANCE_POLICY - A YAML file describing this Certificate Authority's issuance policy. - - --publish-ca-cert - If this is enabled, the following will happen: 1) The CA certificate - will be written to a known location within the CA distribution point. - 2) The AIA extension in all issued certificates will point to the CA - cert URL in that distribution point. - - If this gets disabled, the AIA extension will not be written to any - future certificates issued by this CA. However, an existing bucket will - not be deleted, and the CA certificate will not be removed from that - bucket. - - Note that the same bucket may be used for the CRLs if --publish-crl is - set. - - Enabled by default, use --no-publish-ca-cert to disable. - - --publish-crl - If this gets enabled, the following will happen: 1) CRLs will be - written to a known location within the CA distribution point. 2) The - CDP extension in all future issued certificates will point to the CRL - URL in that distribution point. - - If this gets disabled, the CDP extension will not be written to any - future certificates issued by this CA, and new CRLs will not be - published to that bucket (which affects existing certs). However, an - existing bucket will not be deleted, and any existing CRLs will not be - removed from that bucket. - - Note that the same bucket may be used for the CA cert if - --publish-ca-cert is set. - - CRL publication is not supported for CAs in the DevOps tier. - - Enabled by default, use --no-publish-crl to disable. - - --update-labels=[KEY=VALUE,...] - List of label KEY=VALUE pairs to update. If a label exists, its value - is modified. Otherwise, a new label is created. - - Keys must start with a lowercase character and contain only hyphens - (-), underscores (_), lowercase characters, and numbers. Values must - contain only hyphens (-), underscores (_), lowercase characters, and - numbers. - - At most one of these can be specified: - - --clear-labels - Remove all labels. If --update-labels is also specified then - --clear-labels is applied first. - - For example, to remove all labels: - - $ gcloud beta privateca roots update --clear-labels - - To remove all existing labels and create two new labels, foo and baz: - - $ gcloud beta privateca roots update --clear-labels \ - --update-labels foo=bar,baz=qux - - --remove-labels=[KEY,...] - List of label keys to remove. If a label does not exist it is - silently ignored. If --update-labels is also specified then - --update-labels is applied first. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -NOTES - This command is currently in beta and might change without notice. This - variant is also available: - - $ gcloud privateca roots update - diff --git a/gcloud/beta/privateca/subordinates/activate b/gcloud/beta/privateca/subordinates/activate deleted file mode 100644 index d4a3a9820..000000000 --- a/gcloud/beta/privateca/subordinates/activate +++ /dev/null @@ -1,68 +0,0 @@ -NAME - gcloud beta privateca subordinates activate - activate a subordinate - certificate authority in a pending state - -SYNOPSIS - gcloud beta privateca subordinates activate - (CERTIFICATE_AUTHORITY : --location=LOCATION) --pem-chain=PEM_CHAIN - [GCLOUD_WIDE_FLAG ...] - -EXAMPLES - To activate a subordinate CA named 'server-tls-1' in the location 'us' - using a PEM certificate chain in 'chain.crt': - - $ gcloud beta privateca subordinates activate server-tls-1 \ - --location=us --pem-chain=./chain.crt - -POSITIONAL ARGUMENTS - CERTIFICATE AUTHORITY resource - The certificate authority to activate. - The arguments in this group can be used to specify the attributes of this - resource. (NOTE) Some attributes are not given arguments in this group but - can be set in other ways. - - To set the project attribute: - ◆ provide the argument CERTIFICATE_AUTHORITY on the command line with a - fully specified name; - ◆ provide the argument --project on the command line; - ◆ set the property core/project. - - This must be specified. - - CERTIFICATE_AUTHORITY - ID of the CERTIFICATE_AUTHORITY or fully qualified identifier for the - CERTIFICATE_AUTHORITY. - - To set the certificate_authority attribute: - ▸ provide the argument CERTIFICATE_AUTHORITY on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --location=LOCATION - The location of the CERTIFICATE_AUTHORITY. - - To set the location attribute: - ▸ provide the argument CERTIFICATE_AUTHORITY on the command line - with a fully specified name; - ▸ provide the argument --location on the command line; - ▸ set the property privateca/location. - -REQUIRED FLAGS - --pem-chain=PEM_CHAIN - A file containing a list of PEM-encoded certificates, starting with the - current CA certificate and ending with the root CA certificate. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --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 privateca subordinates activate - diff --git a/gcloud/beta/privateca/subordinates/add-iam-policy-binding b/gcloud/beta/privateca/subordinates/add-iam-policy-binding deleted file mode 100644 index efd3afc4a..000000000 --- a/gcloud/beta/privateca/subordinates/add-iam-policy-binding +++ /dev/null @@ -1,95 +0,0 @@ -NAME - gcloud beta privateca subordinates add-iam-policy-binding - add IAM policy - binding for a subordinate Certificate Authority - -SYNOPSIS - gcloud beta privateca subordinates add-iam-policy-binding - (CERTIFICATE_AUTHORITY : --location=LOCATION) --member=PRINCIPAL - --role=ROLE [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (BETA) Adds a policy binding to the IAM policy of a subordinate Certificate - Authority. One binding consists of a member and a role. - - See https://cloud.google.com/iam/docs/managing-policies for details of the - policy file format and contents. - -EXAMPLES - To add an IAM policy binding for the role of - 'roles/privateca.certificateManager' for the user 'test-user@gmail.com' on - 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' - -POSITIONAL ARGUMENTS - Certificate Authority resource - The certificate authority for which to - add the IAM policy binding. The arguments in this group can be used to - specify the attributes of this resource. (NOTE) Some attributes are not - given arguments in this group but can be set in other ways. - - To set the project attribute: - ◆ provide the argument certificate_authority on the command line with a - fully specified name; - ◆ set the property core/project; - ◆ provide the argument --project on the command line. - - This must be specified. - - CERTIFICATE_AUTHORITY - ID of the Certificate Authority or fully qualified identifier for the - Certificate Authority. - - To set the certificate_authority attribute: - ▸ provide the argument certificate_authority on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --location=LOCATION - The location of the Certificate Authority. - - To set the location attribute: - ▸ provide the argument certificate_authority on the command line - with a fully specified name; - ▸ provide the argument --location on the command line; - ▸ set the property privateca/location. - -REQUIRED FLAGS - --member=PRINCIPAL - The principal to add the binding for. Should be of the form - user|group|serviceAccount:email or domain:domain. - - Examples: user:test-user@gmail.com, group:admins@example.com, - serviceAccount:test123@example.domain.com, or - domain:example.domain.com. - - Some resources also accept the following special values: - ◆ allUsers - Special identifier that represents anyone who is on the - internet, with or without a Google account. - ◆ allAuthenticatedUsers - Special identifier that represents anyone - who is authenticated with a Google account or a service account. - - --role=ROLE - Role name to assign to the principal. The role name is the complete - path of a predefined role, such as roles/logging.viewer, or the role ID - for a custom role, such as - organizations/{ORGANIZATION_ID}/roles/logging.viewer. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -API REFERENCE - This command uses the privateca/v1beta1 API. The full documentation for - this API can be found at: https://cloud.google.com/ - -NOTES - This command is currently in beta and might change without notice. - diff --git a/gcloud/beta/privateca/subordinates/create b/gcloud/beta/privateca/subordinates/create deleted file mode 100644 index 2693207fd..000000000 --- a/gcloud/beta/privateca/subordinates/create +++ /dev/null @@ -1,354 +0,0 @@ -NAME - gcloud beta privateca subordinates create - create a new subordinate - certificate authority - -SYNOPSIS - gcloud beta privateca subordinates create - (CERTIFICATE_AUTHORITY : --location=LOCATION) - (--create-csr --csr-output-file=CSR_OUTPUT_FILE - | [--issuer=ISSUER : --issuer-location=ISSUER_LOCATION]) - [--bucket=BUCKET] [--dns-san=[DNS_SAN,...]] - [--email-san=[EMAIL_SAN,...]] [--ip-san=[IP_SAN,...]] - [--issuance-policy=ISSUANCE_POLICY] [--labels=[KEY=VALUE,...]] - [--no-publish-ca-cert] [--no-publish-crl] [--subject=[SUBJECT,...]] - [--tier=TIER; default="enterprise"] [--uri-san=[URI_SAN,...]] - [--validity=VALIDITY; default="P3Y"] - [--from-ca=FROM_CA : --from-ca-location=FROM_CA_LOCATION - --from-ca-project=FROM_CA_PROJECT] - [--key-algorithm=KEY_ALGORITHM; default="rsa-pkcs1-2048-sha256" - | [--kms-key-version=KMS_KEY_VERSION : --kms-key=KMS_KEY - --kms-keyring=KMS_KEYRING - --kms-location=KMS_LOCATION --kms-project=KMS_PROJECT]] - [--reusable-config=REUSABLE_CONFIG - | --extended-key-usages=[EXTENDED_KEY_USAGES,...] - --key-usages=[KEY_USAGES,...] --max-chain-length=MAX_CHAIN_LENGTH] - [GCLOUD_WIDE_FLAG ...] - -EXAMPLES - To create a subordinate CA named 'server-tls-1' whose issuer is on Private - CA: - - $ gcloud beta privateca subordinates create server-tls-1 \ - --subject="CN=Example TLS CA, O=Google" --issuer=prod-root \ - --issuer-location=us-west1 \ - --kms-key-version="projects/my-project-pki/locations/us-west1/ke\ - yRings/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=Example TLS CA, O=Google" --create-csr \ - --csr-output-file="./csr.pem" \ - --kms-key-version="projects/my-project-pki/locations/us-west1/ke\ - yRings/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/my-project-pki/locations/us-west1/ke\ - yRings/kr1/cryptoKeys/key2/cryptoKeyVersions/1" - -POSITIONAL ARGUMENTS - Certificate Authority resource - The name of the subordinate CA to create. - The arguments in this group can be used to specify the attributes of this - resource. (NOTE) Some attributes are not given arguments in this group but - can be set in other ways. - - To set the project attribute: - ◆ provide the argument CERTIFICATE_AUTHORITY on the command line with a - fully specified name; - ◆ provide the argument --project on the command line; - ◆ set the property core/project. - - This must be specified. - - CERTIFICATE_AUTHORITY - ID of the Certificate Authority or fully qualified identifier for the - Certificate Authority. - - To set the certificate_authority attribute: - ▸ provide the argument CERTIFICATE_AUTHORITY on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --location=LOCATION - The location of the Certificate Authority. - - To set the location attribute: - ▸ provide the argument CERTIFICATE_AUTHORITY on the command line - with a fully specified name; - ▸ provide the argument --location on the command line; - ▸ set the property privateca/location. - -REQUIRED FLAGS - The issuer configuration used for this CA certificate. - - Exactly one of these must be specified: - - If the issuing CA is not hosted on Private CA, you must provide these - settings: - - --create-csr - Indicates that a CSR should be generated which can be signed by the - issuing CA. This must be set if --issuer is not provided. - - This flag argument must be specified if any of the other arguments - in this group are specified. - - --csr-output-file=CSR_OUTPUT_FILE - The path where the resulting PEM-encoded CSR file should be - written. - - This flag argument must be specified if any of the other arguments - in this group are specified. - - Issuer resource - The issuing certificate authority to use, if it is on - Private CA. The arguments in this group can be used to specify the - attributes of this resource. (NOTE) Some attributes are not given - arguments in this group but can be set in other ways. - - To set the project attribute: - ▸ provide the argument --issuer on the command line with a fully - specified name; - ▸ provide the argument --project on the command line; - ▸ set the property core/project. - - --issuer=ISSUER - ID of the Issuer or fully qualified identifier for the Issuer. - - To set the certificate_authority attribute: - ▫ provide the argument --issuer on the command line. - - This flag argument must be specified if any of the other arguments - in this group are specified. - - --issuer-location=ISSUER_LOCATION - The location of the Issuer. - - To set the location attribute: - ▫ provide the argument --issuer on the command line with a fully - specified name; - ▫ provide the argument --issuer-location on the command line; - ▫ set the property privateca/location. - -OPTIONAL FLAGS - --bucket=BUCKET - The name of an existing storage bucket to use for storing the CA - certificate and CRLs. If omitted, a new bucket will be created and - managed by the service on your behalf. - - --dns-san=[DNS_SAN,...] - One or more comma-separated DNS Subject Alternative Names. - - --email-san=[EMAIL_SAN,...] - One or more comma-separated email Subject Alternative Names. - - --ip-san=[IP_SAN,...] - One or more comma-separated IP Subject Alternative Names. - - --issuance-policy=ISSUANCE_POLICY - A YAML file describing this Certificate Authority's issuance policy. - - --labels=[KEY=VALUE,...] - List of label KEY=VALUE pairs to add. - - Keys must start with a lowercase character and contain only hyphens - (-), underscores (_), lowercase characters, and numbers. Values must - contain only hyphens (-), underscores (_), lowercase characters, and - numbers. - - --publish-ca-cert - If this is enabled, the following will happen: 1) The CA certificate - will be written to a known location within the CA distribution point. - 2) The AIA extension in all issued certificates will point to the CA - cert URL in that distribition point. - - Note that the same bucket may be used for the CRLs if --publish-crl is - set. - - Enabled by default, use --no-publish-ca-cert to disable. - - --publish-crl - If this gets enabled, the following will happen: 1) CRLs will be - written to a known location within the CA distribution point. 2) The - CDP extension in all future issued certificates will point to the CRL - URL in that distribution point. - - Note that the same bucket may be used for the CA cert if - --publish-ca-cert is set. - - CRL publication is not supported for CAs in the DevOps tier. - - Enabled by default, use --no-publish-crl to disable. - - --subject=[SUBJECT,...] - X.501 name of the certificate subject. Example: --subject - "C=US,ST=California,L=Mountain View,O=Google LLC,CN=google.com" - - --tier=TIER; default="enterprise" - The tier for the Certificate Authority. TIER must be one of: devops, - enterprise. - - --uri-san=[URI_SAN,...] - One or more comma-separated URI Subject Alternative Names. - - --validity=VALIDITY; default="P3Y" - The validity of this CA, as an ISO8601 duration. Defaults to 3 years. - - Source CA resource - An existing CA from which to copy configuration - values for the new CA. You can still override any of those values by - explicitly providing the appropriate flags. The arguments in this group - can be used to specify the attributes of this resource. - - --from-ca=FROM_CA - ID of the source CA or fully qualified identifier for the source CA. - - To set the certificate_authority attribute: - ▸ provide the argument --from-ca on the command line. - - This flag argument must be specified if any of the other arguments in - this group are specified. - - --from-ca-location=FROM_CA_LOCATION - The location of the source CA. - - To set the location attribute: - ▸ provide the argument --from-ca on the command line with a fully - specified name; - ▸ provide the argument --from-ca-location on the command line; - ▸ set the property privateca/location. - - --from-ca-project=FROM_CA_PROJECT - Project ID of the Google Cloud project for the source CA. - - To set the project attribute: - ▸ provide the argument --from-ca on the command line with a fully - specified name; - ▸ provide the argument --from-ca-project on the command line; - ▸ provide the argument --project on the command line; - ▸ set the property core/project. - - The key configuration used for the CA certificate. Defaults to a managed - key if not specified. - - At most one of these can be specified: - - --key-algorithm=KEY_ALGORITHM; default="rsa-pkcs1-2048-sha256" - The crypto algorithm to use for creating a managed KMS key for the - Certificate Authority. The default is rsa-pkcs1-2048-sha256. - KEY_ALGORITHM must be one of: ec-p256-sha256, ec-p384-sha384, - rsa-pkcs1-2048-sha256, rsa-pkcs1-3072-sha256, rsa-pkcs1-4096-sha256, - rsa-pss-2048-sha256, rsa-pss-3078-sha256, rsa-pss-4096-sha256. - - Key version resource - The KMS key version backing this CA. The - arguments in this group can be used to specify the attributes of this - resource. - - --kms-key-version=KMS_KEY_VERSION - ID of the key version or fully qualified identifier for the key - version. - - To set the kms-key-version attribute: - ▫ provide the argument --kms-key-version on the command line. - - This flag argument must be specified if any of the other arguments - in this group are specified. - - --kms-key=KMS_KEY - The KMS key of the key version. - - To set the kms-key attribute: - ▫ provide the argument --kms-key-version on the command line with - a fully specified name; - ▫ provide the argument --kms-key on the command line. - - --kms-keyring=KMS_KEYRING - The KMS keyring of the key version. - - To set the kms-keyring attribute: - ▫ provide the argument --kms-key-version on the command line with - a fully specified name; - ▫ provide the argument --kms-keyring on the command line. - - --kms-location=KMS_LOCATION - The location of the key version. - - To set the kms-location attribute: - ▫ provide the argument --kms-key-version on the command line with - a fully specified name; - ▫ provide the argument --kms-location on the command line; - ▫ provide the argument location on the command line; - ▫ set the property privateca/location. - - --kms-project=KMS_PROJECT - The project containing the key version. - - To set the kms-project attribute: - ▫ provide the argument --kms-key-version on the command line with - a fully specified name; - ▫ provide the argument --kms-project on the command line; - ▫ provide the argument project on the command line; - ▫ set the property core/project. - - The X.509 configuration used for the CA certificate. - - At most one of these can be specified: - - Reusable config resource - The Reusable Config containing X.509 values - for this CA. 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 --reusable-config on the command line with a - fully specified name; - ▸ project will default to privateca-data. - - To set the location attribute: - ▸ provide the argument --reusable-config on the command line with a - fully specified name; - ▸ location will default to the same location as the CA. - - --reusable-config=REUSABLE_CONFIG - ID of the reusable config or fully qualified identifier for the - reusable config. - - To set the reusable_config attribute: - ▫ provide the argument --reusable-config on the command line. - - --extended-key-usages=[EXTENDED_KEY_USAGES,...] - The list of extended key usages for this CA. This can only be - provided if --reusable-config is not provided. EXTENDED_KEY_USAGES - must be one of: server_auth, client_auth, code_signing, - email_protection, time_stamping, ocsp_signing. - - --key-usages=[KEY_USAGES,...] - The list of key usages for this CA. This can only be provided if - --reusable-config is not provided. KEY_USAGES must be one of: - digital_signature, content_commitment, key_encipherment, - data_encipherment, key_agreement, cert_sign, crl_sign, encipher_only, - decipher_only. - - --max-chain-length=MAX_CHAIN_LENGTH - Maximum depth of subordinate CAs allowed under this CA for a CA - certificate. This can only be provided if --reusable-config is not - provided. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --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 privateca subordinates create - diff --git a/gcloud/beta/privateca/subordinates/delete b/gcloud/beta/privateca/subordinates/delete deleted file mode 100644 index 264ac8707..000000000 --- a/gcloud/beta/privateca/subordinates/delete +++ /dev/null @@ -1,96 +0,0 @@ -NAME - gcloud beta privateca subordinates delete - schedule a subordinate - certificate authority for deletion - -SYNOPSIS - gcloud beta privateca subordinates delete - (CERTIFICATE_AUTHORITY : --location=LOCATION) - [--ignore-active-certificates] [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (BETA) Schedule a subordinate certificate authority for deletion in 30 - days. - - Note that any user-managed KMS keys or Google Cloud Storage buckets will - not be affected by this operation. You will need to delete the user- - managed resources separately once the CA is deleted. Any Google-managed - resources will be cleaned up. - - The CA specified in this command MUST: - - 1) be disabled. - 2) have no un-revoked or un-expired certificates. Use the revoke command - to revoke any active certificates. - - You can use the restore command to halt this process. - -EXAMPLES - To schedule a subordinate CA for deletion: - - $ gcloud beta privateca subordinates delete server-tls-1 \ - --location='us-west1' - - To schedule a subordinate CA for deletion while skipping the confirmation - input: - - $ gcloud beta privateca subordinates delete server-tls-1 \ - --location='us-west1' --quiet - - To un-do the scheduled deletion for a subordinate CA: - - $ gcloud beta privateca subordinates restore server-tls-1 \ - --location='us-west1' - -POSITIONAL ARGUMENTS - CERTIFICATE AUTHORITY resource - The certificate authority to schedule - deletion for. The arguments in this group can be used to specify the - attributes of this resource. (NOTE) Some attributes are not given - arguments in this group but can be set in other ways. - - To set the project attribute: - ◆ provide the argument CERTIFICATE_AUTHORITY on the command line with a - fully specified name; - ◆ provide the argument --project on the command line; - ◆ set the property core/project. - - This must be specified. - - CERTIFICATE_AUTHORITY - ID of the CERTIFICATE_AUTHORITY or fully qualified identifier for the - CERTIFICATE_AUTHORITY. - - To set the certificate_authority attribute: - ▸ provide the argument CERTIFICATE_AUTHORITY on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --location=LOCATION - The location of the CERTIFICATE_AUTHORITY. - - To set the location attribute: - ▸ provide the argument CERTIFICATE_AUTHORITY on the command line - with a fully specified name; - ▸ provide the argument --location on the command line; - ▸ set the property privateca/location. - -FLAGS - --ignore-active-certificates - If this flag is set, the Certificate Authority will be scheduled for - deletion even if the Certificate Authority has un-revoked or un-expired - certificates. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --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 privateca subordinates delete - diff --git a/gcloud/beta/privateca/subordinates/describe b/gcloud/beta/privateca/subordinates/describe deleted file mode 100644 index 23dc0bd10..000000000 --- a/gcloud/beta/privateca/subordinates/describe +++ /dev/null @@ -1,76 +0,0 @@ -NAME - gcloud beta privateca subordinates describe - get metadata for a - subordinate Certificate Authority - -SYNOPSIS - gcloud beta privateca subordinates describe - (CERTIFICATE_AUTHORITY : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (BETA) Returns metadata for the given Certificate Authority. - -EXAMPLES - To get metadata for the subordinate CA 'server-tls-1' in location - 'us-west1': - - $ gcloud beta privateca subordinates describe server-tls-1 \ - --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 - -POSITIONAL ARGUMENTS - Certificate Authority resource - The certificate authority for which to - obtain metadata. The arguments in this group can be used to specify the - attributes of this resource. (NOTE) Some attributes are not given - arguments in this group but can be set in other ways. - - To set the project attribute: - ◆ provide the argument certificate_authority on the command line with a - fully specified name; - ◆ set the property core/project; - ◆ provide the argument --project on the command line. - - This must be specified. - - CERTIFICATE_AUTHORITY - ID of the Certificate Authority or fully qualified identifier for the - Certificate Authority. - - To set the certificate_authority attribute: - ▸ provide the argument certificate_authority on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --location=LOCATION - The location of the Certificate Authority. - - To set the location attribute: - ▸ provide the argument certificate_authority on the command line - with a fully specified name; - ▸ provide the argument --location on the command line; - ▸ set the property privateca/location. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -API REFERENCE - This command uses the privateca/v1beta1 API. The full documentation for - this API can be found at: https://cloud.google.com/ - -NOTES - This command is currently in beta and might change without notice. This - variant is also available: - - $ gcloud privateca subordinates describe - diff --git a/gcloud/beta/privateca/subordinates/disable b/gcloud/beta/privateca/subordinates/disable deleted file mode 100644 index a3e198001..000000000 --- a/gcloud/beta/privateca/subordinates/disable +++ /dev/null @@ -1,66 +0,0 @@ -NAME - gcloud beta privateca subordinates disable - disable a subordinate - certificate authority - -SYNOPSIS - gcloud beta privateca subordinates disable - (CERTIFICATE_AUTHORITY : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (BETA) Disables a subordinate certificate authority. The subordinate - certificate authority will not be allowed to issue certificates once - disabled. It may still revoke certificates and/or generate CRLs. - -EXAMPLES - To disable a subordinate CA: - - $ gcloud beta privateca subordinates disable server-tls1 \ - --location=us-west1 - -POSITIONAL ARGUMENTS - CERTIFICATE AUTHORITY resource - The certificate authority to disable. The - arguments in this group can be used to specify the attributes of this - resource. (NOTE) Some attributes are not given arguments in this group but - can be set in other ways. - - To set the project attribute: - ◆ provide the argument CERTIFICATE_AUTHORITY on the command line with a - fully specified name; - ◆ provide the argument --project on the command line; - ◆ set the property core/project. - - This must be specified. - - CERTIFICATE_AUTHORITY - ID of the CERTIFICATE_AUTHORITY or fully qualified identifier for the - CERTIFICATE_AUTHORITY. - - To set the certificate_authority attribute: - ▸ provide the argument CERTIFICATE_AUTHORITY on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --location=LOCATION - The location of the CERTIFICATE_AUTHORITY. - - To set the location attribute: - ▸ provide the argument CERTIFICATE_AUTHORITY on the command line - with a fully specified name; - ▸ provide the argument --location on the command line; - ▸ set the property privateca/location. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -NOTES - This command is currently in beta and might change without notice. This - variant is also available: - - $ gcloud privateca subordinates disable - diff --git a/gcloud/beta/privateca/subordinates/enable b/gcloud/beta/privateca/subordinates/enable deleted file mode 100644 index 3cf0caba8..000000000 --- a/gcloud/beta/privateca/subordinates/enable +++ /dev/null @@ -1,65 +0,0 @@ -NAME - gcloud beta privateca subordinates enable - enable a subordinate - certificate authority - -SYNOPSIS - gcloud beta privateca subordinates enable - (CERTIFICATE_AUTHORITY : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (BETA) Enables a subordinate certificate authority. The subordinate - certificate authority will be allowed to issue certificates once enabled. - -EXAMPLES - To enable a subordinate CA: - - $ gcloud beta privateca subordinates enable server-tls1 \ - --location=us-west1 - -POSITIONAL ARGUMENTS - CERTIFICATE AUTHORITY resource - The certificate authority to enable. The - arguments in this group can be used to specify the attributes of this - resource. (NOTE) Some attributes are not given arguments in this group but - can be set in other ways. - - To set the project attribute: - ◆ provide the argument CERTIFICATE_AUTHORITY on the command line with a - fully specified name; - ◆ provide the argument --project on the command line; - ◆ set the property core/project. - - This must be specified. - - CERTIFICATE_AUTHORITY - ID of the CERTIFICATE_AUTHORITY or fully qualified identifier for the - CERTIFICATE_AUTHORITY. - - To set the certificate_authority attribute: - ▸ provide the argument CERTIFICATE_AUTHORITY on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --location=LOCATION - The location of the CERTIFICATE_AUTHORITY. - - To set the location attribute: - ▸ provide the argument CERTIFICATE_AUTHORITY on the command line - with a fully specified name; - ▸ provide the argument --location on the command line; - ▸ set the property privateca/location. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -NOTES - This command is currently in beta and might change without notice. This - variant is also available: - - $ gcloud privateca subordinates enable - diff --git a/gcloud/beta/privateca/subordinates/get-csr b/gcloud/beta/privateca/subordinates/get-csr deleted file mode 100644 index 51af84cd4..000000000 --- a/gcloud/beta/privateca/subordinates/get-csr +++ /dev/null @@ -1,68 +0,0 @@ -NAME - gcloud beta privateca subordinates get-csr - get the CSR for a subordinate - certificate authority that has not yet been activated - -SYNOPSIS - gcloud beta privateca subordinates get-csr - (CERTIFICATE_AUTHORITY : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (BETA) Gets the PEM-encoded CSR for a subordinate certificate authority - that is pending activation. The CSR should be signed by the issuing - Certificate Authority and uploaded back to the Private CA instance using - the subordinates activate command. - -EXAMPLES - To download the CSR for the 'server-tls-1' CA into a file called - 'server-tls-1.csr': - - $ gcloud beta privateca subordinates get-csr server-tls-1 \ - --location=us > server-tls-1.csr - -POSITIONAL ARGUMENTS - CERTIFICATE AUTHORITY resource - The certificate authority to get csr for. - The arguments in this group can be used to specify the attributes of this - resource. (NOTE) Some attributes are not given arguments in this group but - can be set in other ways. - - To set the project attribute: - ◆ provide the argument CERTIFICATE_AUTHORITY on the command line with a - fully specified name; - ◆ provide the argument --project on the command line; - ◆ set the property core/project. - - This must be specified. - - CERTIFICATE_AUTHORITY - ID of the CERTIFICATE_AUTHORITY or fully qualified identifier for the - CERTIFICATE_AUTHORITY. - - To set the certificate_authority attribute: - ▸ provide the argument CERTIFICATE_AUTHORITY on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --location=LOCATION - The location of the CERTIFICATE_AUTHORITY. - - To set the location attribute: - ▸ provide the argument CERTIFICATE_AUTHORITY on the command line - with a fully specified name; - ▸ provide the argument --location on the command line; - ▸ set the property privateca/location. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -NOTES - This command is currently in beta and might change without notice. This - variant is also available: - - $ gcloud privateca subordinates get-csr - diff --git a/gcloud/beta/privateca/subordinates/get-iam-policy b/gcloud/beta/privateca/subordinates/get-iam-policy deleted file mode 100644 index aac012ceb..000000000 --- a/gcloud/beta/privateca/subordinates/get-iam-policy +++ /dev/null @@ -1,96 +0,0 @@ -NAME - gcloud beta privateca subordinates get-iam-policy - get the IAM policy for - a subordinate Certificate Authority - -SYNOPSIS - gcloud beta privateca subordinates get-iam-policy - (CERTIFICATE_AUTHORITY : --location=LOCATION) [--filter=EXPRESSION] - [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (BETA) Gets the IAM policy for the given subordinate Certificate Authority. - - Returns an empty policy if the resource does not have a policy set. - -EXAMPLES - To get the IAM policy for the CA 'server-tls-1' with the location - 'us-west1', run: - - $ gcloud beta privateca subordinates get-iam-policy server-tls-1 \ - --location=us-west1 - -POSITIONAL ARGUMENTS - Certificate Authority resource - The certificate authority for which to - display the IAM policy. The arguments in this group can be used to specify - the attributes of this resource. (NOTE) Some attributes are not given - arguments in this group but can be set in other ways. - - To set the project attribute: - ◆ provide the argument certificate_authority on the command line with a - fully specified name; - ◆ set the property core/project; - ◆ provide the argument --project on the command line. - - This must be specified. - - CERTIFICATE_AUTHORITY - ID of the Certificate Authority or fully qualified identifier for the - Certificate Authority. - - To set the certificate_authority attribute: - ▸ provide the argument certificate_authority on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --location=LOCATION - The location of the Certificate Authority. - - To set the location attribute: - ▸ provide the argument certificate_authority on the command line - with a fully specified name; - ▸ provide the argument --location on the command line; - ▸ set the property privateca/location. - -LIST COMMAND FLAGS - --filter=EXPRESSION - Apply a Boolean filter EXPRESSION to each resource item to be listed. - If the expression evaluates True, then that item is listed. For more - details and examples of filter expressions, run $ gcloud topic filters. - This flag interacts with other flags that are applied in this order: - --flatten, --sort-by, --filter, --limit. - - --limit=LIMIT - Maximum number of resources to list. The default is unlimited. This - flag interacts with other flags that are applied in this order: - --flatten, --sort-by, --filter, --limit. - - --page-size=PAGE_SIZE - Some services group resource list output into pages. This flag - specifies the maximum number of resources per page. The default is - determined by the service if it supports paging, otherwise it is - unlimited (no paging). Paging may be applied before or after --filter - and --limit depending on the service. - - --sort-by=[FIELD,...] - Comma-separated list of resource field key names to sort by. The - default order is ascending. Prefix a field with ``~'' for descending - order on that field. This flag interacts with other flags that are - applied in this order: --flatten, --sort-by, --filter, --limit. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -API REFERENCE - This command uses the privateca/v1beta1 API. The full documentation for - this API can be found at: https://cloud.google.com/ - -NOTES - This command is currently in beta and might change without notice. - diff --git a/gcloud/beta/privateca/subordinates/help b/gcloud/beta/privateca/subordinates/help deleted file mode 100644 index a3470244a..000000000 --- a/gcloud/beta/privateca/subordinates/help +++ /dev/null @@ -1,68 +0,0 @@ -NAME - gcloud beta privateca subordinates - manage subordinate certificate - authorities - -SYNOPSIS - gcloud beta privateca subordinates COMMAND [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (BETA) Manage subordinate certificate authorities. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --help. - - Run $ gcloud help for details. - -COMMANDS - COMMAND is one of the following: - - activate - (BETA) Activate a subordinate certificate authority in a pending state. - - add-iam-policy-binding - (BETA) Add IAM policy binding for a subordinate Certificate Authority. - - create - (BETA) Create a new subordinate certificate authority. - - delete - (BETA) Schedule a subordinate certificate authority for deletion. - - describe - (BETA) Get metadata for a subordinate Certificate Authority. - - disable - (BETA) Disable a subordinate certificate authority. - - enable - (BETA) Enable a subordinate certificate authority. - - get-csr - (BETA) Get the CSR for a subordinate certificate authority that has not - yet been activated. - - get-iam-policy - (BETA) Get the IAM policy for a subordinate Certificate Authority. - - list - (BETA) List the subordinate certificate authorities within a project. - - remove-iam-policy-binding - (BETA) Remove IAM policy binding for a subordinate Certificate - Authority. - - restore - (BETA) Restore a subordinate Certificate Authority. - - set-iam-policy - (BETA) Set the IAM policy for a subordinate Certificate Authority. - - update - (BETA) Update an existing subordinate certificate authority. - -NOTES - This command is currently in beta and might change without notice. This - variant is also available: - - $ gcloud privateca subordinates - diff --git a/gcloud/beta/privateca/subordinates/list b/gcloud/beta/privateca/subordinates/list deleted file mode 100644 index 89155b023..000000000 --- a/gcloud/beta/privateca/subordinates/list +++ /dev/null @@ -1,54 +0,0 @@ -NAME - gcloud beta privateca subordinates list - list the subordinate certificate - authorities within a project - -SYNOPSIS - gcloud beta privateca subordinates list [--location=LOCATION] - [--limit=LIMIT] [--page-size=PAGE_SIZE; default=100] - [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (BETA) List the subordinate certificate authorities within a project. - -FLAGS - --location=LOCATION - Location of the certificate authorities. - -LIST COMMAND FLAGS - --limit=LIMIT - Maximum number of resources to list. The default is unlimited. This - flag interacts with other flags that are applied in this order: - --flatten, --sort-by, --filter, --limit. - - --page-size=PAGE_SIZE; default=100 - Some services group resource list output into pages. This flag - specifies the maximum number of resources per page. The default is 100. - Paging may be applied before or after --filter and --limit depending on - the service. - - --sort-by=[FIELD,...] - Comma-separated list of resource field key names to sort by. The - default order is ascending. Prefix a field with ``~'' for descending - order on that field. This flag interacts with other flags that are - applied in this order: --flatten, --sort-by, --filter, --limit. - - --uri - Print a list of resource URIs instead of the default output, and change - the command output to a list of URIs. If this flag is used with - --format, the formatting is applied on this URI list. To display URIs - alongside other keys instead, use the uri() transform. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -NOTES - This command is currently in beta and might change without notice. This - variant is also available: - - $ gcloud privateca subordinates list - diff --git a/gcloud/beta/privateca/subordinates/remove-iam-policy-binding b/gcloud/beta/privateca/subordinates/remove-iam-policy-binding deleted file mode 100644 index 4a4a1c559..000000000 --- a/gcloud/beta/privateca/subordinates/remove-iam-policy-binding +++ /dev/null @@ -1,96 +0,0 @@ -NAME - gcloud beta privateca subordinates remove-iam-policy-binding - remove IAM - policy binding for a subordinate Certificate Authority - -SYNOPSIS - gcloud beta privateca subordinates remove-iam-policy-binding - (CERTIFICATE_AUTHORITY : --location=LOCATION) --member=PRINCIPAL - --role=ROLE [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (BETA) Removes a policy binding from the IAM policy of a subordinate - Certificate Authority. One binding consists of a member and a role. - - See https://cloud.google.com/iam/docs/managing-policies for details of - policy role and member types. - -EXAMPLES - To remove an IAM policy binding for the role of - 'roles/privateca.certificateManager' for the user 'test-user@gmail.com' on - 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' - -POSITIONAL ARGUMENTS - Certificate Authority resource - The certificate authority for which to - update the IAM policy. The arguments in this group can be used to specify - the attributes of this resource. (NOTE) Some attributes are not given - arguments in this group but can be set in other ways. - - To set the project attribute: - ◆ provide the argument certificate_authority on the command line with a - fully specified name; - ◆ set the property core/project; - ◆ provide the argument --project on the command line. - - This must be specified. - - CERTIFICATE_AUTHORITY - ID of the Certificate Authority or fully qualified identifier for the - Certificate Authority. - - To set the certificate_authority attribute: - ▸ provide the argument certificate_authority on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --location=LOCATION - The location of the Certificate Authority. - - To set the location attribute: - ▸ provide the argument certificate_authority on the command line - with a fully specified name; - ▸ provide the argument --location on the command line; - ▸ set the property privateca/location. - -REQUIRED FLAGS - --member=PRINCIPAL - The principal to remove the binding for. Should be of the form - user|group|serviceAccount:email or domain:domain. - - Examples: user:test-user@gmail.com, group:admins@example.com, - serviceAccount:test123@example.domain.com, or - domain:example.domain.com. - - Deleted principals have an additional deleted: prefix and a ?uid=UID - suffix, where UID is a unique identifier for the principal. Example: - deleted:user:test-user@gmail.com?uid=123456789012345678901. - - Some resources also accept the following special values: - ◆ allUsers - Special identifier that represents anyone who is on the - internet, with or without a Google account. - ◆ allAuthenticatedUsers - Special identifier that represents anyone - who is authenticated with a Google account or a service account. - - --role=ROLE - The role to remove the principal from. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -API REFERENCE - This command uses the privateca/v1beta1 API. The full documentation for - this API can be found at: https://cloud.google.com/ - -NOTES - This command is currently in beta and might change without notice. - diff --git a/gcloud/beta/privateca/subordinates/restore b/gcloud/beta/privateca/subordinates/restore deleted file mode 100644 index 49e68686c..000000000 --- a/gcloud/beta/privateca/subordinates/restore +++ /dev/null @@ -1,64 +0,0 @@ -NAME - gcloud beta privateca subordinates restore - restore a subordinate - Certificate Authority - -SYNOPSIS - gcloud beta privateca subordinates restore - (CERTIFICATE_AUTHORITY : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (BETA) Restores a subordinate Certificate Authority that has been marked - for deletion. A Certificate Authority can be restored within 30 days of - being scheduled for deletion. Use this command to halt the deletion - process. A restored CA will move to DISABLED state. - -EXAMPLES - To restore a subordinate CA: - - $ gcloud beta privateca subordinates restore server-tls-1 \ - --location=us-west1 - -POSITIONAL ARGUMENTS - CERTIFICATE AUTHORITY resource - The certificate authority to restore. The - arguments in this group can be used to specify the attributes of this - resource. (NOTE) Some attributes are not given arguments in this group but - can be set in other ways. - - To set the project attribute: - ◆ provide the argument CERTIFICATE_AUTHORITY on the command line with a - fully specified name; - ◆ provide the argument --project on the command line; - ◆ set the property core/project. - - This must be specified. - - CERTIFICATE_AUTHORITY - ID of the CERTIFICATE_AUTHORITY or fully qualified identifier for the - CERTIFICATE_AUTHORITY. - - To set the certificate_authority attribute: - ▸ provide the argument CERTIFICATE_AUTHORITY on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --location=LOCATION - The location of the CERTIFICATE_AUTHORITY. - - To set the location attribute: - ▸ provide the argument CERTIFICATE_AUTHORITY on the command line - with a fully specified name; - ▸ provide the argument --location on the command line; - ▸ set the property privateca/location. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -NOTES - This command is currently in beta and might change without notice. - diff --git a/gcloud/beta/privateca/subordinates/set-iam-policy b/gcloud/beta/privateca/subordinates/set-iam-policy deleted file mode 100644 index c18b18e21..000000000 --- a/gcloud/beta/privateca/subordinates/set-iam-policy +++ /dev/null @@ -1,79 +0,0 @@ -NAME - gcloud beta privateca subordinates set-iam-policy - set the IAM policy for - a subordinate Certificate Authority - -SYNOPSIS - gcloud beta privateca subordinates set-iam-policy - (CERTIFICATE_AUTHORITY : --location=LOCATION) POLICY_FILE - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (BETA) Sets the IAM policy for the given subordinate Certificate Authority - 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 am IAM policy defined in a JSON file - 'policy.json' and set it for the CA 'server-tls-1' with the location - 'us-west1': - - $ gcloud beta privateca subordinates set-iam-policy server-tls-1 \ - policy.json --location=us-west1 - -POSITIONAL ARGUMENTS - Certificate Authority resource - The certificate authority for which to - update the IAM policy. The arguments in this group can be used to specify - the attributes of this resource. (NOTE) Some attributes are not given - arguments in this group but can be set in other ways. - - To set the project attribute: - ◆ provide the argument certificate_authority on the command line with a - fully specified name; - ◆ set the property core/project; - ◆ provide the argument --project on the command line. - - This must be specified. - - CERTIFICATE_AUTHORITY - ID of the Certificate Authority or fully qualified identifier for the - Certificate Authority. - - To set the certificate_authority attribute: - ▸ provide the argument certificate_authority on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --location=LOCATION - The location of the Certificate Authority. - - To set the location attribute: - ▸ provide the argument certificate_authority on the command line - with a fully specified name; - ▸ provide the argument --location on the command line; - ▸ set the property privateca/location. - - POLICY_FILE - Path to a local JSON or YAML formatted file containing a valid policy. - - The output of the get-iam-policy command is a valid file, as is any - JSON or YAML file conforming to the structure of a Policy - (https://cloud.google.com/iam/reference/rest/v1/Policy). - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -API REFERENCE - This command uses the privateca/v1beta1 API. The full documentation for - this API can be found at: https://cloud.google.com/ - -NOTES - This command is currently in beta and might change without notice. - diff --git a/gcloud/beta/privateca/subordinates/update b/gcloud/beta/privateca/subordinates/update deleted file mode 100644 index bbcdf8b96..000000000 --- a/gcloud/beta/privateca/subordinates/update +++ /dev/null @@ -1,142 +0,0 @@ -NAME - gcloud beta privateca subordinates update - update an existing subordinate - certificate authority - -SYNOPSIS - gcloud beta privateca subordinates update - (CERTIFICATE_AUTHORITY : --location=LOCATION) - [--issuance-policy=ISSUANCE_POLICY] [--pem-chain=PEM_CHAIN] - [--no-publish-ca-cert] [--no-publish-crl] - [--update-labels=[KEY=VALUE,...]] - [--clear-labels | --remove-labels=[KEY,...]] [GCLOUD_WIDE_FLAG ...] - -EXAMPLES - To update labels on a subordinate CA: - - $ gcloud beta privateca subordinates update server-tls-1 \ - --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 - -POSITIONAL ARGUMENTS - CERTIFICATE AUTHORITY resource - The certificate authority to update. The - arguments in this group can be used to specify the attributes of this - resource. (NOTE) Some attributes are not given arguments in this group but - can be set in other ways. - - To set the project attribute: - ◆ provide the argument CERTIFICATE_AUTHORITY on the command line with a - fully specified name; - ◆ provide the argument --project on the command line; - ◆ set the property core/project. - - This must be specified. - - CERTIFICATE_AUTHORITY - ID of the CERTIFICATE_AUTHORITY or fully qualified identifier for the - CERTIFICATE_AUTHORITY. - - To set the certificate_authority attribute: - ▸ provide the argument CERTIFICATE_AUTHORITY on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --location=LOCATION - The location of the CERTIFICATE_AUTHORITY. - - To set the location attribute: - ▸ provide the argument CERTIFICATE_AUTHORITY on the command line - with a fully specified name; - ▸ provide the argument --location on the command line; - ▸ set the property privateca/location. - -FLAGS - --issuance-policy=ISSUANCE_POLICY - A YAML file describing this Certificate Authority's issuance policy. - - --pem-chain=PEM_CHAIN - A file containing a list of PEM-encoded certificates that represent the - issuing chain of this CA. - - --publish-ca-cert - If this is enabled, the following will happen: 1) The CA certificate - will be written to a known location within the CA distribution point. - 2) The AIA extension in all issued certificates will point to the CA - cert URL in that distribution point. - - If this gets disabled, the AIA extension will not be written to any - future certificates issued by this CA. However, an existing bucket will - not be deleted, and the CA certificate will not be removed from that - bucket. - - Note that the same bucket may be used for the CRLs if --publish-crl is - set. - - Enabled by default, use --no-publish-ca-cert to disable. - - --publish-crl - If this gets enabled, the following will happen: 1) CRLs will be - written to a known location within the CA distribution point. 2) The - CDP extension in all future issued certificates will point to the CRL - URL in that distribution point. - - If this gets disabled, the CDP extension will not be written to any - future certificates issued by this CA, and new CRLs will not be - published to that bucket (which affects existing certs). However, an - existing bucket will not be deleted, and any existing CRLs will not be - removed from that bucket. - - Note that the same bucket may be used for the CA cert if - --publish-ca-cert is set. - - CRL publication is not supported for CAs in the DevOps tier. - - Enabled by default, use --no-publish-crl to disable. - - --update-labels=[KEY=VALUE,...] - List of label KEY=VALUE pairs to update. If a label exists, its value - is modified. Otherwise, a new label is created. - - Keys must start with a lowercase character and contain only hyphens - (-), underscores (_), lowercase characters, and numbers. Values must - contain only hyphens (-), underscores (_), lowercase characters, and - numbers. - - At most one of these can be specified: - - --clear-labels - Remove all labels. If --update-labels is also specified then - --clear-labels is applied first. - - For example, to remove all labels: - - $ gcloud beta privateca subordinates update --clear-labels - - To remove all existing labels and create two new labels, foo and baz: - - $ gcloud beta privateca subordinates update --clear-labels \ - --update-labels foo=bar,baz=qux - - --remove-labels=[KEY,...] - List of label keys to remove. If a label does not exist it is - silently ignored. If --update-labels is also specified then - --update-labels is applied first. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -NOTES - This command is currently in beta and might change without notice. This - variant is also available: - - $ gcloud privateca subordinates update - diff --git a/gcloud/beta/run/deploy b/gcloud/beta/run/deploy index d55752f72..7ad9d0ff3 100644 --- a/gcloud/beta/run/deploy +++ b/gcloud/beta/run/deploy @@ -9,11 +9,12 @@ SYNOPSIS [--platform=PLATFORM; default="managed"] [--service-account=SERVICE_ACCOUNT] [--tag=TAG] [--timeout=TIMEOUT] [--no-traffic] - [--args=[ARG,...] --command=[COMMAND,...] --cpu=CPU - --depends-on=[CONTAINER,...] - --memory=MEMORY --port=PORT --[no-]use-http2 --clear-env-vars - | --env-vars-file=FILE_PATH | --set-env-vars=[KEY=VALUE,...] - | --remove-env-vars=[KEY,...] + [--add-volume-mount=[volume=NAME,mount-path=MOUNT_PATH,...] + --args=[ARG,...] --clear-volume-mounts --command=[COMMAND,...] + --cpu=CPU --depends-on=[CONTAINER,...] --memory=MEMORY --port=PORT + --remove-volume-mount=[MOUNT_PATH,...] + --[no-]use-http2 --clear-env-vars | --env-vars-file=FILE_PATH + | --set-env-vars=[KEY=VALUE,...] | --remove-env-vars=[KEY,...] --update-env-vars=[KEY=VALUE,...] --clear-secrets | --set-secrets=[KEY=VALUE,...] | --remove-secrets=[KEY,...] --update-secrets=[KEY=VALUE,...] --image=IMAGE | --source=SOURCE] @@ -37,7 +38,8 @@ SYNOPSIS | --clear-custom-audiences | --remove-custom-audiences=[CUSTOM-AUDIENCES,...] | --set-custom-audiences=[CUSTOM-AUDIENCES,...] - --binary-authorization=POLICY + --add-volume=[KEY=VALUE,...] --clear-volumes + --remove-volume=[VOLUME,...] --binary-authorization=POLICY | --clear-binary-authorization --clear-encryption-key-shutdown-hours | --encryption-key-shutdown-hours=ENCRYPTION_KEY_SHUTDOWN_HOURS --clear-key | --key=KEY --clear-network @@ -192,6 +194,12 @@ FLAGS The following flags apply to a single container. If the --container flag is specified these flags may only be specified after a --container flag. Otherwise they will apply to the primary ingress container. + --add-volume-mount=[volume=NAME,mount-path=MOUNT_PATH,...] + Adds a mount to the current container. Must contain the keys + volume=NAME and mount-path=/PATH where NAME is the name of a volume + on this resource and PATH is the path within the container's + filesystem to mount this volume. + --args=[ARG,...] Comma-separated arguments passed to the command run by the container image. If not specified and no '--command' is provided, @@ -199,6 +207,9 @@ FLAGS specified, no arguments are passed. To reset this field to its default, pass an empty string. + --clear-volume-mounts + Remove all existing mounts from the current container. + --command=[COMMAND,...] Entrypoint for the container image. If not specified, the container image's default Entrypoint is run. To reset this field to its @@ -228,6 +239,10 @@ FLAGS to the previous container port, this will also update the probe port. + --remove-volume-mount=[MOUNT_PATH,...] + Removes the volume mounted at the specified path from the current + container. + --[no-]use-http2 Whether to use HTTP/2 for connections to the service. Use --use-http2 to enable and --no-use-http2 to disable. @@ -509,6 +524,39 @@ FLAGS Completely replace the current custom audiences with the given values. + --add-volume=[KEY=VALUE,...] + Adds a volume to the Cloud Run resource. To add more than one volume, + specify this flag mulitple times. Volumes must have a name and type + key. Only certain values are supported for type. Depending on the + provided type, other keys will be required. The following types are + supported with the specified additional keys: + + cloud-storage: A volume representing a Cloud Storage bucket. This + volume type is mounted using Cloud Storage FUSE. See + https://cloud.google.com/storage/docs/gcs-fuse for the details and + limitations of this filesystem. Additional keys: + ◆ bucket: (required) the name of the bucket to use as the source of + this volume + ◆ readonly: (optional) A boolean. If true, this volume will be + read-only from all mounts. + + in-memory: An ephemeral volume that stores data in the instance's memory. + With this type of volume, data is not shared between instances and all + data will be lost when the instance it is on is terminated. Additional + keys: + ◆ size-limit: (optional) A quantity representing the maximum amount of + memory allocated to this volume, such as "512Mi" or "3G". Data stored + in an in-memory volume consumes the memory allocation of the container + that wrote the data. If size-limit is not specified, the maximum size + will be half the total memory limit of all containers. + + --clear-volumes + Remove all existing volumes from the Cloud Run resource, including + volumes mounted as secrets + + --remove-volume=[VOLUME,...] + Removes volumes from the Cloud Run resource. + At most one of these can be specified: --binary-authorization=POLICY diff --git a/gcloud/beta/run/jobs/deploy b/gcloud/beta/run/jobs/deploy index 2a65be9dc..389677f4c 100644 --- a/gcloud/beta/run/jobs/deploy +++ b/gcloud/beta/run/jobs/deploy @@ -12,6 +12,10 @@ SYNOPSIS [--set-secrets=[KEY=SECRET_NAME:SECRET_VERSION,...]] [--task-timeout=TASK_TIMEOUT] [--tasks=TASKS; default=1] [--vpc-connector=VPC_CONNECTOR] [--vpc-egress=VPC_EGRESS] + [--add-volume=[KEY=VALUE,...] + --clear-volumes --remove-volume=[VOLUME,...]] + [--add-volume-mount=[volume=NAME,mount-path=MOUNT_PATH,...] + --clear-volume-mounts --remove-volume-mount=[MOUNT_PATH,...]] [--async | --execute-now --wait] [--clear-env-vars | --env-vars-file=FILE_PATH | --set-env-vars=[KEY=VALUE,...] @@ -163,6 +167,52 @@ FLAGS https://cloud.google.com/run/docs/securing/private-networking#send_requests_to_other_services_and_services for more information. + --add-volume=[KEY=VALUE,...] + Adds a volume to the Cloud Run resource. To add more than one volume, + specify this flag mulitple times. Volumes must have a name and type + key. Only certain values are supported for type. Depending on the + provided type, other keys will be required. The following types are + supported with the specified additional keys: + + cloud-storage: A volume representing a Cloud Storage bucket. This + volume type is mounted using Cloud Storage FUSE. See + https://cloud.google.com/storage/docs/gcs-fuse for the details and + limitations of this filesystem. Additional keys: + ◆ bucket: (required) the name of the bucket to use as the source of + this volume + ◆ readonly: (optional) A boolean. If true, this volume will be + read-only from all mounts. + + in-memory: An ephemeral volume that stores data in the instance's + memory. With this type of volume, data is not shared between instances + and all data will be lost when the instance it is on is terminated. + Additional keys: + ◆ size-limit: (optional) A quantity representing the maximum amount + of memory allocated to this volume, such as "512Mi" or "3G". Data + stored in an in-memory volume consumes the memory allocation of the + container that wrote the data. If size-limit is not specified, the + maximum size will be half the total memory limit of all containers. + + --clear-volumes + Remove all existing volumes from the Cloud Run resource, including + volumes mounted as secrets + + --remove-volume=[VOLUME,...] + Removes volumes from the Cloud Run resource. + + --add-volume-mount=[volume=NAME,mount-path=MOUNT_PATH,...] + Adds a mount to the current container. Must contain the keys + volume=NAME and mount-path=/PATH where NAME is the name of a volume on + this resource and PATH is the path within the container's filesystem to + mount this volume. + + --clear-volume-mounts + Remove all existing mounts from the current container. + + --remove-volume-mount=[MOUNT_PATH,...] + Removes the volume mounted at the specified path from the current + container. + At most one of these can be specified: --async diff --git a/gcloud/beta/run/jobs/update b/gcloud/beta/run/jobs/update index ded41616c..a7eedcf5f 100644 --- a/gcloud/beta/run/jobs/update +++ b/gcloud/beta/run/jobs/update @@ -14,6 +14,10 @@ SYNOPSIS | --clear-cloudsql-instances | --remove-cloudsql-instances=[CLOUDSQL-INSTANCES,...] | --set-cloudsql-instances=[CLOUDSQL-INSTANCES,...]] + [--add-volume=[KEY=VALUE,...] + --clear-volumes --remove-volume=[VOLUME,...]] + [--add-volume-mount=[volume=NAME,mount-path=MOUNT_PATH,...] + --clear-volume-mounts --remove-volume-mount=[MOUNT_PATH,...]] [--async | --execute-now --wait] [--binary-authorization=POLICY | --clear-binary-authorization] [--clear-env-vars | --env-vars-file=FILE_PATH @@ -173,6 +177,52 @@ FLAGS Completely replace the current Cloud SQL instances with the given values. + --add-volume=[KEY=VALUE,...] + Adds a volume to the Cloud Run resource. To add more than one volume, + specify this flag mulitple times. Volumes must have a name and type + key. Only certain values are supported for type. Depending on the + provided type, other keys will be required. The following types are + supported with the specified additional keys: + + cloud-storage: A volume representing a Cloud Storage bucket. This + volume type is mounted using Cloud Storage FUSE. See + https://cloud.google.com/storage/docs/gcs-fuse for the details and + limitations of this filesystem. Additional keys: + ◆ bucket: (required) the name of the bucket to use as the source of + this volume + ◆ readonly: (optional) A boolean. If true, this volume will be + read-only from all mounts. + + in-memory: An ephemeral volume that stores data in the instance's + memory. With this type of volume, data is not shared between instances + and all data will be lost when the instance it is on is terminated. + Additional keys: + ◆ size-limit: (optional) A quantity representing the maximum amount + of memory allocated to this volume, such as "512Mi" or "3G". Data + stored in an in-memory volume consumes the memory allocation of the + container that wrote the data. If size-limit is not specified, the + maximum size will be half the total memory limit of all containers. + + --clear-volumes + Remove all existing volumes from the Cloud Run resource, including + volumes mounted as secrets + + --remove-volume=[VOLUME,...] + Removes volumes from the Cloud Run resource. + + --add-volume-mount=[volume=NAME,mount-path=MOUNT_PATH,...] + Adds a mount to the current container. Must contain the keys + volume=NAME and mount-path=/PATH where NAME is the name of a volume on + this resource and PATH is the path within the container's filesystem to + mount this volume. + + --clear-volume-mounts + Remove all existing mounts from the current container. + + --remove-volume-mount=[MOUNT_PATH,...] + Removes the volume mounted at the specified path from the current + container. + At most one of these can be specified: --async diff --git a/gcloud/beta/run/services/update b/gcloud/beta/run/services/update index df6dfd655..081818198 100644 --- a/gcloud/beta/run/services/update +++ b/gcloud/beta/run/services/update @@ -10,11 +10,12 @@ SYNOPSIS [--platform=PLATFORM; default="managed"] [--service-account=SERVICE_ACCOUNT] [--tag=TAG] [--timeout=TIMEOUT] [--no-traffic] - [--args=[ARG,...] --command=[COMMAND,...] --cpu=CPU - --depends-on=[CONTAINER,...] --image=IMAGE - --memory=MEMORY --port=PORT --[no-]use-http2 --clear-env-vars - | --env-vars-file=FILE_PATH | --set-env-vars=[KEY=VALUE,...] - | --remove-env-vars=[KEY,...] + [--add-volume-mount=[volume=NAME,mount-path=MOUNT_PATH,...] + --args=[ARG,...] --clear-volume-mounts --command=[COMMAND,...] + --cpu=CPU --depends-on=[CONTAINER,...] --image=IMAGE --memory=MEMORY + --port=PORT --remove-volume-mount=[MOUNT_PATH,...] + --[no-]use-http2 --clear-env-vars | --env-vars-file=FILE_PATH + | --set-env-vars=[KEY=VALUE,...] | --remove-env-vars=[KEY,...] --update-env-vars=[KEY=VALUE,...] --clear-secrets | --set-secrets=[KEY=VALUE,...] | --remove-secrets=[KEY,...] --update-secrets=[KEY=VALUE,...]] @@ -31,7 +32,8 @@ SYNOPSIS | --clear-custom-audiences | --remove-custom-audiences=[CUSTOM-AUDIENCES,...] | --set-custom-audiences=[CUSTOM-AUDIENCES,...] - --binary-authorization=POLICY + --add-volume=[KEY=VALUE,...] --clear-volumes + --remove-volume=[VOLUME,...] --binary-authorization=POLICY | --clear-binary-authorization --clear-encryption-key-shutdown-hours | --encryption-key-shutdown-hours=ENCRYPTION_KEY_SHUTDOWN_HOURS --clear-key | --key=KEY --clear-network @@ -180,6 +182,12 @@ FLAGS If the --container or --remove-containers flag is specified the following arguments may only be specified after a --container flag. + --add-volume-mount=[volume=NAME,mount-path=MOUNT_PATH,...] + Adds a mount to the current container. Must contain the keys + volume=NAME and mount-path=/PATH where NAME is the name of a volume + on this resource and PATH is the path within the container's + filesystem to mount this volume. + --args=[ARG,...] Comma-separated arguments passed to the command run by the container image. If not specified and no '--command' is provided, @@ -187,6 +195,9 @@ FLAGS specified, no arguments are passed. To reset this field to its default, pass an empty string. + --clear-volume-mounts + Remove all existing mounts from the current container. + --command=[COMMAND,...] Entrypoint for the container image. If not specified, the container image's default Entrypoint is run. To reset this field to its @@ -220,6 +231,10 @@ FLAGS to the previous container port, this will also update the probe port. + --remove-volume-mount=[MOUNT_PATH,...] + Removes the volume mounted at the specified path from the current + container. + --[no-]use-http2 Whether to use HTTP/2 for connections to the service. Use --use-http2 to enable and --no-use-http2 to disable. @@ -389,6 +404,39 @@ FLAGS Completely replace the current custom audiences with the given values. + --add-volume=[KEY=VALUE,...] + Adds a volume to the Cloud Run resource. To add more than one volume, + specify this flag mulitple times. Volumes must have a name and type + key. Only certain values are supported for type. Depending on the + provided type, other keys will be required. The following types are + supported with the specified additional keys: + + cloud-storage: A volume representing a Cloud Storage bucket. This + volume type is mounted using Cloud Storage FUSE. See + https://cloud.google.com/storage/docs/gcs-fuse for the details and + limitations of this filesystem. Additional keys: + ◆ bucket: (required) the name of the bucket to use as the source of + this volume + ◆ readonly: (optional) A boolean. If true, this volume will be + read-only from all mounts. + + in-memory: An ephemeral volume that stores data in the instance's memory. + With this type of volume, data is not shared between instances and all + data will be lost when the instance it is on is terminated. Additional + keys: + ◆ size-limit: (optional) A quantity representing the maximum amount of + memory allocated to this volume, such as "512Mi" or "3G". Data stored + in an in-memory volume consumes the memory allocation of the container + that wrote the data. If size-limit is not specified, the maximum size + will be half the total memory limit of all containers. + + --clear-volumes + Remove all existing volumes from the Cloud Run resource, including + volumes mounted as secrets + + --remove-volume=[VOLUME,...] + Removes volumes from the Cloud Run resource. + At most one of these can be specified: --binary-authorization=POLICY diff --git a/gcloud/beta/services/vpc-peerings/get-vpc-service-controls b/gcloud/beta/services/vpc-peerings/get-vpc-service-controls index d64def9e8..62e38b030 100644 --- a/gcloud/beta/services/vpc-peerings/get-vpc-service-controls +++ b/gcloud/beta/services/vpc-peerings/get-vpc-service-controls @@ -62,8 +62,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud services vpc-peerings get-vpc-service-controls $ gcloud alpha services vpc-peerings get-vpc-service-controls diff --git a/gcloud/beta/sql/backups/restore b/gcloud/beta/sql/backups/restore index ab3cbf7a3..84c278994 100644 --- a/gcloud/beta/sql/backups/restore +++ b/gcloud/beta/sql/backups/restore @@ -2,15 +2,14 @@ NAME gcloud beta sql backups restore - restores a backup of a Cloud SQL instance SYNOPSIS - gcloud beta sql backups restore BACKUP_ID - --restore-instance=RESTORE_INSTANCE [--async] - [--backup-instance=BACKUP_INSTANCE] [GCLOUD_WIDE_FLAG ...] + gcloud beta sql backups restore ID --restore-instance=RESTORE_INSTANCE + [--async] [--backup-instance=BACKUP_INSTANCE] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Restores a backup of a Cloud SQL instance. POSITIONAL ARGUMENTS - BACKUP_ID + ID The ID of the backup run to restore from. REQUIRED FLAGS diff --git a/gcloud/beta/sql/instances/create b/gcloud/beta/sql/instances/create index d0e335c3f..c33b71766 100644 --- a/gcloud/beta/sql/instances/create +++ b/gcloud/beta/sql/instances/create @@ -36,7 +36,6 @@ SYNOPSIS [--master-instance-name=MASTER_INSTANCE_NAME] [--memory=MEMORY] [--network=NETWORK] [--password-policy-complexity=PASSWORD_POLICY_COMPLEXITY] - [--[no-]password-policy-disallow-compromised-credentials] [--[no-]password-policy-disallow-username-substring] [--password-policy-min-length=PASSWORD_POLICY_MIN_LENGTH] [--password-policy-password-change-interval=PASSWORD_POLICY_PASSWORD_CHANGE_INTERVAL] @@ -352,12 +351,6 @@ FLAGS The default value if COMPLEXITY_DEFAULT is not specified. It implies that complexity check is not enabled. - --[no-]password-policy-disallow-compromised-credentials - Prohibits the use of credentials that have been compromised by a data - breach. Use --password-policy-disallow-compromised-credentials to - enable and --no-password-policy-disallow-compromised-credentials to - disable. - --[no-]password-policy-disallow-username-substring Disallow username as a part of the password. Use --password-policy-disallow-username-substring to enable and diff --git a/gcloud/beta/sql/instances/patch b/gcloud/beta/sql/instances/patch index c38239920..68dd3f069 100644 --- a/gcloud/beta/sql/instances/patch +++ b/gcloud/beta/sql/instances/patch @@ -31,7 +31,6 @@ SYNOPSIS [--maintenance-window-hour=MAINTENANCE_WINDOW_HOUR] [--memory=MEMORY] [--network=NETWORK] [--password-policy-complexity=PASSWORD_POLICY_COMPLEXITY] - [--[no-]password-policy-disallow-compromised-credentials] [--[no-]password-policy-disallow-username-substring] [--password-policy-min-length=PASSWORD_POLICY_MIN_LENGTH] [--password-policy-password-change-interval=PASSWORD_POLICY_PASSWORD_CHANGE_INTERVAL] @@ -292,12 +291,6 @@ FLAGS The default value if COMPLEXITY_DEFAULT is not specified. It implies that complexity check is not enabled. - --[no-]password-policy-disallow-compromised-credentials - Prohibits the use of credentials that have been compromised by a data - breach. Use --password-policy-disallow-compromised-credentials to - enable and --no-password-policy-disallow-compromised-credentials to - disable. - --[no-]password-policy-disallow-username-substring Disallow username as a part of the password. Use --password-policy-disallow-username-substring to enable and diff --git a/gcloud/builds/worker-pools/create b/gcloud/builds/worker-pools/create index d784e3e24..61344fe72 100644 --- a/gcloud/builds/worker-pools/create +++ b/gcloud/builds/worker-pools/create @@ -1,6 +1,6 @@ NAME - gcloud builds worker-pools create - create a worker pool for use by Cloud - Build + gcloud builds worker-pools create - create a worker pool for use by Google + Cloud Build SYNOPSIS gcloud builds worker-pools create WORKER_POOL --region=REGION @@ -10,7 +10,7 @@ SYNOPSIS --worker-machine-type=WORKER_MACHINE_TYPE] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - Create a worker pool for use by Cloud Build. + Create a worker pool for use by Google Cloud Build. EXAMPLES To create a worker pool named wp1 in region us-central1, run: diff --git a/gcloud/builds/worker-pools/help b/gcloud/builds/worker-pools/help index 3cf00607c..300d9b0be 100644 --- a/gcloud/builds/worker-pools/help +++ b/gcloud/builds/worker-pools/help @@ -16,7 +16,7 @@ COMMANDS COMMAND is one of the following: create - Create a worker pool for use by Cloud Build. + Create a worker pool for use by Google Cloud Build. delete Delete a worker pool from Cloud Build. diff --git a/gcloud/composer/environments/create b/gcloud/composer/environments/create index 60de0cf59..7a502d2ef 100644 --- a/gcloud/composer/environments/create +++ b/gcloud/composer/environments/create @@ -7,7 +7,8 @@ SYNOPSIS [--airflow-configs=[KEY=VALUE,...]] [--async] [--cloud-sql-machine-type=CLOUD_SQL_MACHINE_TYPE] [--cloud-sql-preferred-zone=CLOUD_SQL_PREFERRED_ZONE] - [--disk-size=DISK_SIZE] [--enable-high-resilience] + [--disable-logs-in-cloud-logging-only] [--disk-size=DISK_SIZE] + [--enable-high-resilience] [--enable-logs-in-cloud-logging-only] [--env-variables=[NAME=VALUE,...]] [--environment-size=ENVIRONMENT_SIZE] [--labels=[KEY=VALUE,...]] [--machine-type=MACHINE_TYPE] [--node-count=NODE_COUNT] @@ -123,6 +124,10 @@ FLAGS --cloud-sql-preferred-zone=CLOUD_SQL_PREFERRED_ZONE Select cloud sql preferred zone, supported for Composer 2 Environments. + --disable-logs-in-cloud-logging-only + Disable logs in cloud logging only, supported for Composer 2 + Environments. + --disk-size=DISK_SIZE The disk size for each VM node in the environment. The minimum size is 20GB, and the maximum is 64TB. Specified value must be an integer @@ -132,6 +137,10 @@ FLAGS --enable-high-resilience Enable high resilience, supported for Composer 2 Environments. + --enable-logs-in-cloud-logging-only + Enable logs in cloud logging only, supported for Composer 2 + Environments. + --env-variables=[NAME=VALUE,...] A comma-delimited list of environment variable NAME=VALUE pairs to provide to the Airflow scheduler, worker, and webserver processes. NAME diff --git a/gcloud/composer/environments/update b/gcloud/composer/environments/update index 10d6fa221..875ceadbc 100644 --- a/gcloud/composer/environments/update +++ b/gcloud/composer/environments/update @@ -5,7 +5,8 @@ NAME SYNOPSIS gcloud composer environments update (ENVIRONMENT : --location=LOCATION) (--cloud-sql-machine-type=CLOUD_SQL_MACHINE_TYPE - | --disable-high-resilience | --enable-high-resilience + | --disable-high-resilience | --disable-logs-in-cloud-logging-only + | --enable-high-resilience | --enable-logs-in-cloud-logging-only | --environment-size=ENVIRONMENT_SIZE | --node-count=NODE_COUNT | --web-server-machine-type=WEB_SERVER_MACHINE_TYPE | --disable-master-authorized-networks @@ -99,9 +100,17 @@ REQUIRED FLAGS --disable-high-resilience Disable high resilience, supported for Composer 2 Environments. + --disable-logs-in-cloud-logging-only + Disable logs in cloud logging only, supported for Composer 2 + Environments. + --enable-high-resilience Enable high resilience, supported for Composer 2 Environments. + --enable-logs-in-cloud-logging-only + Enable logs in cloud logging only, supported for Composer 2 + Environments. + --environment-size=ENVIRONMENT_SIZE Size of the environment. Unspecified means that the default option will be chosen. ENVIRONMENT_SIZE must be one of: large, medium, diff --git a/gcloud/compute/copy-files b/gcloud/compute/copy-files index 1870bd992..40aeb7013 100644 --- a/gcloud/compute/copy-files +++ b/gcloud/compute/copy-files @@ -11,10 +11,6 @@ SYNOPSIS | --ssh-key-expire-after=SSH_KEY_EXPIRE_AFTER] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (DEPRECATED) gcloud compute copy-files is deprecated. Please use gcloud - compute scp instead. Note that gcloud compute scp does not have recursive - copy on by default. To turn on recursion, use the --recurse flag. - gcloud compute copy-files copies files between a virtual machine instance and your local machine using the scp command. This command does not work for Windows VMs. diff --git a/gcloud/compute/help b/gcloud/compute/help index 660313e05..1c5b2327d 100644 --- a/gcloud/compute/help +++ b/gcloud/compute/help @@ -214,8 +214,7 @@ COMMANDS Connect to the serial port of an instance. copy-files - (DEPRECATED) Copy files to and from Google Compute Engine virtual - machines via scp. + Copy files to and from Google Compute Engine virtual machines via scp. reset-windows-password Reset and return a password for a Windows machine instance. diff --git a/gcloud/compute/instance-templates/create b/gcloud/compute/instance-templates/create index 9babddc4c..3230ba0df 100644 --- a/gcloud/compute/instance-templates/create +++ b/gcloud/compute/instance-templates/create @@ -602,13 +602,13 @@ FLAGS --aliases="10.128.1.0/24;range1:/32" - Each IP alias range consists of a range name and a CIDR netmask - (e.g. `/24`) separated by a colon or just the netmask. - The range name is the name of the range within the network - interface's subnet from which to allocate an IP alias range. If - unspecified, it defaults to the primary IP range of the subnet. - The IP allocator will pick an available range with the specified - netmask and allocate it to this network interface. + Each IP alias range consists of a range name and a CIDR netmask + (e.g. /24) separated by a colon or just the netmask. The range name + is the name of the range within the network interface's subnet from + which to allocate an IP alias range. If unspecified, it defaults to + the primary IP range of the subnet. The IP allocator will pick an + available range with the specified netmask and allocate it to this + network interface. --network-performance-configs=[PROPERTY=VALUE,...] Configures network performance settings for the instance. If this flag diff --git a/gcloud/compute/instance-templates/create-with-container b/gcloud/compute/instance-templates/create-with-container index bc64ace61..f745b1e1e 100644 --- a/gcloud/compute/instance-templates/create-with-container +++ b/gcloud/compute/instance-templates/create-with-container @@ -521,13 +521,13 @@ FLAGS --aliases="10.128.1.0/24;range1:/32" - Each IP alias range consists of a range name and a CIDR netmask - (e.g. `/24`) separated by a colon or just the netmask. - The range name is the name of the range within the network - interface's subnet from which to allocate an IP alias range. If - unspecified, it defaults to the primary IP range of the subnet. - The IP allocator will pick an available range with the specified - netmask and allocate it to this network interface. + Each IP alias range consists of a range name and a CIDR netmask + (e.g. /24) separated by a colon or just the netmask. The range name + is the name of the range within the network interface's subnet from + which to allocate an IP alias range. If unspecified, it defaults to + the primary IP range of the subnet. The IP allocator will pick an + available range with the specified netmask and allocate it to this + network interface. --network-tier=NETWORK_TIER Specifies the network tier that will be used to configure the instance. diff --git a/gcloud/compute/instances/bulk/create b/gcloud/compute/instances/bulk/create index ab9e0149e..23fe51cec 100644 --- a/gcloud/compute/instances/bulk/create +++ b/gcloud/compute/instances/bulk/create @@ -579,9 +579,9 @@ OPTIONAL FLAGS queue-count Specifies the networking queue count for this interface. Both Rx and Tx queues will be set to this number. If it's not specified, a - default queue count will be assigned. For Virtio-net, each - interface will get min(floor(#vCPU / #vNIC), 32) queues. For gVNIC, - each interface will get min(floor(#vCPU / #vNIC / 2), 16) qeueus. + default queue count will be assigned. See + https://cloud.google.com/compute/docs/network-bandwidth#rx-tx for + more details. --network-performance-configs=[PROPERTY=VALUE,...] Configures network performance settings for the instance. If this flag diff --git a/gcloud/compute/instances/create b/gcloud/compute/instances/create index 4d50a74fe..073a84542 100644 --- a/gcloud/compute/instances/create +++ b/gcloud/compute/instances/create @@ -684,18 +684,18 @@ FLAGS --aliases="10.128.1.0/24;range1:/32" - Each IP alias range consists of a range name and an IP range - separated by a colon, or just the IP range. - The range name is the name of the range within the network - interface's subnet from which to allocate an IP alias range. If - unspecified, it defaults to the primary IP range of the subnet. - The IP range can be a CIDR range (e.g. `192.168.100.0/24`), a single - IP address (e.g. `192.168.100.1`), or a netmask in CIDR format (e.g. - `/24`). If the IP range is specified by CIDR range or single IP - address, it must belong to the CIDR range specified by the range - name on the subnet. If the IP range is specified by netmask, the - IP allocator will pick an available range with the specified netmask - and allocate it to this network interface. + Each IP alias range consists of a range name and an IP range + separated by a colon, or just the IP range. The range name is the + name of the range within the network interface's subnet from which + to allocate an IP alias range. If unspecified, it defaults to the + primary IP range of the subnet. The IP range can be a CIDR range + (e.g. 192.168.100.0/24), a single IP address (e.g. 192.168.100.1), + or a netmask in CIDR format (e.g. /24). If the IP range is + specified by CIDR range or single IP address, it must belong to the + CIDR range specified by the range name on the subnet. If the IP + range is specified by netmask, the IP allocator will pick an + available range with the specified netmask and allocate it to this + network interface. --network-performance-configs=[PROPERTY=VALUE,...] Configures network performance settings for the instance. If this flag diff --git a/gcloud/compute/instances/create-with-container b/gcloud/compute/instances/create-with-container index 5935f294a..eca02e616 100644 --- a/gcloud/compute/instances/create-with-container +++ b/gcloud/compute/instances/create-with-container @@ -577,18 +577,18 @@ FLAGS --aliases="10.128.1.0/24;range1:/32" - Each IP alias range consists of a range name and an IP range - separated by a colon, or just the IP range. - The range name is the name of the range within the network - interface's subnet from which to allocate an IP alias range. If - unspecified, it defaults to the primary IP range of the subnet. - The IP range can be a CIDR range (e.g. `192.168.100.0/24`), a single - IP address (e.g. `192.168.100.1`), or a netmask in CIDR format (e.g. - `/24`). If the IP range is specified by CIDR range or single IP - address, it must belong to the CIDR range specified by the range - name on the subnet. If the IP range is specified by netmask, the - IP allocator will pick an available range with the specified netmask - and allocate it to this network interface. + Each IP alias range consists of a range name and an IP range + separated by a colon, or just the IP range. The range name is the + name of the range within the network interface's subnet from which + to allocate an IP alias range. If unspecified, it defaults to the + primary IP range of the subnet. The IP range can be a CIDR range + (e.g. 192.168.100.0/24), a single IP address (e.g. 192.168.100.1), + or a netmask in CIDR format (e.g. /24). If the IP range is + specified by CIDR range or single IP address, it must belong to the + CIDR range specified by the range name on the subnet. If the IP + range is specified by netmask, the IP allocator will pick an + available range with the specified netmask and allocate it to this + network interface. --network-performance-configs=[PROPERTY=VALUE,...] Configures network performance settings for the instance. If this flag diff --git a/gcloud/compute/instances/update b/gcloud/compute/instances/update index 323e20840..16ae49663 100644 --- a/gcloud/compute/instances/update +++ b/gcloud/compute/instances/update @@ -25,15 +25,15 @@ EXAMPLES --zone=us-central1-a --update-labels=k0=value1,k1=value2 \ --remove-labels=k3 - Labels can be used to identify the disk. To list disks with the 'k1:value2' - label, run: + Labels can be used to identify the instance. To list instances with the + 'k1:value2' label, run: $ gcloud compute instances list --filter='labels.k1:value2' To list only the labels when describing a resource, use --format to filter the result: - $ gcloud compute instances describe example-disk \ + $ gcloud compute instances describe example-instance \ --format="default(labels)" POSITIONAL ARGUMENTS diff --git a/gcloud/compute/networks/vpc-access/connectors/create b/gcloud/compute/networks/vpc-access/connectors/create index a07af946d..f3f742552 100644 --- a/gcloud/compute/networks/vpc-access/connectors/create +++ b/gcloud/compute/networks/vpc-access/connectors/create @@ -77,13 +77,13 @@ FLAGS --max-instances=MAX_INSTANCES; default=10 Maximum number of instances within an autoscaling group underlying - the connector. Value must be between 2-10. Must be higher than the - value specified by --min-instances. + the connector. Value must be between 3 and 10, inclusive. Must be + higher than the value specified by --min-instances. --min-instances=MIN_INSTANCES; default=2 Minimum number of instances within an autoscaling group underlying - the connector. Value must be between 1-9. Must be lower than the - value specified by --max-instances. + the connector. Value must be between 2 and 9, inclusive. Must be + lower than the value specified by --max-instances. Scaling settings of a VPC Access Connector can be specified in terms of throughput. diff --git a/gcloud/container/binauthz/attestations/create b/gcloud/container/binauthz/attestations/create index 4d0213246..b1f749603 100644 --- a/gcloud/container/binauthz/attestations/create +++ b/gcloud/container/binauthz/attestations/create @@ -5,8 +5,10 @@ NAME SYNOPSIS gcloud container binauthz attestations create --artifact-url=ARTIFACT_URL --public-key-id=PUBLIC_KEY_ID --signature-file=SIGNATURE_FILE - (--attestor=ATTESTOR : --attestor-project=ATTESTOR_PROJECT) - [--payload-file=PAYLOAD_FILE] [--validate] [GCLOUD_WIDE_FLAG ...] + [--payload-file=PAYLOAD_FILE] + [[--note=NOTE : --note-project=NOTE_PROJECT] + | --validate [--attestor=ATTESTOR + : --attestor-project=ATTESTOR_PROJECT]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION This command creates a Binary Authorization attestation for your project. @@ -24,6 +26,15 @@ EXAMPLES --signature-file=signed_artifact_attestation.pgp.sig \ --public-key-id=AAAA0000000000000000FFFFFFFFFFFFFFFFFFFF + To create an attestation in the project "my_proj" in note + "projects/foo/notes/bar", run: + + $ gcloud container binauthz attestations create --project=my_proj \ + --artifact-url='gcr.io/example-project/example-image@sha256:abcd\ + ' --note=projects/foo/notes/bar \ + --signature-file=signed_artifact_attestation.pgp.sig \ + --public-key-id=AAAA0000000000000000FFFFFFFFFFFFFFFFFFFF + REQUIRED FLAGS --artifact-url=ARTIFACT_URL Container URL. May be in the gcr.io/repository/image format, or may @@ -42,35 +53,6 @@ REQUIRED FLAGS Path to file containing the signature to store, or - to read signature from stdin. - Attestor resource - The Attestor whose Container Analysis Note will be - used to host the created attestation. In order to successfully attach the - attestation, the active gcloud account (core/account) must be able to read - this attestor and must have the containeranalysis.notes.attachOccurrence - permission for the Attestor's underlying Note resource (usually via the - containeranalysis.notes.attacher role). The arguments in this group can be - used to specify the attributes of this resource. - - This must be specified. - - --attestor=ATTESTOR - ID of the attestor or fully qualified identifier for the attestor. - - To set the name attribute: - ▸ provide the argument --attestor on the command line. - - This flag argument must be specified if any of the other arguments in - this group are specified. - - --attestor-project=ATTESTOR_PROJECT - Project ID of the Google Cloud project for the attestor. - - To set the project attribute: - ▸ provide the argument --attestor on the command line with a fully - specified name; - ▸ provide the argument --attestor-project on the command line; - ▸ provide the argument --project on the command line; - ▸ set the property core/project. - OPTIONAL FLAGS --payload-file=PAYLOAD_FILE Path to file containing the payload over which the signature was @@ -84,9 +66,63 @@ OPTIONAL FLAGS formatting, you must explicitly provide the payload content via this flag. - --validate - Whether to validate that the Attestation can be verified by the - provided Attestor. + At most one of these can be specified: + + Note resource - The Container Analysis Note which will be used to host + the created attestation. In order to successfully attach the + attestation, the active gcloud account (core/account) must have the + containeranalysis.notes.attachOccurrence permission for the Note + (usually via the containeranalysis.notes.attacher role). The arguments + in this group can be used to specify the attributes of this resource. + + --note=NOTE + ID of the note or fully qualified identifier for the note. + + To set the note attribute: + ▫ provide the argument --note on the command line. + + This flag argument must be specified if any of the other arguments + in this group are specified. + + --note-project=NOTE_PROJECT + The Container Analysis project for the note. + + To set the project attribute: + ▫ provide the argument --note on the command line with a fully + specified name; + ▫ provide the argument --note-project on the command line. + + --validate + Whether to validate that the Attestation can be verified by the + provided Attestor. + + Attestor resource - The Attestor whose Container Analysis Note will be + used to host the created attestation. In order to successfully attach + the attestation, the active gcloud account (core/account) must be able + to read this attestor and must have the + containeranalysis.notes.attachOccurrence permission for the Attestor's + underlying Note resource (usually via the + containeranalysis.notes.attacher role). The arguments in this group can + be used to specify the attributes of this resource. + + --attestor=ATTESTOR + ID of the attestor or fully qualified identifier for the attestor. + + To set the name attribute: + ▫ provide the argument --attestor on the command line. + + This flag argument must be specified if any of the other arguments + in this group are specified. + + --attestor-project=ATTESTOR_PROJECT + Project ID of the Google Cloud project for the attestor. + + To set the project attribute: + ▫ provide the argument --attestor on the command line with a + fully specified name; + ▫ provide the argument --attestor-project on the command line; + ▫ provide the argument --project on the command line; + ▫ set the property core/project. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/container/binauthz/attestors/create b/gcloud/container/binauthz/attestors/create index 35e479d47..617695cf2 100644 --- a/gcloud/container/binauthz/attestors/create +++ b/gcloud/container/binauthz/attestors/create @@ -34,8 +34,8 @@ POSITIONAL ARGUMENTS ▸ provide the argument ATTESTOR on the command line. REQUIRED FLAGS - Note resource - The Container Analysis ATTESTATION_AUTHORITY Note to which - the created attestor will be bound. + Note resource - The Container Analysis Note to which the created attestor + will be bound. For the attestor to be able to access and use the Note, the Note must exist and the active gcloud account (core/account) must have the diff --git a/gcloud/container/clusters/create b/gcloud/container/clusters/create index 7f3536231..c617325ed 100644 --- a/gcloud/container/clusters/create +++ b/gcloud/container/clusters/create @@ -676,7 +676,7 @@ FLAGS The maximum number of nodes to allocate per default initial node pool. Kubernetes Engine will automatically create enough nodes pools such that each node pool contains less than --max-nodes-per-pool nodes. - Defaults to 1000 nodes, but can be set as low as 100 nodes per pool on + Defaults to 2000 nodes, but can be set as low as 100 nodes per pool on initial create. --max-pods-per-node=MAX_PODS_PER_NODE @@ -1251,8 +1251,8 @@ FLAGS At most one of these can be specified: --dataplane-v2-observability-mode=DATAPLANE_V2_OBSERVABILITY_MODE - Select Advanced Datapath Observability mode for the cluster. Defaults - to DISABLED. + (DEPRECATED) Select Advanced Datapath Observability mode for the + cluster. Defaults to DISABLED. Advanced Datapath Observability allows for a real-time view into pod-to-pod traffic within your cluster. @@ -1268,6 +1268,11 @@ FLAGS $ gcloud container clusters create \ --dataplane-v2-observability-mode=EXTERNAL_LB + The --dataplane-v2-observability-mode flag is deprecated and will be + removed in an upcoming release. Please use + --enable-dataplane-v2-flow-observability or + --disable-dataplane-v2-flow-observability. + DATAPLANE_V2_OBSERVABILITY_MODE must be one of: DISABLED diff --git a/gcloud/container/clusters/create-auto b/gcloud/container/clusters/create-auto index 097d3140b..497638308 100644 --- a/gcloud/container/clusters/create-auto +++ b/gcloud/container/clusters/create-auto @@ -236,16 +236,21 @@ FLAGS --logging=[COMPONENT,...] Set the components that have logging enabled. Valid component values - are: SYSTEM, WORKLOAD, API_SERVER, CONTROLLER_MANAGER, SCHEDULER, NONE + are: SYSTEM, WORKLOAD, API_SERVER, CONTROLLER_MANAGER, SCHEDULER + + The default is SYSTEM,WORKLOAD. If this flag is set, then SYSTEM must + be included. For more information, see https://cloud.google.com/stackdriver/docs/solutions/gke/installing#available-logs Examples: + $ gcloud container clusters create-auto --logging=SYSTEM $ gcloud container clusters create-auto --logging=SYSTEM,WORKLOAD $ gcloud container clusters create-auto \ - --logging=SYSTEM,API_SERVER,WORKLOAD + --logging=SYSTEM,WORKLOAD,API_SERVER,CONTROLLER_MANAGER,\ + SCHEDULER --monitoring=[COMPONENT,...] Set the components that have monitoring enabled. Valid component values @@ -383,8 +388,8 @@ FLAGS At most one of these can be specified: --dataplane-v2-observability-mode=DATAPLANE_V2_OBSERVABILITY_MODE - Select Advanced Datapath Observability mode for the cluster. Defaults - to DISABLED. + (DEPRECATED) Select Advanced Datapath Observability mode for the + cluster. Defaults to DISABLED. Advanced Datapath Observability allows for a real-time view into pod-to-pod traffic within your cluster. @@ -400,6 +405,11 @@ FLAGS $ gcloud container clusters create-auto \ --dataplane-v2-observability-mode=EXTERNAL_LB + The --dataplane-v2-observability-mode flag is deprecated and will be + removed in an upcoming release. Please use + --enable-dataplane-v2-flow-observability or + --disable-dataplane-v2-flow-observability. + DATAPLANE_V2_OBSERVABILITY_MODE must be one of: DISABLED diff --git a/gcloud/container/clusters/update b/gcloud/container/clusters/update index 3bc2f3e6e..e7ca95ccb 100644 --- a/gcloud/container/clusters/update +++ b/gcloud/container/clusters/update @@ -859,8 +859,8 @@ REQUIRED FLAGS At most one of these can be specified: --dataplane-v2-observability-mode=DATAPLANE_V2_OBSERVABILITY_MODE - Select Advanced Datapath Observability mode for the cluster. - Defaults to DISABLED. + (DEPRECATED) Select Advanced Datapath Observability mode for the + cluster. Defaults to DISABLED. Advanced Datapath Observability allows for a real-time view into pod-to-pod traffic within your cluster. @@ -876,6 +876,11 @@ REQUIRED FLAGS $ gcloud container clusters update \ --dataplane-v2-observability-mode=EXTERNAL_LB + The --dataplane-v2-observability-mode flag is deprecated and will + be removed in an upcoming release. Please use + --enable-dataplane-v2-flow-observability or + --disable-dataplane-v2-flow-observability. + DATAPLANE_V2_OBSERVABILITY_MODE must be one of: DISABLED diff --git a/gcloud/dataproc/jobs/submit/pyspark b/gcloud/dataproc/jobs/submit/pyspark index e222fa635..67ca026ed 100644 --- a/gcloud/dataproc/jobs/submit/pyspark +++ b/gcloud/dataproc/jobs/submit/pyspark @@ -87,7 +87,7 @@ OPTIONAL FLAGS --files=[FILE,...] Comma separated list of files to be placed in the working directory of - both the app master and executors. + both the app driver and executors. --jars=[JAR,...] Comma separated list of jar files to be provided to the executor and diff --git a/gcloud/dataproc/jobs/submit/spark b/gcloud/dataproc/jobs/submit/spark index 81e92009f..482a3a842 100644 --- a/gcloud/dataproc/jobs/submit/spark +++ b/gcloud/dataproc/jobs/submit/spark @@ -98,7 +98,7 @@ OPTIONAL FLAGS --files=[FILE,...] Comma separated list of files to be placed in the working directory of - both the app master and executors. + both the app driver and executors. --jars=[JAR,...] Comma separated list of jar files to be provided to the executor and diff --git a/gcloud/dataproc/jobs/submit/spark-r b/gcloud/dataproc/jobs/submit/spark-r index 0ba7f22b8..6143a5e3d 100644 --- a/gcloud/dataproc/jobs/submit/spark-r +++ b/gcloud/dataproc/jobs/submit/spark-r @@ -85,7 +85,7 @@ OPTIONAL FLAGS --files=[FILE,...] Comma separated list of files to be placed in the working directory of - both the app master and executors. + both the app driver and executors. --labels=[KEY=VALUE,...] List of label KEY=VALUE pairs to add. diff --git a/gcloud/dataproc/workflow-templates/add-job/pyspark b/gcloud/dataproc/workflow-templates/add-job/pyspark index 5d42e6ff3..788751198 100644 --- a/gcloud/dataproc/workflow-templates/add-job/pyspark +++ b/gcloud/dataproc/workflow-templates/add-job/pyspark @@ -85,7 +85,7 @@ OPTIONAL FLAGS --files=[FILE,...] Comma separated list of files to be placed in the working directory of - both the app master and executors. + both the app driver and executors. --jars=[JAR,...] Comma separated list of jar files to be provided to the executor and diff --git a/gcloud/dataproc/workflow-templates/add-job/spark b/gcloud/dataproc/workflow-templates/add-job/spark index 17515187a..a105d86f3 100644 --- a/gcloud/dataproc/workflow-templates/add-job/spark +++ b/gcloud/dataproc/workflow-templates/add-job/spark @@ -81,7 +81,7 @@ OPTIONAL FLAGS --files=[FILE,...] Comma separated list of files to be placed in the working directory of - both the app master and executors. + both the app driver and executors. --jars=[JAR,...] Comma separated list of jar files to be provided to the executor and diff --git a/gcloud/dataproc/workflow-templates/add-job/spark-r b/gcloud/dataproc/workflow-templates/add-job/spark-r index 149f42e9f..6f292498c 100644 --- a/gcloud/dataproc/workflow-templates/add-job/spark-r +++ b/gcloud/dataproc/workflow-templates/add-job/spark-r @@ -84,7 +84,7 @@ OPTIONAL FLAGS --files=[FILE,...] Comma separated list of files to be placed in the working directory of - both the app master and executors. + both the app driver and executors. --labels=[KEY=VALUE,...] List of label KEY=VALUE pairs to add. diff --git a/gcloud/datastore/indexes/create b/gcloud/datastore/indexes/create index 658668953..322da77e2 100644 --- a/gcloud/datastore/indexes/create +++ b/gcloud/datastore/indexes/create @@ -3,7 +3,8 @@ NAME your local index configuration SYNOPSIS - gcloud datastore indexes create INDEX_FILE [GCLOUD_WIDE_FLAG ...] + gcloud datastore indexes create INDEX_FILE [--database=DATABASE] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION Create new datastore indexes based on your local index configuration. Any @@ -24,6 +25,15 @@ POSITIONAL ARGUMENTS your index.yaml file, refer to this configuration guide: https://cloud.google.com/datastore/docs/tools/indexconfig#Datastore_About_index_yaml +FLAGS + --database=DATABASE + The database to operate on. If not specified, the CLI refers the + (default) database by default. + + For example, to operate on database testdb: + + $ gcloud datastore indexes create --database='testdb' + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/edge-cloud/container/clusters/create b/gcloud/edge-cloud/container/clusters/create index b59c31a77..0f5322f7d 100644 --- a/gcloud/edge-cloud/container/clusters/create +++ b/gcloud/edge-cloud/container/clusters/create @@ -146,7 +146,8 @@ FLAGS --maintenance-window-recurrence=MAINTENANCE_WINDOW_RECURRENCE An RFC 5545 (https://tools.ietf.org/html/rfc5545#section-3.8.5.3) recurrence rule for how the cluster maintenance window recurs. They go - on for the span of time between the start and the end time. + on for the span of time between the start and the end time. E.g. + FREQ=WEEKLY;BYDAY=SU. --maintenance-window-start=MAINTENANCE_WINDOW_START Start time of the recurring cluster maintenance window in the RFC 3339 diff --git a/gcloud/edge-cloud/container/clusters/update b/gcloud/edge-cloud/container/clusters/update index 343f610aa..2907c0e4b 100644 --- a/gcloud/edge-cloud/container/clusters/update +++ b/gcloud/edge-cloud/container/clusters/update @@ -75,7 +75,8 @@ FLAGS --maintenance-window-recurrence=MAINTENANCE_WINDOW_RECURRENCE An RFC 5545 (https://tools.ietf.org/html/rfc5545#section-3.8.5.3) recurrence rule for how the cluster maintenance window recurs. They - go on for the span of time between the start and the end time. + go on for the span of time between the start and the end time. E.g. + FREQ=WEEKLY;BYDAY=SU. --maintenance-window-start=MAINTENANCE_WINDOW_START Start time of the recurring cluster maintenance window in the RFC diff --git a/gcloud/firestore/databases/create b/gcloud/firestore/databases/create index 12ff342c9..676cbd21b 100644 --- a/gcloud/firestore/databases/create +++ b/gcloud/firestore/databases/create @@ -4,8 +4,9 @@ NAME SYNOPSIS gcloud firestore databases create --location=LOCATION - [--database=DATABASE; default="(default)"] [--enable-pitr] - [--type=TYPE; default="firestore-native"] [GCLOUD_WIDE_FLAG ...] + [--database=DATABASE; default="(default)"] [--delete-protection] + [--enable-pitr] [--type=TYPE; default="firestore-native"] + [GCLOUD_WIDE_FLAG ...] EXAMPLES To create a Firestore Native database in nam5. @@ -22,6 +23,12 @@ EXAMPLES $ gcloud firestore databases create --database=foo \ --location=us-east1 --type=datastore-mode + To create a Firestore Native database in nam5 with delete protection + enabled. + + $ gcloud firestore databases create --location=nam5 \ + --delete-protection + To create a Firestore Native database in nam5 with Point In Time Recovery (PITR) enabled. @@ -48,6 +55,14 @@ OPTIONAL FLAGS Using "(default)" database ID is also allowed. + --delete-protection + Whether to enable delete protection on the created database. + + If set to true, delete protection of the new database will be enabled + and delete operations will fail unless delete protection is disabled. + + Default to false. + --enable-pitr Whether to enable Point In Time Recovery (PITR) on the created database. diff --git a/gcloud/firestore/databases/delete b/gcloud/firestore/databases/delete new file mode 100644 index 000000000..1a383ba7d --- /dev/null +++ b/gcloud/firestore/databases/delete @@ -0,0 +1,46 @@ +NAME + gcloud firestore databases delete - delete a Google Cloud Firestore + database + +SYNOPSIS + gcloud firestore databases delete --database=DATABASE [--etag=ETAG] + [GCLOUD_WIDE_FLAG ...] + +EXAMPLES + To delete a Firestore database test. + + $ gcloud firestore databases delete --database=test + + To delete the Firestore (default) database. + + $ gcloud firestore databases delete --database=(default) + + To delete a Firestore database test providing etag. + + $ gcloud firestore databases delete --database=test --etag=etag + +REQUIRED FLAGS + --database=DATABASE + The database to operate on. + +OPTIONAL FLAGS + --etag=ETAG + The current etag of the Database. If an etag is provided and does not + match the current etag of the database, deletion will be blocked and a + FAILED_PRECONDITION error will be returned. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha firestore databases delete + + $ gcloud beta firestore databases delete + diff --git a/gcloud/firestore/databases/help b/gcloud/firestore/databases/help index 63446b667..f5a8a4fdb 100644 --- a/gcloud/firestore/databases/help +++ b/gcloud/firestore/databases/help @@ -19,6 +19,9 @@ COMMANDS create Create a Google Cloud Firestore database via Firestore API. + delete + Delete a Google Cloud Firestore database. + describe Describes information about a Cloud Firestore database. diff --git a/gcloud/firestore/databases/update b/gcloud/firestore/databases/update index 7e19f9c7a..ef8eb2f8c 100644 --- a/gcloud/firestore/databases/update +++ b/gcloud/firestore/databases/update @@ -4,7 +4,8 @@ NAME SYNOPSIS gcloud firestore databases update [--async] [--database=DATABASE] - [--enable-pitr] [--type=TYPE] [GCLOUD_WIDE_FLAG ...] + [--delete-protection] [--enable-pitr] [--type=TYPE] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION Update the database configuration of a Cloud Firestore database. @@ -39,6 +40,12 @@ FLAGS ▸ provide the argument --database on the command line; ▸ the default value of argument [--database] is (default). + --delete-protection + If set to true, the Firestore database will be updated to have database + delete protection enabled. A database with delete protection enabled + cannot be deleted. You can disable the delete protection via + --no-delete-protection. + --enable-pitr If set to true, the Firestore database will be updated to enable Point In Time Recovery. You can disable the this feature via diff --git a/gcloud/functions/deploy b/gcloud/functions/deploy index 887b8c4b5..c93072185 100644 --- a/gcloud/functions/deploy +++ b/gcloud/functions/deploy @@ -539,7 +539,8 @@ FLAGS To set the region attribute: ▸ provide the argument --vpc-connector on the command line with a fully specified name; - ▸ provide the argument --region on the command line. + ▸ provide the argument --region on the command line; + ▸ set the property functions/region. --vpc-connector=VPC_CONNECTOR ID of the connector or fully qualified identifier for the diff --git a/gcloud/iam/workload-identity-pools/create-cred-config b/gcloud/iam/workload-identity-pools/create-cred-config index 3a11528b5..4f21ee779 100644 --- a/gcloud/iam/workload-identity-pools/create-cred-config +++ b/gcloud/iam/workload-identity-pools/create-cred-config @@ -75,7 +75,7 @@ EXAMPLES POSITIONAL ARGUMENTS AUDIENCE - The workload identity pool provider resource ID. + The workload identity pool provider fully qualified identifier. REQUIRED FLAGS --output-file=OUTPUT_FILE diff --git a/gcloud/infra-manager/deployments/apply b/gcloud/infra-manager/deployments/apply index 7b445b3e7..b973894bf 100644 --- a/gcloud/infra-manager/deployments/apply +++ b/gcloud/infra-manager/deployments/apply @@ -101,13 +101,13 @@ FLAGS Update labels for an existing deployment: $ gcloud infra-manager deployments apply \ - projects/p1/location/us-central1/deployments/my-deployment \ + projects/p1/locations/us-central1/deployments/my-deployment \ --gcs-source="gs://my-bucket" --labels="env=prod,team=finance" Clear labels for an existing deployment: $ gcloud infra-manager deployments apply \ - projects/p1/location/us-central1/deployments/my-deployment \ + projects/p1/locations/us-central1/deployments/my-deployment \ --gcs-source="gs://my-bucket" --labels="" Add a label to an existing deployment: diff --git a/gcloud/infra-manager/help b/gcloud/infra-manager/help index ef010ee7f..2a1e0ea28 100644 --- a/gcloud/infra-manager/help +++ b/gcloud/infra-manager/help @@ -18,6 +18,9 @@ GROUPS deployments Manage Deployment resources. + previews + Manage Preview resources. + resources List or describe resources under a Revision. diff --git a/gcloud/infra-manager/previews/create b/gcloud/infra-manager/previews/create new file mode 100644 index 000000000..82f49f125 --- /dev/null +++ b/gcloud/infra-manager/previews/create @@ -0,0 +1,239 @@ +NAME + gcloud infra-manager previews create - create a preview + +SYNOPSIS + gcloud infra-manager previews create [PREVIEW] + [--artifacts-gcs-bucket=ARTIFACTS_GCS_BUCKET] [--async] + [--deployment=DEPLOYMENT] [--labels=[KEY=VALUE,...]] + [--location=LOCATION] [--preview-mode=PREVIEW_MODE] + [--service-account=SERVICE_ACCOUNT] [--worker-pool=WORKER_POOL] + [--gcs-source=GCS_SOURCE | --git-source-directory=GIT_SOURCE_DIRECTORY + --git-source-ref=GIT_SOURCE_REF --git-source-repo=GIT_SOURCE_REPO + | --ignore-file=IGNORE_FILE + --local-source=LOCAL_SOURCE --input-values=[KEY=VALUE,...] + | --inputs-file=INPUTS_FILE] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + This command creates a preview. + +EXAMPLES + Create a preview named my-preview from a storage my-bucket: + + $ gcloud infra-manager previews create \ + projects/p1/locations/us-central1/previews/my-preview \ + --gcs-source="gs://my-bucket" \ + --input-values="project=p1,region=us-central1" + + Create a preview named my-preview from git repo + "https://github.com/examples/repository.git", "staging/compute" folder, + "mainline" branch: + + $ gcloud infra-manager previews create \ + projects/p1/locations/us-central1/previews/my-preview \ + --git-source-repo="https://github.com/examples/repository.git" \ + --git-source-directory="staging/compute" \ + --git-source-ref="mainline" + +POSITIONAL ARGUMENTS + Preview resource - the preview to be used as parent. It is optional and + will be generated if not specified with a fully specified name. This + represents a Cloud resource. (NOTE) Some attributes are not given + arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument PREVIEW on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + To set the location attribute: + ◆ provide the argument PREVIEW on the command line with a fully + specified name; + ◆ provide the argument --location on the command line; + ◆ set the property infra-manager/location. + + PREVIEW + ID of the preview or fully qualified identifier for the preview. + + To set the preview attribute: + ▸ provide the argument PREVIEW on the command line. + +FLAGS + --artifacts-gcs-bucket=ARTIFACTS_GCS_BUCKET + user-defined location of Cloud Build logs, artifacts, and Terraform + state files in Google Cloud Storage. Format: gs://{bucket}/{folder} A + default bucket will be bootstrapped if the field is not set or empty + + --async + Return immediately, without waiting for the operation in progress to + complete. + + --deployment=DEPLOYMENT + Deployment reference for preview. + + --labels=[KEY=VALUE,...] + Labels to apply to the preview. Existing values are overwritten. To + retain the existing labels on a preview, do not specify this flag. + + Examples: + + Update labels for an existing preview: + + $ gcloud infra-manager previews create \ + projects/p1/locations/us-central1/previews/my-preview \ + --gcs-source="gs://my-bucket" --labels="env=prod,team=finance" + + Clear labels for an existing preview: + + $ gcloud infra-manager previews create \ + projects/p1/locations/us-central1/previews/my-preview \ + --gcs-source="gs://my-bucket" --labels="" + + Add a label to an existing preview: + + First, fetch the current labels using the `describe` command, then follow the + preceding example for updating labels. + + Location resource - the location to be used as parent. 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 infra-manager/location with a fully specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + --location=LOCATION + ID of the location or fully qualified identifier for the location. + + To set the location attribute: + ▸ provide the argument --location on the command line; + ▸ set the property infra-manager/location. + + --preview-mode=PREVIEW_MODE + Preview mode to set it to either default or delete. + + --service-account=SERVICE_ACCOUNT + User-specified Service Account (SA) to be used as credential to manage + resources. Format: + projects/{projectID}/serviceAccounts/{serviceAccount} + + --worker-pool=WORKER_POOL + User-specified Worker Pool resource in which the Cloud Build jobwill + execute. Format: + projects/{project}/locations/{location}/workerPools/{workerPoolId} + + At most one of these can be specified: + + --gcs-source=GCS_SOURCE + URI of an object in Google Cloud Storage. e.g. gs://{bucket}/{object} + + Examples: + + Create a deployment from a storage my-bucket: + + $ gcloud infra-manager previews create \ + projects/p1/location/us-central1/deployments/my-deployment \ + --gcs-source="gs://my-bucket" + + --git-source-directory=GIT_SOURCE_DIRECTORY + Subdirectory inside the repository. Example: 'staging/my-package' + + Use in conjunction with --git-source-repo and --git-source-ref + + Examples: + + Create a deployment from the + "https://github.com/examples/repository.git" repo, "staging/compute" + folder, "mainline" branch: + + $ gcloud infra-manager previews create \ + projects/p1/location/us-central1/deployments/my-deployment \ + --git-source-repo="https://github.com/examples/repository.git" + --git-source-directory="staging/compute" --git-source-ref="mainline" + + --git-source-ref=GIT_SOURCE_REF + Subdirectory inside the repository. Example: 'staging/my-package' + + Use in conjunction with --git-source-repo and --git-source-directory + + Examples: + + Create a deployment from the + "https://github.com/examples/repository.git" repo, "staging/compute" + folder, "mainline" branch: + + $ gcloud infra-manager previews create \ + projects/p1/location/us-central1/deployments/my-deployment \ + --git-source-repo="https://github.com/examples/repository.git" + --git-source-directory="staging/compute" --git-source-ref="mainline" + + --git-source-repo=GIT_SOURCE_REPO + Repository URL. Example: 'https://github.com/examples/repository.git' + + Use in conjunction with --git-source-directory and --git-source_ref + + Examples: + + Create a deployment from the + "https://github.com/examples/repository.git" repo, "staging/compute" + folder, "mainline" branch: + + $ gcloud infra-manager previews create \ + projects/p1/location/us-central1/deployments/my-deployment \ + --git-source-repo="https://github.com/examples/repository.git" + --git-source-directory="staging/compute" --git-source-ref="mainline" + + --ignore-file=IGNORE_FILE + Override the .gcloudignore file and use the specified file instead. + See gcloud topic gcloudignore for more information. + + --local-source=LOCAL_SOURCE + Local storage path where config files are stored. e.g. + ./path/to/blueprint + + Examples: + + Create a deployment from a local storage path ./path/to/blueprint: + + $ gcloud infra-manager previews create \ + projects/p1/location/us-central1/deployments/my-deployment \ + --local-source="./path/to/blueprint" + + At most one of these can be specified: + + --input-values=[KEY=VALUE,...] + Input variable values for the Terraform blueprint. It only accepts + (key, value) pairs where value is a scalar value. + + Examples: + + Pass input values on command line: + + $ gcloud infra-manager previews create \ + projects/p1/location/us-central1/deployments/my-deployment \ + --gcs-source="gs://my-bucket" \ + --input-values=projects=p1,region=r + + --inputs-file=INPUTS_FILE + A .tfvars file containing terraform variable values. --inputs-file + flag is supported for python version 3.6 and above. + + Examples: + + Pass input values on the command line: + + $ gcloud infra-manager previews create \ + projects/p1/location/us-central1/deployments/my-deployment \ + --gcs-source="gs://my-bucket" \ + --inputs-file=path-to-tfvar-file.tfvar + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. diff --git a/gcloud/infra-manager/previews/delete b/gcloud/infra-manager/previews/delete new file mode 100644 index 000000000..a622daaa0 --- /dev/null +++ b/gcloud/infra-manager/previews/delete @@ -0,0 +1,63 @@ +NAME + gcloud infra-manager previews delete - delete previews + +SYNOPSIS + gcloud infra-manager previews delete (PREVIEW : --location=LOCATION) + [--async] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Delete a preview + +EXAMPLES + To delete the preview example-preview at location us-central1, run: + + $ gcloud infra-manager previews delete \ + projects/example-project/locations/us-central1/previews/\ + example-preview + +POSITIONAL ARGUMENTS + Preview resource - previews TBD The arguments in this group can be used to + specify the attributes of this resource. (NOTE) Some attributes are not + given arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument preview on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + PREVIEW + ID of the preview or fully qualified identifier for the preview. + + To set the preview attribute: + ▸ provide the argument preview on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + locations TBD + + To set the location attribute: + ▸ provide the argument preview on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the config/v1 API. The full documentation for this API + can be found at: https://cloud.google.com/infrastructure-manager/docs diff --git a/gcloud/infra-manager/previews/describe b/gcloud/infra-manager/previews/describe new file mode 100644 index 000000000..b2c7c4be0 --- /dev/null +++ b/gcloud/infra-manager/previews/describe @@ -0,0 +1,58 @@ +NAME + gcloud infra-manager previews describe - describe previews + +SYNOPSIS + gcloud infra-manager previews describe (PREVIEW : --location=LOCATION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Describe a preview + +EXAMPLES + To describe a preview example-preview in project p1 at location + us-central1, run: + + $ gcloud infra-manager previews describe \ + projects/p1/locations/us-central1/previews/example-preview + +POSITIONAL ARGUMENTS + Preview resource - The preview to describe The arguments in this group can + be used to specify the attributes of this resource. (NOTE) Some attributes + are not given arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument preview on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + PREVIEW + ID of the preview or fully qualified identifier for the preview. + + To set the preview attribute: + ▸ provide the argument preview on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + locations TBD + + To set the location attribute: + ▸ provide the argument preview on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the config/v1 API. The full documentation for this API + can be found at: https://cloud.google.com/infrastructure-manager/docs diff --git a/gcloud/infra-manager/previews/export b/gcloud/infra-manager/previews/export new file mode 100644 index 000000000..52163aadd --- /dev/null +++ b/gcloud/infra-manager/previews/export @@ -0,0 +1,55 @@ +NAME + gcloud infra-manager previews export - export preview results + +SYNOPSIS + gcloud infra-manager previews export (PREVIEW : --location=LOCATION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + This command generates a signed url to download a preview results. + +EXAMPLES + Export preview results for my-preview: + + $ gcloud infra-manager previews export \ + projects/p1/locations/us-central1/previews/my-preview + +POSITIONAL ARGUMENTS + Preview resource - the preview to be used as parent. The arguments in this + group can be used to specify the attributes of this resource. (NOTE) Some + attributes are not given arguments in this group but can be set in other + ways. + + To set the project attribute: + ◆ provide the argument PREVIEW on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + PREVIEW + ID of the preview or fully qualified identifier for the preview. + + To set the preview attribute: + ▸ provide the argument PREVIEW on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The Cloud location for the preview. + + To set the location attribute: + ▸ provide the argument PREVIEW on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property infra-manager/location. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. diff --git a/gcloud/infra-manager/previews/help b/gcloud/infra-manager/previews/help new file mode 100644 index 000000000..91c60d577 --- /dev/null +++ b/gcloud/infra-manager/previews/help @@ -0,0 +1,31 @@ +NAME + gcloud infra-manager previews - manage Preview resources + +SYNOPSIS + gcloud infra-manager previews COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Manage Preview resources. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + create + Create a preview. + + delete + Delete previews. + + describe + Describe previews. + + export + Export preview results. + + list + List previews. diff --git a/gcloud/beta/privateca/reusable-configs/list b/gcloud/infra-manager/previews/list similarity index 53% rename from gcloud/beta/privateca/reusable-configs/list rename to gcloud/infra-manager/previews/list index 8b46c58e9..9677977cb 100644 --- a/gcloud/beta/privateca/reusable-configs/list +++ b/gcloud/infra-manager/previews/list @@ -1,19 +1,37 @@ NAME - gcloud beta privateca reusable-configs list - list reusable configs + gcloud infra-manager previews list - list previews SYNOPSIS - gcloud beta privateca reusable-configs list [--location=LOCATION] - [--filter=EXPRESSION] [--limit=LIMIT] - [--page-size=PAGE_SIZE; default=100] - [--sort-by=[FIELD,...]; default="name"] [--uri] [GCLOUD_WIDE_FLAG ...] + gcloud infra-manager previews list --location=LOCATION + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) List reusable configs. + List previews -FLAGS - --location=LOCATION - Location of the reusable configs. If this is not specified, it defaults - to the first location supported by the service. +EXAMPLES + To list all previews at location us-central1, run: + + $ gcloud infra-manager previews list --location=us-central1 + +REQUIRED FLAGS + Location resource - Location to list previews This represents a Cloud + resource. (NOTE) Some attributes are not given arguments in this group but + can be set in other ways. + + To set the project attribute: + ◆ provide the argument --location on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + --location=LOCATION + ID of the location or fully qualified identifier for the location. + + To set the location attribute: + ▸ provide the argument --location on the command line. LIST COMMAND FLAGS --filter=EXPRESSION @@ -28,18 +46,18 @@ LIST COMMAND FLAGS flag interacts with other flags that are applied in this order: --flatten, --sort-by, --filter, --limit. - --page-size=PAGE_SIZE; default=100 + --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 100. - Paging may be applied before or after --filter and --limit depending on - the service. + 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,...]; default="name" + --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. The - default is name. + applied in this order: --flatten, --sort-by, --filter, --limit. --uri Print a list of resource URIs instead of the default output, and change @@ -55,6 +73,6 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. -NOTES - This command is currently in beta and might change without notice. - +API REFERENCE + This command uses the config/v1 API. The full documentation for this API + can be found at: https://cloud.google.com/infrastructure-manager/docs diff --git a/gcloud/logging/copy b/gcloud/logging/copy index e4d2c4253..f0c1360fb 100644 --- a/gcloud/logging/copy +++ b/gcloud/logging/copy @@ -15,13 +15,12 @@ DESCRIPTION EXAMPLES To start a copy log entries operation, run: - $ gcloud logging copy "BUCKET_ID DESTINATION --location=LOCATION" + $ gcloud logging copy BUCKET_ID DESTINATION --location=LOCATION To copy log entries in a specific time window, run: - $ gcloud logging copy \ - 'BUCKET_ID DESTINATION --location=LOCATION - --log-filter=timestamp<="2021-05-31T23:59:59Z" AND + $ gcloud logging copy BUCKET_ID DESTINATION --location=LOCATION \ + --log-filter='timestamp<="2021-05-31T23:59:59Z" AND timestamp>="2021-05-31T00:00:00Z"' POSITIONAL ARGUMENTS diff --git a/gcloud/logging/operations/list b/gcloud/logging/operations/list index 2b00198b2..44009576d 100644 --- a/gcloud/logging/operations/list +++ b/gcloud/logging/operations/list @@ -24,32 +24,32 @@ EXAMPLES To list CopyLogEntries operations, run: $ gcloud logging operations list --location=LOCATION \ - --operation-filter=request_type=CopyLogEntries + --operation-filter='request_type=CopyLogEntries' To list CopyLogEntries operations that started after a specified time, run: $ gcloud logging operations list --location=LOCATION \ - --operation-filter=request_type=CopyLogEntries AND \ - operation_start_time>TIMESTAMP + --operation-filter='request_type=CopyLogEntries AND + operation_start_time>="2023-11-20T00:00:00Z"' To list CopyLogEntries operations that finished before a specified time, run: $ gcloud logging operations list --location=LOCATION \ - --operation-filter=request_type=CopyLogEntries AND \ - operation_finish_time