From d3074f94bbf66cc4f16ecff3c83fe269deb2d53b Mon Sep 17 00:00:00 2001 From: Automated Date: Wed, 15 Nov 2023 11:42:54 +0000 Subject: [PATCH] gcloud: Wed Nov 15 11:42:54 UTC 2023 --- gcloud/_version | 10 +- gcloud/alpha/assured/operations/list | 2 +- gcloud/alpha/assured/workloads/create | 2 +- gcloud/alpha/assured/workloads/list | 2 +- .../alpha/assured/workloads/violations/list | 2 +- .../alpha/backup-dr/management-servers/create | 6 + gcloud/alpha/batch/jobs/submit | 9 +- .../alpha/compute/instance-templates/create | 54 ++++--- gcloud/alpha/compute/instances/bulk/create | 57 ++++--- gcloud/alpha/compute/instances/create | 57 +++---- .../compute/instances/create-with-container | 55 ++++--- gcloud/alpha/compute/queued-resources/create | 57 ++++--- gcloud/alpha/compute/queued-resources/list | 34 +++-- gcloud/alpha/compute/tpus/help | 3 + .../compute/tpus/queued-resources/create | 2 +- gcloud/alpha/compute/tpus/reservations/help | 26 ++++ gcloud/alpha/compute/tpus/reservations/list | 90 +++++++++++ gcloud/alpha/compute/tpus/tpu-vm/create | 2 +- gcloud/alpha/config/get | 14 ++ gcloud/alpha/config/help | 14 ++ gcloud/alpha/config/list | 14 ++ gcloud/alpha/config/set | 14 ++ gcloud/alpha/config/unset | 14 ++ .../container/binauthz/attestations/list | 29 ++-- .../binauthz/attestations/sign-and-create | 23 ++- gcloud/alpha/container/fleet/create | 25 +++- .../container/fleet/identity-service/apply | 40 +++-- .../container/fleet/identity-service/delete | 13 +- .../container/fleet/identity-service/enable | 8 +- .../container/fleet/identity-service/help | 7 +- gcloud/alpha/container/fleet/mesh/disable | 13 +- gcloud/alpha/container/fleet/mesh/enable | 14 +- gcloud/alpha/container/fleet/mesh/update | 18 ++- gcloud/alpha/container/fleet/update | 22 +++ gcloud/alpha/container/hub/create | 25 +++- .../container/hub/identity-service/apply | 40 +++-- .../container/hub/identity-service/delete | 13 +- .../container/hub/identity-service/enable | 8 +- .../alpha/container/hub/identity-service/help | 7 +- gcloud/alpha/container/hub/mesh/disable | 13 +- gcloud/alpha/container/hub/mesh/enable | 14 +- gcloud/alpha/container/hub/mesh/update | 18 ++- gcloud/alpha/container/hub/update | 22 +++ gcloud/alpha/dataproc/clusters/create | 42 ++++++ .../workflow-templates/set-managed-cluster | 42 ++++++ gcloud/alpha/filestore/instances/create | 10 +- gcloud/alpha/filestore/instances/update | 1 + gcloud/alpha/firestore/databases/delete | 4 +- gcloud/alpha/firestore/export | 13 +- gcloud/alpha/metastore/services/update | 4 +- .../firewall-endpoints/create | 7 +- gcloud/alpha/run/jobs/executions/cancel | 4 +- gcloud/alpha/scc/custom-modules/sha/help | 3 + gcloud/alpha/scc/custom-modules/sha/simulate | 83 +++++++++++ gcloud/alpha/sql/instances/create | 4 + gcloud/alpha/sql/instances/list | 11 +- gcloud/alpha/sql/instances/patch | 10 ++ gcloud/alpha/storage/buckets/create | 6 +- gcloud/alpha/storage/cp | 14 +- .../storage/insights/dataset-configs/create | 129 ++++++++++++++++ .../insights/dataset-configs/create-link | 70 +++++++++ .../storage/insights/dataset-configs/delete | 87 +++++++++++ .../insights/dataset-configs/delete-link | 69 +++++++++ .../storage/insights/dataset-configs/describe | 69 +++++++++ .../storage/insights/dataset-configs/help | 47 ++++++ .../storage/insights/dataset-configs/list | 82 ++++++++++ .../storage/insights/dataset-configs/update | 84 +++++++++++ gcloud/alpha/storage/insights/help | 6 + .../alpha/storage/insights/operations/cancel | 39 +++++ .../storage/insights/operations/describe | 37 +++++ gcloud/alpha/storage/insights/operations/help | 32 ++++ gcloud/alpha/storage/insights/operations/list | 73 +++++++++ gcloud/alpha/storage/mv | 14 +- gcloud/alpha/storage/objects/compose | 14 +- gcloud/alpha/storage/objects/update | 25 +++- gcloud/alpha/transfer/jobs/create | 2 +- gcloud/alpha/transfer/jobs/update | 2 +- gcloud/asset/get-effective-iam-policy | 2 +- gcloud/asset/search-all-iam-policies | 2 +- gcloud/asset/search-all-resources | 2 +- gcloud/assured/operations/list | 2 +- gcloud/assured/workloads/create | 2 +- gcloud/assured/workloads/list | 2 +- gcloud/assured/workloads/violations/list | 2 +- gcloud/beta/asset/search-all-resources | 2 +- gcloud/beta/assured/operations/list | 2 +- gcloud/beta/assured/workloads/create | 2 +- gcloud/beta/assured/workloads/list | 2 +- gcloud/beta/assured/workloads/violations/list | 2 +- gcloud/beta/config/get | 14 ++ gcloud/beta/config/help | 14 ++ gcloud/beta/config/list | 14 ++ gcloud/beta/config/set | 14 ++ gcloud/beta/config/unset | 14 ++ .../beta/container/binauthz/attestations/list | 29 ++-- .../binauthz/attestations/sign-and-create | 23 ++- gcloud/beta/container/fleet/create | 25 +++- .../container/fleet/identity-service/apply | 40 +++-- .../container/fleet/identity-service/delete | 13 +- .../container/fleet/identity-service/enable | 8 +- .../container/fleet/identity-service/help | 7 +- gcloud/beta/container/fleet/mesh/disable | 13 +- gcloud/beta/container/fleet/mesh/enable | 14 +- gcloud/beta/container/fleet/update | 22 +++ gcloud/beta/container/hub/create | 25 +++- .../beta/container/hub/identity-service/apply | 40 +++-- .../container/hub/identity-service/delete | 13 +- .../container/hub/identity-service/enable | 10 +- .../beta/container/hub/identity-service/help | 7 +- gcloud/beta/container/hub/mesh/disable | 13 +- gcloud/beta/container/hub/mesh/enable | 14 +- gcloud/beta/container/hub/update | 22 +++ gcloud/beta/data-fusion/instances/create | 9 +- gcloud/beta/data-fusion/instances/update | 17 ++- gcloud/beta/dataproc/clusters/create | 42 ++++++ .../workflow-templates/set-managed-cluster | 42 ++++++ gcloud/beta/filestore/instances/create | 10 +- gcloud/beta/filestore/instances/update | 1 + gcloud/beta/firestore/databases/delete | 45 ++++++ gcloud/beta/firestore/databases/help | 3 + gcloud/beta/firestore/export | 13 +- gcloud/beta/metastore/services/update | 4 +- gcloud/beta/run/jobs/executions/cancel | 6 +- gcloud/beta/sql/instances/create | 4 + gcloud/beta/sql/instances/list | 11 +- gcloud/beta/sql/instances/patch | 10 ++ gcloud/compute/tpus/tpu-vm/update | 40 +++++ gcloud/config/get | 14 ++ gcloud/config/help | 14 ++ gcloud/config/list | 14 ++ gcloud/config/set | 14 ++ gcloud/config/unset | 14 ++ gcloud/container/binauthz/attestations/list | 30 ++-- gcloud/container/fleet/create | 25 +++- gcloud/container/fleet/identity-service/apply | 40 +++-- .../container/fleet/identity-service/delete | 24 ++- .../container/fleet/identity-service/enable | 28 +++- gcloud/container/fleet/identity-service/help | 6 +- gcloud/container/fleet/mesh/disable | 12 +- gcloud/container/fleet/mesh/enable | 14 +- gcloud/container/fleet/mesh/update | 17 ++- gcloud/container/fleet/update | 22 +++ gcloud/container/hub/create | 25 +++- gcloud/container/hub/identity-service/apply | 40 +++-- gcloud/container/hub/identity-service/delete | 24 ++- gcloud/container/hub/identity-service/enable | 26 +++- gcloud/container/hub/identity-service/help | 6 +- gcloud/container/hub/mesh/disable | 12 +- gcloud/container/hub/mesh/enable | 14 +- gcloud/container/hub/mesh/update | 17 ++- gcloud/container/hub/update | 22 +++ gcloud/dataproc/clusters/create | 42 ++++++ .../workflow-templates/set-managed-cluster | 42 ++++++ gcloud/filestore/instances/create | 10 +- gcloud/filestore/instances/update | 1 + gcloud/firestore/export | 13 +- gcloud/functions/deploy | 62 +++++--- gcloud/metastore/services/create | 7 +- gcloud/metastore/services/update | 10 +- gcloud/network-connectivity/spokes/accept | 66 -------- gcloud/network-connectivity/spokes/help | 6 - gcloud/network-connectivity/spokes/reject | 70 --------- gcloud/run/jobs/executions/cancel | 59 ++++++++ gcloud/run/jobs/executions/help | 3 + gcloud/scc/custom-modules/sha/help | 3 + gcloud/scc/custom-modules/sha/simulate | 77 ++++++++++ gcloud/sql/instances/create | 4 + gcloud/sql/instances/list | 11 +- gcloud/sql/instances/patch | 10 ++ gcloud/storage/buckets/create | 6 +- gcloud/storage/cp | 14 +- gcloud/storage/mv | 14 +- gcloud/storage/objects/compose | 14 +- gcloud/storage/objects/update | 25 +++- gcloud/transfer/jobs/create | 2 +- gcloud/transfer/jobs/update | 2 +- gcloud/vmware/dns-bind-permission/describe | 31 ++++ gcloud/vmware/dns-bind-permission/grant | 71 +++++++++ gcloud/vmware/dns-bind-permission/help | 26 ++++ gcloud/vmware/dns-bind-permission/revoke | 68 +++++++++ gcloud/vmware/help | 6 + gcloud/vmware/network-peerings/create | 135 +++++++++++++++++ gcloud/vmware/network-peerings/delete | 54 +++++++ gcloud/vmware/network-peerings/describe | 46 ++++++ gcloud/vmware/network-peerings/help | 39 +++++ gcloud/vmware/network-peerings/list | 81 ++++++++++ gcloud/vmware/network-peerings/routes/help | 20 +++ gcloud/vmware/network-peerings/routes/list | 85 +++++++++++ gcloud/vmware/network-peerings/update | 57 +++++++ .../external-access-rules/create | 141 ++++++++++++++++++ .../external-access-rules/delete | 84 +++++++++++ .../external-access-rules/describe | 78 ++++++++++ .../external-access-rules/help | 34 +++++ .../external-access-rules/list | 117 +++++++++++++++ .../external-access-rules/update | 123 +++++++++++++++ gcloud/vmware/network-policies/help | 7 + gcloud/vmware/private-clouds/clusters/help | 6 + .../private-clouds/clusters/nodes/describe | 83 +++++++++++ .../vmware/private-clouds/clusters/nodes/help | 23 +++ .../vmware/private-clouds/clusters/nodes/list | 106 +++++++++++++ gcloud/vmware/private-clouds/create | 29 +++- .../private-clouds/dns-forwarding/describe | 67 +++++++++ .../vmware/private-clouds/dns-forwarding/help | 23 +++ .../private-clouds/dns-forwarding/update | 88 +++++++++++ .../private-clouds/external-addresses/create | 94 ++++++++++++ .../private-clouds/external-addresses/delete | 82 ++++++++++ .../external-addresses/describe | 76 ++++++++++ .../private-clouds/external-addresses/help | 33 ++++ .../private-clouds/external-addresses/list | 91 +++++++++++ .../private-clouds/external-addresses/update | 94 ++++++++++++ gcloud/vmware/private-clouds/help | 12 ++ .../private-clouds/logging-servers/create | 101 +++++++++++++ .../private-clouds/logging-servers/delete | 81 ++++++++++ .../private-clouds/logging-servers/describe | 75 ++++++++++ .../private-clouds/logging-servers/help | 32 ++++ .../private-clouds/logging-servers/list | 99 ++++++++++++ .../private-clouds/logging-servers/update | 100 +++++++++++++ .../management-dns-zone-bindings/create | 104 +++++++++++++ .../management-dns-zone-bindings/delete | 84 +++++++++++ .../management-dns-zone-bindings/describe | 81 ++++++++++ .../management-dns-zone-bindings/help | 36 +++++ .../management-dns-zone-bindings/list | 92 ++++++++++++ .../management-dns-zone-bindings/repair | 85 +++++++++++ .../management-dns-zone-bindings/update | 91 +++++++++++ 224 files changed, 6432 insertions(+), 626 deletions(-) create mode 100644 gcloud/alpha/compute/tpus/reservations/help create mode 100644 gcloud/alpha/compute/tpus/reservations/list create mode 100644 gcloud/alpha/scc/custom-modules/sha/simulate create mode 100644 gcloud/alpha/storage/insights/dataset-configs/create create mode 100644 gcloud/alpha/storage/insights/dataset-configs/create-link create mode 100644 gcloud/alpha/storage/insights/dataset-configs/delete create mode 100644 gcloud/alpha/storage/insights/dataset-configs/delete-link create mode 100644 gcloud/alpha/storage/insights/dataset-configs/describe create mode 100644 gcloud/alpha/storage/insights/dataset-configs/help create mode 100644 gcloud/alpha/storage/insights/dataset-configs/list create mode 100644 gcloud/alpha/storage/insights/dataset-configs/update create mode 100644 gcloud/alpha/storage/insights/operations/cancel create mode 100644 gcloud/alpha/storage/insights/operations/describe create mode 100644 gcloud/alpha/storage/insights/operations/help create mode 100644 gcloud/alpha/storage/insights/operations/list create mode 100644 gcloud/beta/firestore/databases/delete delete mode 100644 gcloud/network-connectivity/spokes/accept delete mode 100644 gcloud/network-connectivity/spokes/reject create mode 100644 gcloud/run/jobs/executions/cancel create mode 100644 gcloud/scc/custom-modules/sha/simulate create mode 100644 gcloud/vmware/dns-bind-permission/describe create mode 100644 gcloud/vmware/dns-bind-permission/grant create mode 100644 gcloud/vmware/dns-bind-permission/help create mode 100644 gcloud/vmware/dns-bind-permission/revoke create mode 100644 gcloud/vmware/network-peerings/create create mode 100644 gcloud/vmware/network-peerings/delete create mode 100644 gcloud/vmware/network-peerings/describe create mode 100644 gcloud/vmware/network-peerings/help create mode 100644 gcloud/vmware/network-peerings/list create mode 100644 gcloud/vmware/network-peerings/routes/help create mode 100644 gcloud/vmware/network-peerings/routes/list create mode 100644 gcloud/vmware/network-peerings/update create mode 100644 gcloud/vmware/network-policies/external-access-rules/create create mode 100644 gcloud/vmware/network-policies/external-access-rules/delete create mode 100644 gcloud/vmware/network-policies/external-access-rules/describe create mode 100644 gcloud/vmware/network-policies/external-access-rules/help create mode 100644 gcloud/vmware/network-policies/external-access-rules/list create mode 100644 gcloud/vmware/network-policies/external-access-rules/update create mode 100644 gcloud/vmware/private-clouds/clusters/nodes/describe create mode 100644 gcloud/vmware/private-clouds/clusters/nodes/help create mode 100644 gcloud/vmware/private-clouds/clusters/nodes/list create mode 100644 gcloud/vmware/private-clouds/dns-forwarding/describe create mode 100644 gcloud/vmware/private-clouds/dns-forwarding/help create mode 100644 gcloud/vmware/private-clouds/dns-forwarding/update create mode 100644 gcloud/vmware/private-clouds/external-addresses/create create mode 100644 gcloud/vmware/private-clouds/external-addresses/delete create mode 100644 gcloud/vmware/private-clouds/external-addresses/describe create mode 100644 gcloud/vmware/private-clouds/external-addresses/help create mode 100644 gcloud/vmware/private-clouds/external-addresses/list create mode 100644 gcloud/vmware/private-clouds/external-addresses/update create mode 100644 gcloud/vmware/private-clouds/logging-servers/create create mode 100644 gcloud/vmware/private-clouds/logging-servers/delete create mode 100644 gcloud/vmware/private-clouds/logging-servers/describe create mode 100644 gcloud/vmware/private-clouds/logging-servers/help create mode 100644 gcloud/vmware/private-clouds/logging-servers/list create mode 100644 gcloud/vmware/private-clouds/logging-servers/update create mode 100644 gcloud/vmware/private-clouds/management-dns-zone-bindings/create create mode 100644 gcloud/vmware/private-clouds/management-dns-zone-bindings/delete create mode 100644 gcloud/vmware/private-clouds/management-dns-zone-bindings/describe create mode 100644 gcloud/vmware/private-clouds/management-dns-zone-bindings/help create mode 100644 gcloud/vmware/private-clouds/management-dns-zone-bindings/list create mode 100644 gcloud/vmware/private-clouds/management-dns-zone-bindings/repair create mode 100644 gcloud/vmware/private-clouds/management-dns-zone-bindings/update diff --git a/gcloud/_version b/gcloud/_version index eab0c91e6..58f6211f4 100644 --- a/gcloud/_version +++ b/gcloud/_version @@ -1,8 +1,8 @@ -Google Cloud SDK 454.0.0 -alpha 2023.11.03 -beta 2023.11.03 +Google Cloud SDK 455.0.0 +alpha 2023.11.10 +beta 2023.11.10 bq 2.0.98 -bundled-python3-unix 3.9.17 -core 2023.11.03 +bundled-python3-unix 3.11.6 +core 2023.11.10 gcloud-crc32c 1.0.0 gsutil 5.27 diff --git a/gcloud/alpha/assured/operations/list b/gcloud/alpha/assured/operations/list index 1720035ec..c2c4c7da0 100644 --- a/gcloud/alpha/assured/operations/list +++ b/gcloud/alpha/assured/operations/list @@ -29,7 +29,7 @@ REQUIRED FLAGS --location=LOCATION The location of the Assured Workloads operations. For a current list of supported LOCATION values, see Assured Workloads locations - (http://cloud/assured-workloads/docs/locations). + (https://cloud.google.com/assured-workloads/docs/locations). --organization=ORGANIZATION The parent organization of the Assured Workloads operations, provided diff --git a/gcloud/alpha/assured/workloads/create b/gcloud/alpha/assured/workloads/create index ae9bd323c..d71906c23 100644 --- a/gcloud/alpha/assured/workloads/create +++ b/gcloud/alpha/assured/workloads/create @@ -60,7 +60,7 @@ REQUIRED FLAGS --location=LOCATION The location of the new Assured Workloads environment. For a current list of supported LOCATION values, see Assured Workloads locations - (http://cloud/assured-workloads/docs/locations). + (https://cloud.google.com/assured-workloads/docs/locations). --organization=ORGANIZATION The parent organization of the new Assured Workloads environment, diff --git a/gcloud/alpha/assured/workloads/list b/gcloud/alpha/assured/workloads/list index c25c20973..43c42ba20 100644 --- a/gcloud/alpha/assured/workloads/list +++ b/gcloud/alpha/assured/workloads/list @@ -29,7 +29,7 @@ REQUIRED FLAGS --location=LOCATION The location of the Assured Workloads environments. For a current list of supported LOCATION values, see Assured Workloads locations - (http://cloud/assured-workloads/docs/locations). + (https://cloud.google.com/assured-workloads/docs/locations). --organization=ORGANIZATION The parent organization of the Assured Workloads environments, provided diff --git a/gcloud/alpha/assured/workloads/violations/list b/gcloud/alpha/assured/workloads/violations/list index b219417c8..44b23600f 100644 --- a/gcloud/alpha/assured/workloads/violations/list +++ b/gcloud/alpha/assured/workloads/violations/list @@ -29,7 +29,7 @@ REQUIRED FLAGS --location=LOCATION The location of the Assured Workloads environments. For a current list of supported LOCATION values, see Assured Workloads locations - (http://cloud/assured-workloads/docs/locations). + (https://cloud.google.com/assured-workloads/docs/locations). --organization=ORGANIZATION The parent organization of the Assured Workloads environments, provided diff --git a/gcloud/alpha/backup-dr/management-servers/create b/gcloud/alpha/backup-dr/management-servers/create index c8948bdb0..7676827da 100644 --- a/gcloud/alpha/backup-dr/management-servers/create +++ b/gcloud/alpha/backup-dr/management-servers/create @@ -53,6 +53,12 @@ POSITIONAL ARGUMENTS REQUIRED FLAGS --network=NETWORK Name of an existing VPC network with private service access configured + in the format - projects//global/networks/. This VPC + network allows the management console to communicate with all + backup/recovery appliances and requires a minimum IP range of /23. This + value cannot be changed after you deploy the management server. If you + don't have private service access, configure one. [Learn more] + (https://cloud.google.com/vpc/docs/configure-private-services-access) OPTIONAL FLAGS --async diff --git a/gcloud/alpha/batch/jobs/submit b/gcloud/alpha/batch/jobs/submit index 908e35ed0..f6cb31e1b 100644 --- a/gcloud/alpha/batch/jobs/submit +++ b/gcloud/alpha/batch/jobs/submit @@ -17,12 +17,17 @@ DESCRIPTION ▪ The active account does not have permission to create the Batch job. EXAMPLES - To submit the job with config.json sample config file and name - projects/foo/locations/us-central1/jobs/bar, run: + To submit the job with config.json or config.yaml sample config file and + name projects/foo/locations/us-central1/jobs/bar, run: $ gcloud alpha batch jobs submit \ projects/foo/locations/us-central1/jobs/bar --config=config.json + or + + $ gcloud alpha batch jobs submit \ + projects/foo/locations/us-central1/jobs/bar --config=config.yaml + To submit the job through stdin with json job config and name projects/foo/locations/us-central1/jobs/bar, run: diff --git a/gcloud/alpha/compute/instance-templates/create b/gcloud/alpha/compute/instance-templates/create index 86e398dbb..0b3fa826c 100644 --- a/gcloud/alpha/compute/instance-templates/create +++ b/gcloud/alpha/compute/instance-templates/create @@ -9,9 +9,7 @@ SYNOPSIS [--boot-disk-provisioned-iops=BOOT_DISK_PROVISIONED_IOPS] [--boot-disk-provisioned-throughput=BOOT_DISK_PROVISIONED_THROUGHPUT] [--boot-disk-size=BOOT_DISK_SIZE] [--boot-disk-type=BOOT_DISK_TYPE] - [--can-ip-forward] [--confidential-compute] - [--confidential-compute-type=CONFIDENTIAL_COMPUTE_TYPE] - [--configure-disk=[PROPERTY=VALUE,...]] + [--can-ip-forward] [--configure-disk=[PROPERTY=VALUE,...]] [--create-disk=[PROPERTY=VALUE,...]] [--description=DESCRIPTION] [--disk=[auto-delete=AUTO-DELETE], [boot=BOOT],[device-name=DEVICE-NAME],[mode=MODE],[name=NAME]] @@ -61,6 +59,8 @@ SYNOPSIS : --boot-disk-kms-keyring=BOOT_DISK_KMS_KEYRING --boot-disk-kms-location=BOOT_DISK_KMS_LOCATION --boot-disk-kms-project=BOOT_DISK_KMS_PROJECT] + [--confidential-compute + | --confidential-compute-type=CONFIDENTIAL_COMPUTE_TYPE] [--custom-cpu=CUSTOM_CPU --custom-memory=CUSTOM_MEMORY : --custom-extensions --custom-vm-type=CUSTOM_VM_TYPE] [--image-project=IMAGE_PROJECT --image=IMAGE @@ -149,27 +149,6 @@ FLAGS If provided, allows the instances to send and receive packets with non-matching destination or source IP addresses. - --confidential-compute - The instance boots with Confidential Computing enabled. Confidential - Computing is based on Secure Encrypted Virtualization (SEV), an AMD - virtualization feature for running confidential instances. - - --confidential-compute-type=CONFIDENTIAL_COMPUTE_TYPE - The instance boots with Confidential Computing enabled. Confidential - Computing can be based on Secure Encrypted Virtualization (SEV) or - Secure Encrypted Virtualization - Secure Nested Paging (SEV-SNP), both - of which are AMD virtualization features for running confidential - instances. Trust Domain eXtension based on Intel virtualization - features for running confidential instances is also supported. - CONFIDENTIAL_COMPUTE_TYPE must be one of: - - SEV - Secure Encrypted Virtualization - SEV_SNP - Secure Encrypted Virtualization - Secure Nested Paging - TDX - Trust Domain eXtension - --configure-disk=[PROPERTY=VALUE,...] This option has effect only when used with --source-instance. It allows you to override how the source-instance's disks are defined in the @@ -984,6 +963,33 @@ FLAGS ▸ provide the argument --boot-disk-kms-project on the command line; ▸ set the property core/project. + At most one of these can be specified: + + --confidential-compute + (DEPRECATED) The instance boots with Confidential Computing enabled. + Confidential Computing is based on Secure Encrypted Virtualization + (SEV), an AMD virtualization feature for running confidential + instances. + + The --confidential-compute flag will soon be deprecated. Please use + --confidential-compute-type=SEV instead + + --confidential-compute-type=CONFIDENTIAL_COMPUTE_TYPE + The instance boots with Confidential Computing enabled. Confidential + Computing can be based on Secure Encrypted Virtualization (SEV) or + Secure Encrypted Virtualization - Secure Nested Paging (SEV-SNP), + both of which are AMD virtualization features for running + confidential instances. Trust Domain eXtension based on Intel + virtualization features for running confidential instances is also + supported. CONFIDENTIAL_COMPUTE_TYPE must be one of: + + SEV + Secure Encrypted Virtualization + SEV_SNP + Secure Encrypted Virtualization - Secure Nested Paging + TDX + Trust Domain eXtension + Custom machine type extensions. --custom-cpu=CUSTOM_CPU diff --git a/gcloud/alpha/compute/instances/bulk/create b/gcloud/alpha/compute/instances/bulk/create index 55d122763..04746f6f0 100644 --- a/gcloud/alpha/compute/instances/bulk/create +++ b/gcloud/alpha/compute/instances/bulk/create @@ -12,9 +12,8 @@ SYNOPSIS [--boot-disk-provisioned-iops=BOOT_DISK_PROVISIONED_IOPS] [--boot-disk-provisioned-throughput=BOOT_DISK_PROVISIONED_THROUGHPUT] [--boot-disk-size=BOOT_DISK_SIZE] [--boot-disk-type=BOOT_DISK_TYPE] - [--can-ip-forward] [--confidential-compute] - [--confidential-compute-type=CONFIDENTIAL_COMPUTE_TYPE] [--count=COUNT] - [--create-disk=[PROPERTY=VALUE,...]] [--description=DESCRIPTION] + [--can-ip-forward] [--count=COUNT] [--create-disk=[PROPERTY=VALUE,...]] + [--description=DESCRIPTION] [--disk=[boot=BOOT], [device-name=DEVICE-NAME],[name=NAME],[scope=SCOPE]] [--enable-display-device] [--[no-]enable-nested-virtualization] @@ -54,6 +53,8 @@ SYNOPSIS : --boot-disk-kms-keyring=BOOT_DISK_KMS_KEYRING --boot-disk-kms-location=BOOT_DISK_KMS_LOCATION --boot-disk-kms-project=BOOT_DISK_KMS_PROJECT] + [--confidential-compute + | --confidential-compute-type=CONFIDENTIAL_COMPUTE_TYPE] [--custom-cpu=CUSTOM_CPU --custom-memory=CUSTOM_MEMORY : --custom-extensions --custom-vm-type=CUSTOM_VM_TYPE] [--image-project=IMAGE_PROJECT --image=IMAGE @@ -189,27 +190,6 @@ OPTIONAL FLAGS If provided, allows the instances to send and receive packets with non-matching destination or source IP addresses. - --confidential-compute - The instance boots with Confidential Computing enabled. Confidential - Computing is based on Secure Encrypted Virtualization (SEV), an AMD - virtualization feature for running confidential instances. - - --confidential-compute-type=CONFIDENTIAL_COMPUTE_TYPE - The instance boots with Confidential Computing enabled. Confidential - Computing can be based on Secure Encrypted Virtualization (SEV) or - Secure Encrypted Virtualization - Secure Nested Paging (SEV-SNP), both - of which are AMD virtualization features for running confidential - instances. Trust Domain eXtension based on Intel virtualization - features for running confidential instances is also supported. - CONFIDENTIAL_COMPUTE_TYPE must be one of: - - SEV - Secure Encrypted Virtualization - SEV_SNP - Secure Encrypted Virtualization - Secure Nested Paging - TDX - Trust Domain eXtension - --count=COUNT Number of Compute Engine virtual machines to create. If specified, and --predefined-names is specified, count must equal the amount of names @@ -787,6 +767,8 @@ OPTIONAL FLAGS The network interface can have both IPv4 and IPv6 addresses IPV4_ONLY The network interface will be assigned IPv4 addresses + IPV6_ONLY + The network interface will be assigned IPv6 addresses --subnet=SUBNET Specifies the subnet that the VM instances are a part of. If --network @@ -899,6 +881,33 @@ OPTIONAL FLAGS ▸ provide the argument --boot-disk-kms-project on the command line; ▸ set the property core/project. + At most one of these can be specified: + + --confidential-compute + (DEPRECATED) The instance boots with Confidential Computing enabled. + Confidential Computing is based on Secure Encrypted Virtualization + (SEV), an AMD virtualization feature for running confidential + instances. + + The --confidential-compute flag will soon be deprecated. Please use + --confidential-compute-type=SEV instead + + --confidential-compute-type=CONFIDENTIAL_COMPUTE_TYPE + The instance boots with Confidential Computing enabled. Confidential + Computing can be based on Secure Encrypted Virtualization (SEV) or + Secure Encrypted Virtualization - Secure Nested Paging (SEV-SNP), + both of which are AMD virtualization features for running + confidential instances. Trust Domain eXtension based on Intel + virtualization features for running confidential instances is also + supported. CONFIDENTIAL_COMPUTE_TYPE must be one of: + + SEV + Secure Encrypted Virtualization + SEV_SNP + Secure Encrypted Virtualization - Secure Nested Paging + TDX + Trust Domain eXtension + Custom machine type extensions. --custom-cpu=CUSTOM_CPU diff --git a/gcloud/alpha/compute/instances/create b/gcloud/alpha/compute/instances/create index d6d3772a5..5a1141236 100644 --- a/gcloud/alpha/compute/instances/create +++ b/gcloud/alpha/compute/instances/create @@ -11,10 +11,9 @@ SYNOPSIS [--boot-disk-provisioned-iops=BOOT_DISK_PROVISIONED_IOPS] [--boot-disk-provisioned-throughput=BOOT_DISK_PROVISIONED_THROUGHPUT] [--boot-disk-size=BOOT_DISK_SIZE] [--boot-disk-type=BOOT_DISK_TYPE] - [--can-ip-forward] [--confidential-compute] - [--confidential-compute-type=CONFIDENTIAL_COMPUTE_TYPE] - [--create-disk=[PROPERTY=VALUE,...]] [--csek-key-file=FILE] - [--deletion-protection] [--description=DESCRIPTION] + [--can-ip-forward] [--create-disk=[PROPERTY=VALUE,...]] + [--csek-key-file=FILE] [--deletion-protection] + [--description=DESCRIPTION] [--disk=[auto-delete=AUTO-DELETE],[boot=BOOT],[device-name=DEVICE-NAME], [force-attach=FORCE-ATTACH],[mode=MODE],[name=NAME],[scope=SCOPE]] [--enable-display-device] [--[no-]enable-nested-virtualization] @@ -69,6 +68,8 @@ SYNOPSIS : --boot-disk-kms-keyring=BOOT_DISK_KMS_KEYRING --boot-disk-kms-location=BOOT_DISK_KMS_LOCATION --boot-disk-kms-project=BOOT_DISK_KMS_PROJECT] + [--confidential-compute + | --confidential-compute-type=CONFIDENTIAL_COMPUTE_TYPE] [--custom-cpu=CUSTOM_CPU --custom-memory=CUSTOM_MEMORY : --custom-extensions --custom-vm-type=CUSTOM_VM_TYPE] [--image-family-scope=IMAGE_FAMILY_SCOPE @@ -213,27 +214,6 @@ FLAGS If provided, allows the instances to send and receive packets with non-matching destination or source IP addresses. - --confidential-compute - The instance boots with Confidential Computing enabled. Confidential - Computing is based on Secure Encrypted Virtualization (SEV), an AMD - virtualization feature for running confidential instances. - - --confidential-compute-type=CONFIDENTIAL_COMPUTE_TYPE - The instance boots with Confidential Computing enabled. Confidential - Computing can be based on Secure Encrypted Virtualization (SEV) or - Secure Encrypted Virtualization - Secure Nested Paging (SEV-SNP), both - of which are AMD virtualization features for running confidential - instances. Trust Domain eXtension based on Intel virtualization - features for running confidential instances is also supported. - CONFIDENTIAL_COMPUTE_TYPE must be one of: - - SEV - Secure Encrypted Virtualization - SEV_SNP - Secure Encrypted Virtualization - Secure Nested Paging - TDX - Trust Domain eXtension - --create-disk=[PROPERTY=VALUE,...] Creates and attaches persistent disks to the instances. @@ -1051,6 +1031,33 @@ FLAGS ▸ provide the argument --boot-disk-kms-project on the command line; ▸ set the property core/project. + At most one of these can be specified: + + --confidential-compute + (DEPRECATED) The instance boots with Confidential Computing enabled. + Confidential Computing is based on Secure Encrypted Virtualization + (SEV), an AMD virtualization feature for running confidential + instances. + + The --confidential-compute flag will soon be deprecated. Please use + --confidential-compute-type=SEV instead + + --confidential-compute-type=CONFIDENTIAL_COMPUTE_TYPE + The instance boots with Confidential Computing enabled. Confidential + Computing can be based on Secure Encrypted Virtualization (SEV) or + Secure Encrypted Virtualization - Secure Nested Paging (SEV-SNP), + both of which are AMD virtualization features for running + confidential instances. Trust Domain eXtension based on Intel + virtualization features for running confidential instances is also + supported. CONFIDENTIAL_COMPUTE_TYPE must be one of: + + SEV + Secure Encrypted Virtualization + SEV_SNP + Secure Encrypted Virtualization - Secure Nested Paging + TDX + Trust Domain eXtension + Custom machine type extensions. --custom-cpu=CUSTOM_CPU diff --git a/gcloud/alpha/compute/instances/create-with-container b/gcloud/alpha/compute/instances/create-with-container index 67791e770..9cb67a254 100644 --- a/gcloud/alpha/compute/instances/create-with-container +++ b/gcloud/alpha/compute/instances/create-with-container @@ -10,9 +10,8 @@ SYNOPSIS [--boot-disk-provisioned-iops=BOOT_DISK_PROVISIONED_IOPS] [--boot-disk-provisioned-throughput=BOOT_DISK_PROVISIONED_THROUGHPUT] [--boot-disk-size=BOOT_DISK_SIZE] [--boot-disk-type=BOOT_DISK_TYPE] - [--can-ip-forward] [--confidential-compute] - [--confidential-compute-type=CONFIDENTIAL_COMPUTE_TYPE] - [--container-arg=CONTAINER_ARG] [--container-command=CONTAINER_COMMAND] + [--can-ip-forward] [--container-arg=CONTAINER_ARG] + [--container-command=CONTAINER_COMMAND] [--container-env=[KEY=VALUE, ...,...]] [--container-env-file=CONTAINER_ENV_FILE] [--container-image=CONTAINER_IMAGE] @@ -56,6 +55,8 @@ SYNOPSIS [--threads-per-core=THREADS_PER_CORE] [--visible-core-count=VISIBLE_CORE_COUNT] [--zone=ZONE] [--address=ADDRESS | --no-address] + [--confidential-compute + | --confidential-compute-type=CONFIDENTIAL_COMPUTE_TYPE] [--custom-cpu=CUSTOM_CPU --custom-memory=CUSTOM_MEMORY : --custom-extensions --custom-vm-type=CUSTOM_VM_TYPE] [--image-project=IMAGE_PROJECT --image=IMAGE @@ -151,27 +152,6 @@ FLAGS If provided, allows the instances to send and receive packets with non-matching destination or source IP addresses. - --confidential-compute - The instance boots with Confidential Computing enabled. Confidential - Computing is based on Secure Encrypted Virtualization (SEV), an AMD - virtualization feature for running confidential instances. - - --confidential-compute-type=CONFIDENTIAL_COMPUTE_TYPE - The instance boots with Confidential Computing enabled. Confidential - Computing can be based on Secure Encrypted Virtualization (SEV) or - Secure Encrypted Virtualization - Secure Nested Paging (SEV-SNP), both - of which are AMD virtualization features for running confidential - instances. Trust Domain eXtension based on Intel virtualization - features for running confidential instances is also supported. - CONFIDENTIAL_COMPUTE_TYPE must be one of: - - SEV - Secure Encrypted Virtualization - SEV_SNP - Secure Encrypted Virtualization - Secure Nested Paging - TDX - Trust Domain eXtension - --container-arg=CONTAINER_ARG Argument to append to container entrypoint or to override container CMD. Each argument must have a separate flag. Arguments are appended in @@ -853,6 +833,33 @@ FLAGS ▸ https://cloud.google.com/vpc/docs/configure-private-google-access ▸ https://cloud.google.com/nat/docs/using-nat + At most one of these can be specified: + + --confidential-compute + (DEPRECATED) The instance boots with Confidential Computing enabled. + Confidential Computing is based on Secure Encrypted Virtualization + (SEV), an AMD virtualization feature for running confidential + instances. + + The --confidential-compute flag will soon be deprecated. Please use + --confidential-compute-type=SEV instead + + --confidential-compute-type=CONFIDENTIAL_COMPUTE_TYPE + The instance boots with Confidential Computing enabled. Confidential + Computing can be based on Secure Encrypted Virtualization (SEV) or + Secure Encrypted Virtualization - Secure Nested Paging (SEV-SNP), + both of which are AMD virtualization features for running + confidential instances. Trust Domain eXtension based on Intel + virtualization features for running confidential instances is also + supported. CONFIDENTIAL_COMPUTE_TYPE must be one of: + + SEV + Secure Encrypted Virtualization + SEV_SNP + Secure Encrypted Virtualization - Secure Nested Paging + TDX + Trust Domain eXtension + Custom machine type extensions. --custom-cpu=CUSTOM_CPU diff --git a/gcloud/alpha/compute/queued-resources/create b/gcloud/alpha/compute/queued-resources/create index a3a838874..151c74f03 100644 --- a/gcloud/alpha/compute/queued-resources/create +++ b/gcloud/alpha/compute/queued-resources/create @@ -13,9 +13,8 @@ SYNOPSIS [--boot-disk-provisioned-iops=BOOT_DISK_PROVISIONED_IOPS] [--boot-disk-provisioned-throughput=BOOT_DISK_PROVISIONED_THROUGHPUT] [--boot-disk-size=BOOT_DISK_SIZE] [--boot-disk-type=BOOT_DISK_TYPE] - [--can-ip-forward] [--confidential-compute] - [--confidential-compute-type=CONFIDENTIAL_COMPUTE_TYPE] [--count=COUNT] - [--create-disk=[PROPERTY=VALUE,...]] [--description=DESCRIPTION] + [--can-ip-forward] [--count=COUNT] [--create-disk=[PROPERTY=VALUE,...]] + [--description=DESCRIPTION] [--disk=[boot=BOOT], [device-name=DEVICE-NAME],[name=NAME],[scope=SCOPE]] [--enable-display-device] [--[no-]enable-nested-virtualization] @@ -54,6 +53,8 @@ SYNOPSIS : --boot-disk-kms-keyring=BOOT_DISK_KMS_KEYRING --boot-disk-kms-location=BOOT_DISK_KMS_LOCATION --boot-disk-kms-project=BOOT_DISK_KMS_PROJECT] + [--confidential-compute + | --confidential-compute-type=CONFIDENTIAL_COMPUTE_TYPE] [--custom-cpu=CUSTOM_CPU --custom-memory=CUSTOM_MEMORY : --custom-extensions --custom-vm-type=CUSTOM_VM_TYPE] [--image-project=IMAGE_PROJECT --image=IMAGE @@ -173,27 +174,6 @@ OPTIONAL FLAGS If provided, allows the instances to send and receive packets with non-matching destination or source IP addresses. - --confidential-compute - The instance boots with Confidential Computing enabled. Confidential - Computing is based on Secure Encrypted Virtualization (SEV), an AMD - virtualization feature for running confidential instances. - - --confidential-compute-type=CONFIDENTIAL_COMPUTE_TYPE - The instance boots with Confidential Computing enabled. Confidential - Computing can be based on Secure Encrypted Virtualization (SEV) or - Secure Encrypted Virtualization - Secure Nested Paging (SEV-SNP), both - of which are AMD virtualization features for running confidential - instances. Trust Domain eXtension based on Intel virtualization - features for running confidential instances is also supported. - CONFIDENTIAL_COMPUTE_TYPE must be one of: - - SEV - Secure Encrypted Virtualization - SEV_SNP - Secure Encrypted Virtualization - Secure Nested Paging - TDX - Trust Domain eXtension - --count=COUNT Number of Compute Engine virtual machines to create. If specified, and --predefined-names is specified, count must equal the amount of names @@ -756,6 +736,8 @@ OPTIONAL FLAGS The network interface can have both IPv4 and IPv6 addresses IPV4_ONLY The network interface will be assigned IPv4 addresses + IPV6_ONLY + The network interface will be assigned IPv6 addresses --subnet=SUBNET Specifies the subnet that the VM instances are a part of. If --network @@ -889,6 +871,33 @@ OPTIONAL FLAGS ▸ provide the argument --boot-disk-kms-project on the command line; ▸ set the property core/project. + At most one of these can be specified: + + --confidential-compute + (DEPRECATED) The instance boots with Confidential Computing enabled. + Confidential Computing is based on Secure Encrypted Virtualization + (SEV), an AMD virtualization feature for running confidential + instances. + + The --confidential-compute flag will soon be deprecated. Please use + --confidential-compute-type=SEV instead + + --confidential-compute-type=CONFIDENTIAL_COMPUTE_TYPE + The instance boots with Confidential Computing enabled. Confidential + Computing can be based on Secure Encrypted Virtualization (SEV) or + Secure Encrypted Virtualization - Secure Nested Paging (SEV-SNP), + both of which are AMD virtualization features for running + confidential instances. Trust Domain eXtension based on Intel + virtualization features for running confidential instances is also + supported. CONFIDENTIAL_COMPUTE_TYPE must be one of: + + SEV + Secure Encrypted Virtualization + SEV_SNP + Secure Encrypted Virtualization - Secure Nested Paging + TDX + Trust Domain eXtension + Custom machine type extensions. --custom-cpu=CUSTOM_CPU diff --git a/gcloud/alpha/compute/queued-resources/list b/gcloud/alpha/compute/queued-resources/list index b9505f0d1..70d5e6c48 100644 --- a/gcloud/alpha/compute/queued-resources/list +++ b/gcloud/alpha/compute/queued-resources/list @@ -4,26 +4,31 @@ NAME SYNOPSIS gcloud alpha compute queued-resources list [NAME ...] - --zones=ZONE,[ZONE,...] [--regexp=REGEXP, -r REGEXP] + [--regexp=REGEXP, -r REGEXP] [--zones=ZONE,[ZONE,...]] [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) gcloud alpha compute queued-resources list displays all Google - Compute Engine queued resources in a project in given zones. + Compute Engine queued resources in a project. + + By default, queued resources from all zones are listed. The results can be + narrowed down using a filter: --filter="zone:( ZONE ... )". EXAMPLES - To list all queued resources in us-central1-b and europe-west1-d zones in a - project in table form, run: + To list all queued resources in a project in table form, run: + + $ gcloud alpha compute queued-resources list + + To list the URIs of all queued resources in a project, run: + + $ gcloud alpha compute queued-resources list --uri + + To list all queued resources in the us-central1-b and europe-west1-d zones, + run: $ gcloud alpha compute queued-resources list \ - --zones=us-central1-b,europe-west1-d - - To list the URIs of all queued resources in us-central1-b zone in a - project, run: - - $ gcloud alpha compute queued-resources list --zones=us-central1-b \ - --uri + --filter="zone:( us-central1-b europe-west1-d )" POSITIONAL ARGUMENTS [NAME ...] @@ -33,10 +38,6 @@ POSITIONAL ARGUMENTS Argument NAME is deprecated. Use --filter="name=( 'NAME' ... )" instead. -REQUIRED FLAGS - --zones=ZONE,[ZONE,...] - Only resources from the given zones are queried. - FLAGS --regexp=REGEXP, -r REGEXP (DEPRECATED) Regular expression to filter the names of the results on. @@ -45,6 +46,9 @@ FLAGS Flag --regexp is deprecated. Use --filter="name~'REGEXP'" instead. + --zones=ZONE,[ZONE,...] + If provided, only resources from the given zones are queried. + LIST COMMAND FLAGS --filter=EXPRESSION Apply a Boolean filter EXPRESSION to each resource item to be listed. diff --git a/gcloud/alpha/compute/tpus/help b/gcloud/alpha/compute/tpus/help index 0ca962d05..71cb6f211 100644 --- a/gcloud/alpha/compute/tpus/help +++ b/gcloud/alpha/compute/tpus/help @@ -34,6 +34,9 @@ GROUPS queued-resources (ALPHA) List, create, delete, and manage Queued Resources. + reservations + (ALPHA) List and manage Reservations. + topologies (ALPHA) List available Cloud TPU topologies. diff --git a/gcloud/alpha/compute/tpus/queued-resources/create b/gcloud/alpha/compute/tpus/queued-resources/create index fc41a8a52..15183ae27 100644 --- a/gcloud/alpha/compute/tpus/queued-resources/create +++ b/gcloud/alpha/compute/tpus/queued-resources/create @@ -100,7 +100,7 @@ REQUIRED FLAGS in this group are specified. --type=TYPE - Type of TPU. TYPE must be one of: v2, v3, v4, v5litepod. + Type of TPU. TYPE must be one of: v2, v3, v4, v5litepod, v5p. This flag argument must be specified if any of the other arguments in this group are specified. diff --git a/gcloud/alpha/compute/tpus/reservations/help b/gcloud/alpha/compute/tpus/reservations/help new file mode 100644 index 000000000..cd8afe724 --- /dev/null +++ b/gcloud/alpha/compute/tpus/reservations/help @@ -0,0 +1,26 @@ +NAME + gcloud alpha compute tpus reservations - list and manage Reservations + +SYNOPSIS + gcloud alpha compute tpus reservations COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) List and manage Reservations. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + list + (ALPHA) List Reservations. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/compute/tpus/reservations/list b/gcloud/alpha/compute/tpus/reservations/list new file mode 100644 index 000000000..87dae4eb2 --- /dev/null +++ b/gcloud/alpha/compute/tpus/reservations/list @@ -0,0 +1,90 @@ +NAME + gcloud alpha compute tpus reservations list - list Reservations + +SYNOPSIS + gcloud alpha compute tpus reservations list [--zone=ZONE] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) List all Reservations associated with a project and location. + +EXAMPLES + To list all Reservations available in zone us-central1-b for project + my-project, run: + + $ gcloud alpha compute tpus reservations list --zone=us-central1-b \ + --project=my-project + +FLAGS + Location resource - Zone of the Reservation. + + To find a list of zones available for Cloud TPUs in your project, run + gcloud alpha compute tpus reservations locations list. This represents a + Cloud resource. (NOTE) Some attributes are not given arguments in this + group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument --zone on the command line with a fully + specified name; + ◆ set the property compute/zone with a fully specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + --zone=ZONE + ID of the location or fully qualified identifier for the location. + + To set the zone attribute: + ▸ provide the argument --zone on the command line; + ▸ set the property compute/zone. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the tpu/v2alpha1 API. The full documentation for this API + can be found at: https://cloud.google.com/tpu/ + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/compute/tpus/tpu-vm/create b/gcloud/alpha/compute/tpus/tpu-vm/create index 3614bffe9..7ad449bfd 100644 --- a/gcloud/alpha/compute/tpus/tpu-vm/create +++ b/gcloud/alpha/compute/tpus/tpu-vm/create @@ -225,7 +225,7 @@ OPTIONAL FLAGS in this group are specified. --type=TYPE - Type of TPU. TYPE must be one of: v2, v3, v4, v5litepod. + Type of TPU. TYPE must be one of: v2, v3, v4, v5litepod, v5p. This flag argument must be specified if any of the other arguments in this group are specified. diff --git a/gcloud/alpha/config/get b/gcloud/alpha/config/get index 5e96eb052..23d5c2663 100644 --- a/gcloud/alpha/config/get +++ b/gcloud/alpha/config/get @@ -1235,6 +1235,20 @@ AVAILABLE PROPERTIES max_retry_delay Max second delay between retriable operations. + multipart_chunksize + Specifies partition size in bytes of each part of a multipart + upload made by the Boto3 client. To calculate the maximum size of a + Boto3 client multipart upload, multiply the multipart_chunk value + by the maximum number of parts the API allows. For AWS S3 this + limit is 10000. Values can be provided either in bytes or as + human-readable values (e.g., "150M" to represent 150 mebibytes). + + multipart_threshold + Files larger than this threshold will be partitioned into parts, + uploaded separately by the Boto3 client, and then combined into a + single object. Otherwise, files smaller than this threshold will be + uploaded by the Boto3 client in a single stream. + parallel_composite_upload_compatibility_check Determines if the GET bucket call should be performed to check if the default storage class and retention period for the destination diff --git a/gcloud/alpha/config/help b/gcloud/alpha/config/help index f1f260997..69af2a584 100644 --- a/gcloud/alpha/config/help +++ b/gcloud/alpha/config/help @@ -1267,6 +1267,20 @@ AVAILABLE PROPERTIES max_retry_delay Max second delay between retriable operations. + multipart_chunksize + Specifies partition size in bytes of each part of a multipart + upload made by the Boto3 client. To calculate the maximum size of a + Boto3 client multipart upload, multiply the multipart_chunk value + by the maximum number of parts the API allows. For AWS S3 this + limit is 10000. Values can be provided either in bytes or as + human-readable values (e.g., "150M" to represent 150 mebibytes). + + multipart_threshold + Files larger than this threshold will be partitioned into parts, + uploaded separately by the Boto3 client, and then combined into a + single object. Otherwise, files smaller than this threshold will be + uploaded by the Boto3 client in a single stream. + parallel_composite_upload_compatibility_check Determines if the GET bucket call should be performed to check if the default storage class and retention period for the destination diff --git a/gcloud/alpha/config/list b/gcloud/alpha/config/list index d2c5896bf..0398a8e47 100644 --- a/gcloud/alpha/config/list +++ b/gcloud/alpha/config/list @@ -1279,6 +1279,20 @@ AVAILABLE PROPERTIES max_retry_delay Max second delay between retriable operations. + multipart_chunksize + Specifies partition size in bytes of each part of a multipart + upload made by the Boto3 client. To calculate the maximum size of a + Boto3 client multipart upload, multiply the multipart_chunk value + by the maximum number of parts the API allows. For AWS S3 this + limit is 10000. Values can be provided either in bytes or as + human-readable values (e.g., "150M" to represent 150 mebibytes). + + multipart_threshold + Files larger than this threshold will be partitioned into parts, + uploaded separately by the Boto3 client, and then combined into a + single object. Otherwise, files smaller than this threshold will be + uploaded by the Boto3 client in a single stream. + parallel_composite_upload_compatibility_check Determines if the GET bucket call should be performed to check if the default storage class and retention period for the destination diff --git a/gcloud/alpha/config/set b/gcloud/alpha/config/set index 3c77607d4..d9a922690 100644 --- a/gcloud/alpha/config/set +++ b/gcloud/alpha/config/set @@ -1282,6 +1282,20 @@ AVAILABLE PROPERTIES max_retry_delay Max second delay between retriable operations. + multipart_chunksize + Specifies partition size in bytes of each part of a multipart + upload made by the Boto3 client. To calculate the maximum size of a + Boto3 client multipart upload, multiply the multipart_chunk value + by the maximum number of parts the API allows. For AWS S3 this + limit is 10000. Values can be provided either in bytes or as + human-readable values (e.g., "150M" to represent 150 mebibytes). + + multipart_threshold + Files larger than this threshold will be partitioned into parts, + uploaded separately by the Boto3 client, and then combined into a + single object. Otherwise, files smaller than this threshold will be + uploaded by the Boto3 client in a single stream. + parallel_composite_upload_compatibility_check Determines if the GET bucket call should be performed to check if the default storage class and retention period for the destination diff --git a/gcloud/alpha/config/unset b/gcloud/alpha/config/unset index b70ad341b..9a8904fd6 100644 --- a/gcloud/alpha/config/unset +++ b/gcloud/alpha/config/unset @@ -1243,6 +1243,20 @@ AVAILABLE PROPERTIES max_retry_delay Max second delay between retriable operations. + multipart_chunksize + Specifies partition size in bytes of each part of a multipart + upload made by the Boto3 client. To calculate the maximum size of a + Boto3 client multipart upload, multiply the multipart_chunk value + by the maximum number of parts the API allows. For AWS S3 this + limit is 10000. Values can be provided either in bytes or as + human-readable values (e.g., "150M" to represent 150 mebibytes). + + multipart_threshold + Files larger than this threshold will be partitioned into parts, + uploaded separately by the Boto3 client, and then combined into a + single object. Otherwise, files smaller than this threshold will be + uploaded by the Boto3 client in a single stream. + parallel_composite_upload_compatibility_check Determines if the GET bucket call should be performed to check if the default storage class and retention period for the destination diff --git a/gcloud/alpha/container/binauthz/attestations/list b/gcloud/alpha/container/binauthz/attestations/list index a67cf1486..be0031699 100644 --- a/gcloud/alpha/container/binauthz/attestations/list +++ b/gcloud/alpha/container/binauthz/attestations/list @@ -4,16 +4,18 @@ NAME SYNOPSIS gcloud alpha container binauthz attestations list - (--attestor=ATTESTOR : --attestor-project=ATTESTOR_PROJECT) - [--artifact-url=ARTIFACT_URL] [--filter=EXPRESSION] [--limit=LIMIT] - [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] - [GCLOUD_WIDE_FLAG ...] + [--artifact-url=ARTIFACT_URL] + [--attestor=ATTESTOR : --attestor-project=ATTESTOR_PROJECT] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) This command lists Binary Authorization attestations for your - project. Command line flags specify which artifact to list the attestations - for. If no artifact is specified, then this lists all URLs with associated - occurrences. + project. Command line flags specify which attestor and artifact to list the + attestations for. If no attestor is specified, this lists all attestations + in the project, which requires the containeranalysis.occurrences.get + permission. If no artifact is specified, then this lists all URLs with + associated occurrences. EXAMPLES List the Occurrence messages for all attestations bound to the passed @@ -29,15 +31,17 @@ EXAMPLES --attestor=projects/foo/attestors/bar \ --artifact-url='gcr.io/foo/example-image@sha256:abcd' -REQUIRED FLAGS +FLAGS + --artifact-url=ARTIFACT_URL + Container URL. May be in the gcr.io/repository/image format, or may + optionally contain the http or https scheme + Attestor resource - The Attestor whose Container Analysis Note will be queried for attestations. Note that the caller must have the containeranalysis.notes.listOccurrences permission on the note being queried. 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. @@ -57,11 +61,6 @@ REQUIRED FLAGS ▸ provide the argument --project on the command line; ▸ set the property core/project. -FLAGS - --artifact-url=ARTIFACT_URL - Container URL. May be in the gcr.io/repository/image format, or may - optionally contain the http or https scheme - LIST COMMAND FLAGS --filter=EXPRESSION Apply a Boolean filter EXPRESSION to each resource item to be listed. diff --git a/gcloud/alpha/container/binauthz/attestations/sign-and-create b/gcloud/alpha/container/binauthz/attestations/sign-and-create index f6e2854a8..b1bb00f96 100644 --- a/gcloud/alpha/container/binauthz/attestations/sign-and-create +++ b/gcloud/alpha/container/binauthz/attestations/sign-and-create @@ -12,8 +12,9 @@ SYNOPSIS --keyversion-project=KEYVERSION_PROJECT) [--dsse-type=DSSE_TYPE; default="application/vnd.dev.cosign.simplesigning.v1+json"] - [--public-key-id-override=PUBLIC_KEY_ID_OVERRIDE] - [--pae-encode-payload | --validate] [GCLOUD_WIDE_FLAG ...] + [--pae-encode-payload] + [--public-key-id-override=PUBLIC_KEY_ID_OVERRIDE] [--validate] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) This command signs and creates a Binary Authorization attestation @@ -122,6 +123,9 @@ OPTIONAL FLAGS --dsse-type=DSSE_TYPE; default="application/vnd.dev.cosign.simplesigning.v1+json" DSSE type used for pae encoding. + --pae-encode-payload + Whether to pae-encode the payload before signing. + --public-key-id-override=PUBLIC_KEY_ID_OVERRIDE If provided, the ID of the public key that will be used to verify the Attestation instead of the default generated one. This ID should match @@ -131,18 +135,9 @@ OPTIONAL FLAGS This parameter is only necessary if the --public-key-id-override flag was provided when this KMS key was added to the Attestor. - exclusive flags - - At most one of these can be specified: - - --pae-encode-payload - Whether to pae-encode the payload before signing. Note: currently - validation is not supported for attestations with pae-encoded - payload. - - --validate - Whether to validate that the Attestation can be verified by the - provided Attestor. + --validate + Whether to validate that the Attestation can be verified by the + provided Attestor. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/container/fleet/create b/gcloud/alpha/container/fleet/create index 6d6d162ee..5da50288f 100644 --- a/gcloud/alpha/container/fleet/create +++ b/gcloud/alpha/container/fleet/create @@ -3,7 +3,10 @@ NAME SYNOPSIS gcloud alpha container fleet create [--async] [--display-name=DISPLAY_NAME] - [--labels=[KEY=VALUE,...]] [GCLOUD_WIDE_FLAG ...] + [--labels=[KEY=VALUE,...]] + [--security-posture=SECURITY_POSTURE + --workload-vulnerability-scanning=WORKLOAD_VULNERABILITY_SCANNING] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) This command can fail for the following reasons: @@ -36,6 +39,26 @@ FLAGS contain only hyphens (-), underscores (_), lowercase characters, and numbers. + Default cluster configurations to apply across the fleet. + + Security posture config. + + --security-posture=SECURITY_POSTURE + To apply standard security posture to clusters in the fleet, + + $ gcloud alpha container fleet create --security-posture=standard + + SECURITY_POSTURE must be one of: disabled, standard. + + --workload-vulnerability-scanning=WORKLOAD_VULNERABILITY_SCANNING + To apply standard vulnerability scanning to clusters in the fleet, + + $ gcloud alpha container fleet create \ + --workload-vulnerability-scanning=standard + + WORKLOAD_VULNERABILITY_SCANNING must be one of: disabled, standard, + enterprise. + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/alpha/container/fleet/identity-service/apply b/gcloud/alpha/container/fleet/identity-service/apply index 5236cb848..f0d893746 100644 --- a/gcloud/alpha/container/fleet/identity-service/apply +++ b/gcloud/alpha/container/fleet/identity-service/apply @@ -1,19 +1,16 @@ NAME - gcloud alpha container fleet identity-service apply - update an Identity - Service Feature Spec + gcloud alpha container fleet identity-service apply - update the Identity + Service Feature SYNOPSIS gcloud alpha container fleet identity-service apply - ([--config=CONFIG : [--membership=MEMBERSHIP : --location=LOCATION]]) + (--fleet-default-member-config=FLEET_DEFAULT_MEMBER_CONFIG + [(--config=CONFIG | --origin=ORIGIN) + : [--membership=MEMBERSHIP : --location=LOCATION]]) [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Applies the authentication configuration to the Identity Service - feature spec for this membership. This configuration is now the "source of - truth" for the cluster and can only be updated by using this command or the - Cloud Console. Any local authentication configuration on the cluster is - overwritten by this configuration, including any local updates made after - you run this command. + (ALPHA) This command updates the Identity Service Feature in a fleet. EXAMPLES To apply an Identity Service configuration to a membership, run: @@ -22,14 +19,31 @@ EXAMPLES --membership=MEMBERSHIP_NAME \ --config=/path/to/identity-service.yaml + To create or modify a fleet-level default membership configuration, run: + + $ gcloud alpha container fleet identity-service apply \ + --fleet-default-member-config=/path/to/identity-service.yaml + + To apply an existing fleet-level default membership configuration to a + membership, run: + + $ gcloud alpha container fleet identity-service apply \ + --origin=fleet --membership=MEMBERSHIP_NAME + REQUIRED FLAGS At least one of these must be specified: - --config=CONFIG - The path to an identity-service.yaml config file. + --fleet-default-member-config=FLEET_DEFAULT_MEMBER_CONFIG + The path to an identity-service.yaml configuration file. - This flag argument must be specified if any of the other arguments in - this group are specified. + Exactly one of these must be specified: + + --config=CONFIG + The path to an identity-service.yaml configuration file. + + --origin=ORIGIN + Applies the fleet-level default membership configuration to a + membership. ORIGIN must be (only one value is supported): fleet. Membership resource - The group of arguments defining a membership. The arguments in this group can be used to specify the attributes of this diff --git a/gcloud/alpha/container/fleet/identity-service/delete b/gcloud/alpha/container/fleet/identity-service/delete index f9822889c..4d53a9e9d 100644 --- a/gcloud/alpha/container/fleet/identity-service/delete +++ b/gcloud/alpha/container/fleet/identity-service/delete @@ -1,6 +1,6 @@ NAME - gcloud alpha container fleet identity-service delete - remove the Identity - Service Feature Spec for the given membership + gcloud alpha container fleet identity-service delete - delete a resource + from the Identity Service Feature SYNOPSIS gcloud alpha container fleet identity-service delete @@ -8,14 +8,19 @@ SYNOPSIS [--membership=MEMBERSHIP : --location=LOCATION] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Removes the Identity Service Feature Spec for the given membership. + (ALPHA) Deletes a resource from the Identity Service Feature. EXAMPLES - To delete an Identity Service configuration for a membership, run: + To delete the Identity Service configuration from a membership, run: $ gcloud alpha container fleet identity-service delete \ --membership=MEMBERSHIP_NAME + To delete the fleet-level default membership configuration, run: + + $ gcloud alpha container fleet identity-service delete \ + --fleet-default-member-config + FLAGS --fleet-default-member-config If specified, deletes the default membership configuration present in diff --git a/gcloud/alpha/container/fleet/identity-service/enable b/gcloud/alpha/container/fleet/identity-service/enable index aeb8bac88..90aad570a 100644 --- a/gcloud/alpha/container/fleet/identity-service/enable +++ b/gcloud/alpha/container/fleet/identity-service/enable @@ -1,5 +1,5 @@ NAME - gcloud alpha container fleet identity-service enable - enable Identity + gcloud alpha container fleet identity-service enable - enable the Identity Service Feature SYNOPSIS @@ -15,6 +15,12 @@ EXAMPLES $ gcloud alpha container fleet identity-service enable + To enable the Identity Service Feature with a fleet-level default + membership configuration, run: + + $ gcloud alpha container fleet identity-service enable \ + --fleet-default-member-config=/path/to/identity-service.yaml + FLAGS --fleet-default-member-config=FLEET_DEFAULT_MEMBER_CONFIG The path to an identity-service.yaml identity configuration file. If diff --git a/gcloud/alpha/container/fleet/identity-service/help b/gcloud/alpha/container/fleet/identity-service/help index 8b88293aa..101f3f160 100644 --- a/gcloud/alpha/container/fleet/identity-service/help +++ b/gcloud/alpha/container/fleet/identity-service/help @@ -18,11 +18,10 @@ COMMANDS COMMAND is one of the following: apply - (ALPHA) Update an Identity Service Feature Spec. + (ALPHA) Update the Identity Service Feature. delete - (ALPHA) Remove the Identity Service Feature Spec for the given - membership. + (ALPHA) Delete a resource from the Identity Service Feature. describe (ALPHA) Prints the status of all clusters with Identity Service @@ -32,7 +31,7 @@ COMMANDS (ALPHA) Disable Identity Service Feature. enable - (ALPHA) Enable Identity Service Feature. + (ALPHA) Enable the Identity Service Feature. NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/container/fleet/mesh/disable b/gcloud/alpha/container/fleet/mesh/disable index d3e413e07..096f62415 100644 --- a/gcloud/alpha/container/fleet/mesh/disable +++ b/gcloud/alpha/container/fleet/mesh/disable @@ -2,7 +2,8 @@ NAME gcloud alpha container fleet mesh disable - disable Service Mesh Feature SYNOPSIS - gcloud alpha container fleet mesh disable [--force] [GCLOUD_WIDE_FLAG ...] + gcloud alpha container fleet mesh disable [--fleet-default-member-config] + [--force] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Disable the Service Mesh Feature in a fleet. @@ -18,6 +19,16 @@ EXAMPLES --fleet-default-member-config FLAGS + --fleet-default-member-config + If specified, deletes the default membership configuration present in + your fleet. + + To delete the fleet-level default Membership configuration present in + your fleet, run: + + $ gcloud alpha container fleet mesh disable \ + --fleet-default-member-config + --force Disable this feature, even if it is currently in use. Force disablement may result in unexpected behavior. diff --git a/gcloud/alpha/container/fleet/mesh/enable b/gcloud/alpha/container/fleet/mesh/enable index a25f76d58..21209cc04 100644 --- a/gcloud/alpha/container/fleet/mesh/enable +++ b/gcloud/alpha/container/fleet/mesh/enable @@ -2,7 +2,9 @@ NAME gcloud alpha container fleet mesh enable - enable Service Mesh Feature SYNOPSIS - gcloud alpha container fleet mesh enable [GCLOUD_WIDE_FLAG ...] + gcloud alpha container fleet mesh enable + [--fleet-default-member-config=FLEET_DEFAULT_MEMBER_CONFIG] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Enable the Service Mesh Feature in a fleet. @@ -18,6 +20,16 @@ EXAMPLES $ gcloud alpha container fleet mesh enable \ --fleet-default-member-config=/path/to/service-mesh.yaml +FLAGS + --fleet-default-member-config=FLEET_DEFAULT_MEMBER_CONFIG + The path to a service-mesh.yaml configuration file. + + To enable the Service Mesh Feature with a fleet-level default + membership configuration, run: + + $ gcloud alpha container fleet mesh enable \ + --fleet-default-member-config=/path/to/service-mesh.yaml + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/alpha/container/fleet/mesh/update b/gcloud/alpha/container/fleet/mesh/update index 0d1b0e893..286153925 100644 --- a/gcloud/alpha/container/fleet/mesh/update +++ b/gcloud/alpha/container/fleet/mesh/update @@ -4,8 +4,9 @@ NAME SYNOPSIS gcloud alpha container fleet mesh update - ([(--control-plane=CONTROL_PLANE --management=MANAGEMENT) - : --membership=MEMBERSHIP + (--fleet-default-member-config=FLEET_DEFAULT_MEMBER_CONFIG + | [(--control-plane=CONTROL_PLANE + --management=MANAGEMENT --origin=ORIGIN) : --membership=MEMBERSHIP | [--memberships=[MEMBERSHIPS,...] : --location=LOCATION]]) [GCLOUD_WIDE_FLAG ...] @@ -23,6 +24,15 @@ EXAMPLES REQUIRED FLAGS Exactly one of these must be specified: + --fleet-default-member-config=FLEET_DEFAULT_MEMBER_CONFIG + The path to a service-mesh.yaml configuration file. + + To enable the Service Mesh Feature with a fleet-level default + membership configuration, run: + + $ gcloud alpha container fleet mesh update \ + --fleet-default-member-config=/path/to/service-mesh.yaml + At least one of these must be specified: --control-plane=CONTROL_PLANE @@ -37,6 +47,10 @@ REQUIRED FLAGS The management mode to update to. MANAGEMENT must be one of: automatic, manual. + --origin=ORIGIN + Changing the origin of the membership. ORIGIN must be (only one + value is supported): fleet. + At most one of these can be specified: --membership=MEMBERSHIP diff --git a/gcloud/alpha/container/fleet/update b/gcloud/alpha/container/fleet/update index 2453daf8e..1061086db 100644 --- a/gcloud/alpha/container/fleet/update +++ b/gcloud/alpha/container/fleet/update @@ -4,6 +4,8 @@ NAME SYNOPSIS gcloud alpha container fleet update [--async] [--display-name=DISPLAY_NAME] [--update-labels=[KEY=VALUE,...]] + [--security-posture=SECURITY_POSTURE + --workload-vulnerability-scanning=WORKLOAD_VULNERABILITY_SCANNING] [--clear-labels | --remove-labels=[KEY,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -38,6 +40,26 @@ FLAGS contain only hyphens (-), underscores (_), lowercase characters, and numbers. + Default cluster configurations to apply across the fleet. + + Security posture config. + + --security-posture=SECURITY_POSTURE + To apply standard security posture to clusters in the fleet, + + $ gcloud alpha container fleet update --security-posture=standard + + SECURITY_POSTURE must be one of: disabled, standard. + + --workload-vulnerability-scanning=WORKLOAD_VULNERABILITY_SCANNING + To apply standard vulnerability scanning to clusters in the fleet, + + $ gcloud alpha container fleet update \ + --workload-vulnerability-scanning=standard + + WORKLOAD_VULNERABILITY_SCANNING must be one of: disabled, standard, + enterprise. + At most one of these can be specified: --clear-labels diff --git a/gcloud/alpha/container/hub/create b/gcloud/alpha/container/hub/create index 1e038706a..219766a99 100644 --- a/gcloud/alpha/container/hub/create +++ b/gcloud/alpha/container/hub/create @@ -3,7 +3,10 @@ NAME SYNOPSIS gcloud alpha container hub create [--async] [--display-name=DISPLAY_NAME] - [--labels=[KEY=VALUE,...]] [GCLOUD_WIDE_FLAG ...] + [--labels=[KEY=VALUE,...]] + [--security-posture=SECURITY_POSTURE + --workload-vulnerability-scanning=WORKLOAD_VULNERABILITY_SCANNING] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) This command can fail for the following reasons: @@ -36,6 +39,26 @@ FLAGS contain only hyphens (-), underscores (_), lowercase characters, and numbers. + Default cluster configurations to apply across the fleet. + + Security posture config. + + --security-posture=SECURITY_POSTURE + To apply standard security posture to clusters in the fleet, + + $ gcloud alpha container hub create --security-posture=standard + + SECURITY_POSTURE must be one of: disabled, standard. + + --workload-vulnerability-scanning=WORKLOAD_VULNERABILITY_SCANNING + To apply standard vulnerability scanning to clusters in the fleet, + + $ gcloud alpha container hub create \ + --workload-vulnerability-scanning=standard + + WORKLOAD_VULNERABILITY_SCANNING must be one of: disabled, standard, + enterprise. + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/alpha/container/hub/identity-service/apply b/gcloud/alpha/container/hub/identity-service/apply index 99ebce912..4fa18f91d 100644 --- a/gcloud/alpha/container/hub/identity-service/apply +++ b/gcloud/alpha/container/hub/identity-service/apply @@ -1,19 +1,16 @@ NAME - gcloud alpha container hub identity-service apply - update an Identity - Service Feature Spec + gcloud alpha container hub identity-service apply - update the Identity + Service Feature SYNOPSIS gcloud alpha container hub identity-service apply - ([--config=CONFIG : [--membership=MEMBERSHIP : --location=LOCATION]]) + (--fleet-default-member-config=FLEET_DEFAULT_MEMBER_CONFIG + [(--config=CONFIG | --origin=ORIGIN) + : [--membership=MEMBERSHIP : --location=LOCATION]]) [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Applies the authentication configuration to the Identity Service - feature spec for this membership. This configuration is now the "source of - truth" for the cluster and can only be updated by using this command or the - Cloud Console. Any local authentication configuration on the cluster is - overwritten by this configuration, including any local updates made after - you run this command. + (ALPHA) This command updates the Identity Service Feature in a fleet. EXAMPLES To apply an Identity Service configuration to a membership, run: @@ -22,14 +19,31 @@ EXAMPLES --membership=MEMBERSHIP_NAME \ --config=/path/to/identity-service.yaml + To create or modify a fleet-level default membership configuration, run: + + $ gcloud alpha container hub identity-service apply \ + --fleet-default-member-config=/path/to/identity-service.yaml + + To apply an existing fleet-level default membership configuration to a + membership, run: + + $ gcloud alpha container hub identity-service apply --origin=fleet \ + --membership=MEMBERSHIP_NAME + REQUIRED FLAGS At least one of these must be specified: - --config=CONFIG - The path to an identity-service.yaml config file. + --fleet-default-member-config=FLEET_DEFAULT_MEMBER_CONFIG + The path to an identity-service.yaml configuration file. - This flag argument must be specified if any of the other arguments in - this group are specified. + Exactly one of these must be specified: + + --config=CONFIG + The path to an identity-service.yaml configuration file. + + --origin=ORIGIN + Applies the fleet-level default membership configuration to a + membership. ORIGIN must be (only one value is supported): fleet. Membership resource - The group of arguments defining a membership. The arguments in this group can be used to specify the attributes of this diff --git a/gcloud/alpha/container/hub/identity-service/delete b/gcloud/alpha/container/hub/identity-service/delete index 6559df3bd..7315e572d 100644 --- a/gcloud/alpha/container/hub/identity-service/delete +++ b/gcloud/alpha/container/hub/identity-service/delete @@ -1,6 +1,6 @@ NAME - gcloud alpha container hub identity-service delete - remove the Identity - Service Feature Spec for the given membership + gcloud alpha container hub identity-service delete - delete a resource from + the Identity Service Feature SYNOPSIS gcloud alpha container hub identity-service delete @@ -8,14 +8,19 @@ SYNOPSIS [--membership=MEMBERSHIP : --location=LOCATION] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Removes the Identity Service Feature Spec for the given membership. + (ALPHA) Deletes a resource from the Identity Service Feature. EXAMPLES - To delete an Identity Service configuration for a membership, run: + To delete the Identity Service configuration from a membership, run: $ gcloud alpha container hub identity-service delete \ --membership=MEMBERSHIP_NAME + To delete the fleet-level default membership configuration, run: + + $ gcloud alpha container hub identity-service delete \ + --fleet-default-member-config + FLAGS --fleet-default-member-config If specified, deletes the default membership configuration present in diff --git a/gcloud/alpha/container/hub/identity-service/enable b/gcloud/alpha/container/hub/identity-service/enable index 7a4efa518..47caaca49 100644 --- a/gcloud/alpha/container/hub/identity-service/enable +++ b/gcloud/alpha/container/hub/identity-service/enable @@ -1,5 +1,5 @@ NAME - gcloud alpha container hub identity-service enable - enable Identity + gcloud alpha container hub identity-service enable - enable the Identity Service Feature SYNOPSIS @@ -15,6 +15,12 @@ EXAMPLES $ gcloud alpha container hub identity-service enable + To enable the Identity Service Feature with a fleet-level default + membership configuration, run: + + $ gcloud alpha container hub identity-service enable \ + --fleet-default-member-config=/path/to/identity-service.yaml + FLAGS --fleet-default-member-config=FLEET_DEFAULT_MEMBER_CONFIG The path to an identity-service.yaml identity configuration file. If diff --git a/gcloud/alpha/container/hub/identity-service/help b/gcloud/alpha/container/hub/identity-service/help index 9f3cea279..63207e8b5 100644 --- a/gcloud/alpha/container/hub/identity-service/help +++ b/gcloud/alpha/container/hub/identity-service/help @@ -17,11 +17,10 @@ COMMANDS COMMAND is one of the following: apply - (ALPHA) Update an Identity Service Feature Spec. + (ALPHA) Update the Identity Service Feature. delete - (ALPHA) Remove the Identity Service Feature Spec for the given - membership. + (ALPHA) Delete a resource from the Identity Service Feature. describe (ALPHA) Prints the status of all clusters with Identity Service @@ -31,7 +30,7 @@ COMMANDS (ALPHA) Disable Identity Service Feature. enable - (ALPHA) Enable Identity Service Feature. + (ALPHA) Enable the Identity Service Feature. NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/container/hub/mesh/disable b/gcloud/alpha/container/hub/mesh/disable index 2a6cf86d4..cc1cc8c37 100644 --- a/gcloud/alpha/container/hub/mesh/disable +++ b/gcloud/alpha/container/hub/mesh/disable @@ -2,7 +2,8 @@ NAME gcloud alpha container hub mesh disable - disable Service Mesh Feature SYNOPSIS - gcloud alpha container hub mesh disable [--force] [GCLOUD_WIDE_FLAG ...] + gcloud alpha container hub mesh disable [--fleet-default-member-config] + [--force] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Disable the Service Mesh Feature in a fleet. @@ -18,6 +19,16 @@ EXAMPLES --fleet-default-member-config FLAGS + --fleet-default-member-config + If specified, deletes the default membership configuration present in + your fleet. + + To delete the fleet-level default Membership configuration present in + your fleet, run: + + $ gcloud alpha container hub mesh disable \ + --fleet-default-member-config + --force Disable this feature, even if it is currently in use. Force disablement may result in unexpected behavior. diff --git a/gcloud/alpha/container/hub/mesh/enable b/gcloud/alpha/container/hub/mesh/enable index 2add1c997..d291f2bbc 100644 --- a/gcloud/alpha/container/hub/mesh/enable +++ b/gcloud/alpha/container/hub/mesh/enable @@ -2,7 +2,9 @@ NAME gcloud alpha container hub mesh enable - enable Service Mesh Feature SYNOPSIS - gcloud alpha container hub mesh enable [GCLOUD_WIDE_FLAG ...] + gcloud alpha container hub mesh enable + [--fleet-default-member-config=FLEET_DEFAULT_MEMBER_CONFIG] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Enable the Service Mesh Feature in a fleet. @@ -18,6 +20,16 @@ EXAMPLES $ gcloud alpha container hub mesh enable \ --fleet-default-member-config=/path/to/service-mesh.yaml +FLAGS + --fleet-default-member-config=FLEET_DEFAULT_MEMBER_CONFIG + The path to a service-mesh.yaml configuration file. + + To enable the Service Mesh Feature with a fleet-level default + membership configuration, run: + + $ gcloud alpha container hub mesh enable \ + --fleet-default-member-config=/path/to/service-mesh.yaml + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/alpha/container/hub/mesh/update b/gcloud/alpha/container/hub/mesh/update index 8f9bef11f..d7bd2d26c 100644 --- a/gcloud/alpha/container/hub/mesh/update +++ b/gcloud/alpha/container/hub/mesh/update @@ -4,8 +4,9 @@ NAME SYNOPSIS gcloud alpha container hub mesh update - ([(--control-plane=CONTROL_PLANE --management=MANAGEMENT) - : --membership=MEMBERSHIP + (--fleet-default-member-config=FLEET_DEFAULT_MEMBER_CONFIG + | [(--control-plane=CONTROL_PLANE + --management=MANAGEMENT --origin=ORIGIN) : --membership=MEMBERSHIP | [--memberships=[MEMBERSHIPS,...] : --location=LOCATION]]) [GCLOUD_WIDE_FLAG ...] @@ -23,6 +24,15 @@ EXAMPLES REQUIRED FLAGS Exactly one of these must be specified: + --fleet-default-member-config=FLEET_DEFAULT_MEMBER_CONFIG + The path to a service-mesh.yaml configuration file. + + To enable the Service Mesh Feature with a fleet-level default + membership configuration, run: + + $ gcloud alpha container hub mesh update \ + --fleet-default-member-config=/path/to/service-mesh.yaml + At least one of these must be specified: --control-plane=CONTROL_PLANE @@ -37,6 +47,10 @@ REQUIRED FLAGS The management mode to update to. MANAGEMENT must be one of: automatic, manual. + --origin=ORIGIN + Changing the origin of the membership. ORIGIN must be (only one + value is supported): fleet. + At most one of these can be specified: --membership=MEMBERSHIP diff --git a/gcloud/alpha/container/hub/update b/gcloud/alpha/container/hub/update index 68d2edd3d..7a5fbebb9 100644 --- a/gcloud/alpha/container/hub/update +++ b/gcloud/alpha/container/hub/update @@ -4,6 +4,8 @@ NAME SYNOPSIS gcloud alpha container hub update [--async] [--display-name=DISPLAY_NAME] [--update-labels=[KEY=VALUE,...]] + [--security-posture=SECURITY_POSTURE + --workload-vulnerability-scanning=WORKLOAD_VULNERABILITY_SCANNING] [--clear-labels | --remove-labels=[KEY,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -38,6 +40,26 @@ FLAGS contain only hyphens (-), underscores (_), lowercase characters, and numbers. + Default cluster configurations to apply across the fleet. + + Security posture config. + + --security-posture=SECURITY_POSTURE + To apply standard security posture to clusters in the fleet, + + $ gcloud alpha container hub update --security-posture=standard + + SECURITY_POSTURE must be one of: disabled, standard. + + --workload-vulnerability-scanning=WORKLOAD_VULNERABILITY_SCANNING + To apply standard vulnerability scanning to clusters in the fleet, + + $ gcloud alpha container hub update \ + --workload-vulnerability-scanning=standard + + WORKLOAD_VULNERABILITY_SCANNING must be one of: disabled, standard, + enterprise. + At most one of these can be specified: --clear-labels diff --git a/gcloud/alpha/dataproc/clusters/create b/gcloud/alpha/dataproc/clusters/create index eb692c365..637a6868e 100644 --- a/gcloud/alpha/dataproc/clusters/create +++ b/gcloud/alpha/dataproc/clusters/create @@ -60,6 +60,8 @@ SYNOPSIS [--image=IMAGE | --image-version=VERSION] [--kerberos-config-file=KERBEROS_CONFIG_FILE | --enable-kerberos --kerberos-root-principal-password-uri=KERBEROS_ROOT_PRINCIPAL_PASSWORD_URI [--kerberos-kms-key=KERBEROS_KMS_KEY : --kerberos-kms-key-keyring=KERBEROS_KMS_KEY_KEYRING --kerberos-kms-key-location=KERBEROS_KMS_KEY_LOCATION --kerberos-kms-key-project=KERBEROS_KMS_KEY_PROJECT]] + [--kms-key=KMS_KEY : --kms-keyring=KMS_KEYRING + --kms-location=KMS_LOCATION --kms-project=KMS_PROJECT] [--single-node | --min-num-workers=MIN_NUM_WORKERS --num-secondary-workers=NUM_SECONDARY_WORKERS --num-workers=NUM_WORKERS @@ -764,6 +766,46 @@ FLAGS line; ▫ set the property core/project. + Key resource - The Cloud KMS (Key Management Service) cryptokey that will + be used to protect the cluster. The 'Compute Engine Service Agent' service + account must hold permission 'Cloud KMS CryptoKey Encrypter/Decrypter'. + The arguments in this group can be used to specify the attributes of this + resource. + + --kms-key=KMS_KEY + ID of the key or fully qualified identifier for the key. + + To set the kms-key attribute: + ▸ provide the argument --kms-key on the command line. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --kms-keyring=KMS_KEYRING + The KMS keyring of the key. + + To set the kms-keyring attribute: + ▸ provide the argument --kms-key on the command line with a fully + specified name; + ▸ provide the argument --kms-keyring on the command line. + + --kms-location=KMS_LOCATION + The Google Cloud location for the key. + + To set the kms-location attribute: + ▸ provide the argument --kms-key on the command line with a fully + specified name; + ▸ provide the argument --kms-location on the command line. + + --kms-project=KMS_PROJECT + The Google Cloud project for the key. + + To set the kms-project attribute: + ▸ provide the argument --kms-key on the command line with a fully + specified name; + ▸ provide the argument --kms-project on the command line; + ▸ set the property core/project. + At most one of these can be specified: --single-node diff --git a/gcloud/alpha/dataproc/workflow-templates/set-managed-cluster b/gcloud/alpha/dataproc/workflow-templates/set-managed-cluster index 5a456fcf9..3fc6479d5 100644 --- a/gcloud/alpha/dataproc/workflow-templates/set-managed-cluster +++ b/gcloud/alpha/dataproc/workflow-templates/set-managed-cluster @@ -44,6 +44,8 @@ SYNOPSIS [--image=IMAGE | --image-version=VERSION] [--kerberos-config-file=KERBEROS_CONFIG_FILE | --enable-kerberos --kerberos-root-principal-password-uri=KERBEROS_ROOT_PRINCIPAL_PASSWORD_URI [--kerberos-kms-key=KERBEROS_KMS_KEY : --kerberos-kms-key-keyring=KERBEROS_KMS_KEY_KEYRING --kerberos-kms-key-location=KERBEROS_KMS_KEY_LOCATION --kerberos-kms-key-project=KERBEROS_KMS_KEY_PROJECT]] + [--kms-key=KMS_KEY : --kms-keyring=KMS_KEYRING + --kms-location=KMS_LOCATION --kms-project=KMS_PROJECT] [--metadata=KEY=VALUE,[KEY=VALUE,...] --scopes=SCOPE,[SCOPE,...] --service-account=SERVICE_ACCOUNT --tags=TAG,[TAG,...] --network=NETWORK | --subnet=SUBNET @@ -519,6 +521,46 @@ FLAGS line; ▫ set the property core/project. + Key resource - The Cloud KMS (Key Management Service) cryptokey that will + be used to protect the cluster. The 'Compute Engine Service Agent' service + account must hold permission 'Cloud KMS CryptoKey Encrypter/Decrypter'. + The arguments in this group can be used to specify the attributes of this + resource. + + --kms-key=KMS_KEY + ID of the key or fully qualified identifier for the key. + + To set the kms-key attribute: + ▸ provide the argument --kms-key on the command line. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --kms-keyring=KMS_KEYRING + The KMS keyring of the key. + + To set the kms-keyring attribute: + ▸ provide the argument --kms-key on the command line with a fully + specified name; + ▸ provide the argument --kms-keyring on the command line. + + --kms-location=KMS_LOCATION + The Google Cloud location for the key. + + To set the kms-location attribute: + ▸ provide the argument --kms-key on the command line with a fully + specified name; + ▸ provide the argument --kms-location on the command line. + + --kms-project=KMS_PROJECT + The Google Cloud project for the key. + + To set the kms-project attribute: + ▸ provide the argument --kms-key on the command line with a fully + specified name; + ▸ provide the argument --kms-project on the command line; + ▸ set the property core/project. + Compute Engine options for Dataproc clusters. --metadata=KEY=VALUE,[KEY=VALUE,...] diff --git a/gcloud/alpha/filestore/instances/create b/gcloud/alpha/filestore/instances/create index bee6b81df..2398b688d 100644 --- a/gcloud/alpha/filestore/instances/create +++ b/gcloud/alpha/filestore/instances/create @@ -104,6 +104,7 @@ REQUIRED FLAGS ▫ 1TB-9.75TB in 256GB increments or its multiples. ▫ 10TB-100TB in 2.5TB increments or its multiples. ▸ ENTERPRISE: 1TB-10TB in 256GB increments or its multiples. + ▸ REGIONAL: 1TB-9.75TB in 256GB increments or its multiples. name The desired logical name of the volume. @@ -193,8 +194,8 @@ REQUIRED FLAGS allocated IP address range is specified, it must be one of the ranges associated with the private service access connection. When specified as a direct CIDR value, it must be a /29 CIDR block for - Basic tier or a /24 CIDR block for High Scale, Zonal or Enterprise - tier in one of the internal IP address ranges + Basic tier or a /24 CIDR block for High Scale, Zonal, Enterprise or + Regional tier in one of the internal IP address ranges (https://www.arin.net/knowledge/address_filters.html) that identifies the range of IP addresses reserved for this instance. For example, 10.0.0.0/29 or 192.168.0.0/24. The range you specify @@ -238,7 +239,7 @@ OPTIONAL FLAGS basic-ssd Performant NFS storage system using SSD. enterprise - ENTERPRISE instances offer the features and availability needed for + Enterprise instances offer the features and availability needed for mission-critical workloads. high-scale-ssd High Scale SSD instance, an alias for ZONAL. Use ZONAL instead @@ -246,6 +247,9 @@ OPTIONAL FLAGS premium Premium Filestore instance, An alias for BASIC_SSD. Use BASIC_SSD instead whenever possible. + regional + Regional instances offer the features and availability needed for + mission-critical workloads. standard Standard Filestore instance, An alias for BASIC_HDD. Use BASIC_HDD instead whenever possible. diff --git a/gcloud/alpha/filestore/instances/update b/gcloud/alpha/filestore/instances/update index 762f17430..34b1e1313 100644 --- a/gcloud/alpha/filestore/instances/update +++ b/gcloud/alpha/filestore/instances/update @@ -154,6 +154,7 @@ FLAGS ▫ 1TB-9.75TB in 256GB increments or its multiples. ▫ 10TB-100TB in 2.5TB increments or its multiples. ▸ ENTERPRISE: 1TB-10TB in 256GB increments or its multiples. + ▸ REGIONAL: 1TB-9.75TB in 256GB increments or its multiples. name The desired logical name of the volume. diff --git a/gcloud/alpha/firestore/databases/delete b/gcloud/alpha/firestore/databases/delete index 2573a53b1..fd6685427 100644 --- a/gcloud/alpha/firestore/databases/delete +++ b/gcloud/alpha/firestore/databases/delete @@ -41,5 +41,7 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. This variant is also available: + + $ gcloud beta firestore databases delete diff --git a/gcloud/alpha/firestore/export b/gcloud/alpha/firestore/export index e13d43565..b0cc47c3c 100644 --- a/gcloud/alpha/firestore/export +++ b/gcloud/alpha/firestore/export @@ -79,14 +79,11 @@ FLAGS --snapshot-time=SNAPSHOT_TIME The version of the database to export. - The timestamp must be rounded to the minute, in the past, and not older - than 5 days. Please choose a reasonable timestamp based on prior - knowledge on how long exports take as data at provided snapshot - timestamp can expire during export. - - If specified, then the exported documents will represent a consistent - view of the database at the provided time. Otherwise, there are no - guarantees about the consistency of the exported documents. + The timestamp must be in the past, rounded to the minute and not older + than earliestVersionTime. If specified, then the exported documents + will represent a consistent view of the database at the provided time. + Otherwise, there are no guarantees about the consistency of the + exported documents. For example, to operate on snapshot time 2023-05-26T10:20:00.00Z: diff --git a/gcloud/alpha/metastore/services/update b/gcloud/alpha/metastore/services/update index 879b1d262..b2b08a69f 100644 --- a/gcloud/alpha/metastore/services/update +++ b/gcloud/alpha/metastore/services/update @@ -76,8 +76,8 @@ FLAGS complete. --data-catalog-sync - A boolean flag to determine whether Dataproc Metastore metadata sync to - Data Catalog should be enabled, false if unspecified. Mutually + Boolean flag to determine whether or not Dataproc Metastore metadata + sync to Data Catalog is enabled, false if unspecified. Mutually exclusive with flag --encryption-kms-key. Cannot be updated if the service uses customer-managed encryption keys. diff --git a/gcloud/alpha/network-security/firewall-endpoints/create b/gcloud/alpha/network-security/firewall-endpoints/create index 93dd654fd..bb55b4fb3 100644 --- a/gcloud/alpha/network-security/firewall-endpoints/create +++ b/gcloud/alpha/network-security/firewall-endpoints/create @@ -6,7 +6,9 @@ SYNOPSIS gcloud alpha network-security firewall-endpoints create (FIREWALL_ENDPOINT : --organization=ORGANIZATION --zone=ZONE) [--async] [--description=DESCRIPTION] [--labels=[KEY=VALUE,...]] - [--max-wait=MAX_WAIT; default="60m"] [GCLOUD_WIDE_FLAG ...] + [--max-wait=MAX_WAIT; default="60m"] + [--target-firewall-attachment=TARGET_FIREWALL_ATTACHMENT] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Create a firewall endpoint. Successful creation of an endpoint @@ -77,6 +79,9 @@ FLAGS specified. See $ gcloud topic datetimes for information on time formats. + --target-firewall-attachment=TARGET_FIREWALL_ATTACHMENT + Target firewall attachment where third party endpoint forwards traffic. + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/alpha/run/jobs/executions/cancel b/gcloud/alpha/run/jobs/executions/cancel index d1c596a8f..3d4905e95 100644 --- a/gcloud/alpha/run/jobs/executions/cancel +++ b/gcloud/alpha/run/jobs/executions/cancel @@ -54,7 +54,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud run jobs executions cancel $ gcloud beta run jobs executions cancel diff --git a/gcloud/alpha/scc/custom-modules/sha/help b/gcloud/alpha/scc/custom-modules/sha/help index 5e9692f75..4499c7ef1 100644 --- a/gcloud/alpha/scc/custom-modules/sha/help +++ b/gcloud/alpha/scc/custom-modules/sha/help @@ -40,6 +40,9 @@ COMMANDS (ALPHA) List the details of Security Health Analytics custom modules with effective enablement states. + simulate + (ALPHA) Validates a Security Health Analytics custom module. + test (ALPHA) Test a Security Health Analytics custom module. diff --git a/gcloud/alpha/scc/custom-modules/sha/simulate b/gcloud/alpha/scc/custom-modules/sha/simulate new file mode 100644 index 000000000..5d48e339e --- /dev/null +++ b/gcloud/alpha/scc/custom-modules/sha/simulate @@ -0,0 +1,83 @@ +NAME + gcloud alpha scc custom-modules sha simulate - validates a Security Health + Analytics custom module + +SYNOPSIS + gcloud alpha scc custom-modules sha simulate + --custom-config-from-file=CUSTOM_CONFIG_FROM_FILE + --resource-from-file=RESOURCE_FROM_FILE + (--folder=FOLDER | --organization=ORGANIZATION | --project=PROJECT) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Validates a given Security Health Analytics custom module and + resource. + +EXAMPLES + To validate a Security Health Analytics custom module against a custom + resource for organization 123, run: + + $ gcloud alpha scc custom-modules sha simulate \ + --organization=organizations/123 \ + --custom-config-from-file=/tmp/custom_config.yaml \ + --resource-from-file=/tmp/resource.yaml + + To validate a Security Health Analytics custom module against a custom + resource for folder 456, run: + + $ gcloud alpha scc custom-modules sha simulate \ + --folder=folders/456 \ + --custom-config-from-file=/tmp/custom_config.yaml \ + --resource-from-file=/tmp/resource.yaml + + To validate a Security Health Analytics custom module against a custom + resource for project 789, run: + + $ gcloud alpha scc custom-modules sha simulate \ + --project=projects/789 \ + --custom-config-from-file=/tmp/custom_config.yaml \ + --resource-from-file=/tmp/resource.yaml + +REQUIRED FLAGS + --custom-config-from-file=CUSTOM_CONFIG_FROM_FILE + Path to a YAML file that contains the configuration for the Security + Health Analytics custom module. + + --resource-from-file=RESOURCE_FROM_FILE + Path to a YAML file that contains the resource data to validate the + Security Health Analytics custom module against. + + Exactly one of these must be specified: + + --folder=FOLDER + Folder that will own the Security Health Analytics custom module. + Formatted as folders/456 or just 456. + + --organization=ORGANIZATION + Organization that will own the Security Health Analytics custom + module. Formatted as organizations/123 or just 123. + + --project=PROJECT + ID or number of the project that will own the Security Health + Analytics custom module. Formatted as projects/789 or just 789. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the securitycenter/v1 API. The full documentation for + this API can be found at: https://cloud.google.com/security-command-center + +NOTES + This command is currently in alpha and might change without notice. If this + command fails 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 scc custom-modules sha simulate + diff --git a/gcloud/alpha/sql/instances/create b/gcloud/alpha/sql/instances/create index d817f9d2d..049d2ceb0 100644 --- a/gcloud/alpha/sql/instances/create +++ b/gcloud/alpha/sql/instances/create @@ -309,6 +309,10 @@ FLAGS production Production updates are stable and recommended for applications in production. + week5 + week5 updates release after the production updates. Use the week5 + channel to receive a 5 week advance notification about the upcoming + maintenance, so you can prepare your application for the release. --maintenance-window-day=MAINTENANCE_WINDOW_DAY Day of week for maintenance window, in UTC time zone. diff --git a/gcloud/alpha/sql/instances/list b/gcloud/alpha/sql/instances/list index 4af9d16ab..2a4be822d 100644 --- a/gcloud/alpha/sql/instances/list +++ b/gcloud/alpha/sql/instances/list @@ -3,8 +3,9 @@ NAME project SYNOPSIS - gcloud alpha sql instances list [--show-edition] [--filter=EXPRESSION] - [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + gcloud alpha sql instances list [--show-edition] + [--show-sql-network-architecture] [--filter=EXPRESSION] [--limit=LIMIT] + [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -15,6 +16,12 @@ FLAGS --show-edition Show the edition field. + --show-sql-network-architecture + Show the instance's current SqlNetworkArchitecture backend in addition + to the default output list. An instance could use either the old or new + network architecture. The new network architecture offers better + isolation, reliability, and faster new feature adoption. + LIST COMMAND FLAGS --filter=EXPRESSION Apply a Boolean filter EXPRESSION to each resource item to be listed. diff --git a/gcloud/alpha/sql/instances/patch b/gcloud/alpha/sql/instances/patch index 29c12d912..03efc50fb 100644 --- a/gcloud/alpha/sql/instances/patch +++ b/gcloud/alpha/sql/instances/patch @@ -44,6 +44,7 @@ SYNOPSIS [--storage-auto-increase-limit=STORAGE_AUTO_INCREASE_LIMIT] [--storage-size=STORAGE_SIZE] [--threads-per-core=THREADS_PER_CORE] [--tier=TIER, -t TIER] [--update-labels=[KEY=VALUE,...]] + [--upgrade-sql-network-architecture] [--allowed-psc-projects=PROJECT,[PROJECT,...] | --clear-allowed-psc-projects] [--authorized-gae-apps=APP,[APP,...] | --clear-gae-apps] @@ -247,6 +248,10 @@ FLAGS production Production updates are stable and recommended for applications in production. + week5 + week5 updates release after the production updates. Use the week5 + channel to receive a 5 week advance notification about the upcoming + maintenance, so you can prepare your application for the release. --maintenance-version=MAINTENANCE_VERSION The desired maintenance version of the instance. @@ -388,6 +393,11 @@ FLAGS contain only hyphens (-), underscores (_), lowercase characters, and numbers. + --upgrade-sql-network-architecture + Upgrade from old network architecture to new network architecture. The + new network architecture offers better isolation, reliability, and + faster new feature adoption. + At most one of these can be specified: --allowed-psc-projects=PROJECT,[PROJECT,...] diff --git a/gcloud/alpha/storage/buckets/create b/gcloud/alpha/storage/buckets/create index 0c15eca53..4e6153cdf 100644 --- a/gcloud/alpha/storage/buckets/create +++ b/gcloud/alpha/storage/buckets/create @@ -8,7 +8,7 @@ SYNOPSIS -k DEFAULT_ENCRYPTION_KEY] [--default-storage-class=DEFAULT_STORAGE_CLASS, -c DEFAULT_STORAGE_CLASS, -s DEFAULT_STORAGE_CLASS] - [--location=LOCATION, -l LOCATION] + [--enable-per-object-retention] [--location=LOCATION, -l LOCATION] [--[no-]pap, --[no-]public-access-prevention] [--placement=REGION,REGION] [--recovery-point-objective=SETTING, --rpo=SETTING] @@ -57,6 +57,10 @@ FLAGS If not specified, the default storage class used by Cloud Storage is "Standard". + --enable-per-object-retention + Enables each object in the bucket to have its own retention settings, + which prevents deletion until stored for a specific length of time. + --location=LOCATION, -l LOCATION Location (https://cloud.google.com/storage/docs/locations) for the bucket. If not specified, the location used by Cloud Storage is us. A diff --git a/gcloud/alpha/storage/cp b/gcloud/alpha/storage/cp index efc64d7b5..e69803c45 100644 --- a/gcloud/alpha/storage/cp +++ b/gcloud/alpha/storage/cp @@ -28,7 +28,9 @@ SYNOPSIS | --remove-custom-metadata=[METADATA_KEYS,...] --update-custom-metadata=[CUSTOM_METADATA_KEYS_AND_VALUES,...]] [--if-generation-match=GENERATION - --if-metageneration-match=METAGENERATION] [GCLOUD_WIDE_FLAG ...] + --if-metageneration-match=METAGENERATION] + [--retain-until=DATETIME --retention-mode=RETENTION_MODE] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Copy data between your local file system and the cloud, within the @@ -345,6 +347,16 @@ PRECONDITION FLAGS Execute only if the metageneration matches the metageneration of the requested object. +RETENTION FLAGS + --retain-until=DATETIME + Ensures the destination object is retained until the specified time in + RFC 3339 format. + + --retention-mode=RETENTION_MODE + Sets the destination object retention mode to either "Locked" or + "Unlocked". When retention mode is "Locked", the retain until time can + only be increased. RETENTION_MODE must be one of: Locked, Unlocked. + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/alpha/storage/insights/dataset-configs/create b/gcloud/alpha/storage/insights/dataset-configs/create new file mode 100644 index 000000000..c35d26e67 --- /dev/null +++ b/gcloud/alpha/storage/insights/dataset-configs/create @@ -0,0 +1,129 @@ +NAME + gcloud alpha storage insights dataset-configs create - create a new dataset + config for insights + +SYNOPSIS + gcloud alpha storage insights dataset-configs create DATASET_CONFIG_NAME + --location=LOCATION --organization=SOURCE_ORG_NUMBER + --retention-period-days=RETENTION_DAYS + (--source-projects=[SOURCE_PROJECT_NUMBERS,...] + | --source-projects-file=SOURCE_PROJECT_NUMBERS_IN_FILE) + [--auto-add-new-buckets] [--description=DESCRIPTION] + [--identity=IDENTITY_TYPE; default="IDENTITY_TYPE_PER_CONFIG"] + [--exclude-bucket-names=[BUCKETS_NAMES,...] + --exclude-bucket-prefix-regexes=[BUCKETS_REGEXES,...] + | --include-bucket-names=[BUCKETS_NAMES,...] + --include-bucket-prefix-regexes=[BUCKETS_REGEXES,...]] + [--exclude-source-locations=[LIST_OF_SOURCE_LOCATIONS,...] + | --include-source-locations=[LIST_OF_SOURCE_LOCATIONS,...]] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Create a new dataset config for insights. + +EXAMPLES + To create a dataset config with config name as "my-config" in location + "us-central1" and project numbers "123456" and "456789" belonging to + organization number "54321": + + $ gcloud alpha storage insights dataset-configs create my-config \ + --location=us-central1 --source-projects=123456,456789 \ + --organization=54321 --retention-period-days=1 + + To create a dataset config that automatically adds new buckets into config: + + $ gcloud alpha storage insights dataset-configs create my-config \ + --location=us-central1 --source-projects=123456,456789 \ + --organization=54321 --auto-add-new-buckets \ + --retention-period-days=1 + +POSITIONAL ARGUMENTS + DATASET_CONFIG_NAME + Provide human readable config name. + +REQUIRED FLAGS + --location=LOCATION + Provide location of the dataset config. + + --organization=SOURCE_ORG_NUMBER + Provide the source organization number. + + --retention-period-days=RETENTION_DAYS + Provide retention period for the config. + + List of source project numbers or the file containing list of project + numbers. + + Exactly one of these must be specified: + + --source-projects=[SOURCE_PROJECT_NUMBERS,...] + List of source project numbers. + + --source-projects-file=SOURCE_PROJECT_NUMBERS_IN_FILE + CSV formatted file containing source project numbers, one per line. + +OPTIONAL FLAGS + --auto-add-new-buckets + Automatically include any new buckets created if they satisfy criteria + defined in config settings. + + --description=DESCRIPTION + Description for dataset config. + + --identity=IDENTITY_TYPE; default="IDENTITY_TYPE_PER_CONFIG" + The type of service account used in the dataset config. IDENTITY_TYPE + must be one of: IDENTITY_TYPE_PER_CONFIG, IDENTITY_TYPE_PER_PROJECT. + + Specify the list of buckets to be included or excluded, both a list of + bucket names and prefix regexes can be specified for either include or + exclude buckets. + + At most one of these can be specified: + + Specify the list of buckets to be excluded. + + --exclude-bucket-names=[BUCKETS_NAMES,...] + List of bucket names to be excluded. + + --exclude-bucket-prefix-regexes=[BUCKETS_REGEXES,...] + List of bucket prefix regexes to be excluded. Allowed regex + patterns are similar to those for the + --include-bucket-prefix-regexes flag. + + Specify the list of buckets to be included. + + --include-bucket-names=[BUCKETS_NAMES,...] + List of bucket names be included. + + --include-bucket-prefix-regexes=[BUCKETS_REGEXES,...] + List of bucket prefix regexes to be included. The dataset config + will include all the buckets that match with the prefix regex. + Examples of allowed prefix regex patterns can be testbucket*, + testbucket.*foo, testb.+foo* . It should follow syntax specified in + google/re2 on GitHub. + + Specify the list of locations for source projects to be included or + excluded. + + At most one of these can be specified: + + --exclude-source-locations=[LIST_OF_SOURCE_LOCATIONS,...] + List of locations for projects to be excluded. + + --include-source-locations=[LIST_OF_SOURCE_LOCATIONS,...] + List of locations for projects to be included. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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/storage/insights/dataset-configs/create-link b/gcloud/alpha/storage/insights/dataset-configs/create-link new file mode 100644 index 000000000..65ff0ff04 --- /dev/null +++ b/gcloud/alpha/storage/insights/dataset-configs/create-link @@ -0,0 +1,70 @@ +NAME + gcloud alpha storage insights dataset-configs create-link - create a link + to a BigQuery instance + +SYNOPSIS + gcloud alpha storage insights dataset-configs create-link + (DATASET_CONFIG : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Create link to the customer BigQuery instance for insights dataset + config. + +EXAMPLES + To create a link to the customer BigQuery instance for config name: + "my-config" in location "us-central1": + + $ gcloud alpha storage insights dataset-configs create-link \ + my-config --location=us-central1 + + To create a link for the same dataset config with fully specified name: + + $ gcloud alpha storage insights dataset-configs create-link \ + projects/foo/locations/us-central1/datasetConfigs/my-config + +POSITIONAL ARGUMENTS + Dataset config resource - The Dataset config to create link. The arguments + in this group can be used to specify the attributes of this resource. + (NOTE) Some attributes are not given arguments in this group but can be + set in other ways. + + To set the project attribute: + ◆ provide the argument dataset_config on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + DATASET_CONFIG + ID of the dataset-config or fully qualified identifier for the + dataset-config. + + To set the dataset-config attribute: + ▸ provide the argument dataset_config on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Insights supported Google Cloud location for the dataset-config. + + To set the location attribute: + ▸ provide the argument dataset_config on the command line with a + fully specified name; + ▸ provide the argument --location on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails 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/storage/insights/dataset-configs/delete b/gcloud/alpha/storage/insights/dataset-configs/delete new file mode 100644 index 000000000..e04f55bef --- /dev/null +++ b/gcloud/alpha/storage/insights/dataset-configs/delete @@ -0,0 +1,87 @@ +NAME + gcloud alpha storage insights dataset-configs delete - delete dataset + config for insights + +SYNOPSIS + gcloud alpha storage insights dataset-configs delete + (DATASET_CONFIG : --location=LOCATION) [--auto-delete-link] [--force] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Delete an insights dataset config. + +EXAMPLES + To delete a dataset config with config name "my-config" in location + "us-central1": + + $ gcloud alpha storage insights dataset-configs delete my-config \ + --location=us-central1 + + To delete the same dataset config with fully specified name: + + $gcloud alpha storage insights dataset-configs delete projects/foo/locations/us-central1/datasetConfigs/my-config + + To delete the same dataset config and unlink it from the BigQuery instance: + + $ gcloud alpha storage insights dataset-configs delete my-config \ + --location=us-central1 --auto-delete-link + + To delete the same dataset config without taking user consent: + + $ gcloud alpha storage insights dataset-configs delete my-config \ + --location=us-central1 --auto-delete-link --force + +POSITIONAL ARGUMENTS + Dataset config resource - The Dataset config to delete. The arguments in + this group can be used to specify the attributes of this resource. (NOTE) + Some attributes are not given arguments in this group but can be set in + other ways. + + To set the project attribute: + ◆ provide the argument dataset_config on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + DATASET_CONFIG + ID of the dataset-config or fully qualified identifier for the + dataset-config. + + To set the dataset-config attribute: + ▸ provide the argument dataset_config on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Insights supported Google Cloud location for the dataset-config. + + To set the location attribute: + ▸ provide the argument dataset_config on the command line with a + fully specified name; + ▸ provide the argument --location on the command line. + +FLAGS + --auto-delete-link + Delete the BigQuery instance links before the config gets deleted + explicitly. + + --force + Force delete the config by skipping the consent. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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/storage/insights/dataset-configs/delete-link b/gcloud/alpha/storage/insights/dataset-configs/delete-link new file mode 100644 index 000000000..e015ce150 --- /dev/null +++ b/gcloud/alpha/storage/insights/dataset-configs/delete-link @@ -0,0 +1,69 @@ +NAME + gcloud alpha storage insights dataset-configs delete-link - delete a link + to a BigQuery instance + +SYNOPSIS + gcloud alpha storage insights dataset-configs delete-link + (DATASET_CONFIG : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Delete a link to a BigQuery instance. + +EXAMPLES + To unlink a dataset config with config name "my-config" in location + "us-central1": + + $ gcloud alpha storage insights dataset-configs delete-link \ + my-config --location=us-central1 + + To delete a link for the same dataset config with fully specified name: + + $ gcloud alpha storage insights dataset-configs delete-link \ + projects/foo/locations/us-central1/datasetConfigs/my-config + +POSITIONAL ARGUMENTS + Dataset config resource - The Dataset config to delete link. The arguments + in this group can be used to specify the attributes of this resource. + (NOTE) Some attributes are not given arguments in this group but can be + set in other ways. + + To set the project attribute: + ◆ provide the argument dataset_config on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + DATASET_CONFIG + ID of the dataset-config or fully qualified identifier for the + dataset-config. + + To set the dataset-config attribute: + ▸ provide the argument dataset_config on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Insights supported Google Cloud location for the dataset-config. + + To set the location attribute: + ▸ provide the argument dataset_config on the command line with a + fully specified name; + ▸ provide the argument --location on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails 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/storage/insights/dataset-configs/describe b/gcloud/alpha/storage/insights/dataset-configs/describe new file mode 100644 index 000000000..098bf3e3c --- /dev/null +++ b/gcloud/alpha/storage/insights/dataset-configs/describe @@ -0,0 +1,69 @@ +NAME + gcloud alpha storage insights dataset-configs describe - describe dataset + config for insights + +SYNOPSIS + gcloud alpha storage insights dataset-configs describe + (DATASET_CONFIG : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Describe the insights dataset config. + +EXAMPLES + To describe a dataset config with config name "my-config" in location + "us-central1": + + $ gcloud alpha storage insights dataset-configs describe my-config \ + --location=us-central1 + + To describe the same dataset config with fully specified name: + + $ gcloud alpha storage insights dataset-configs describe \ + projects/foo/locations/us-central1/datasetConfigs/my-config + +POSITIONAL ARGUMENTS + Dataset config resource - The Dataset 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 dataset_config on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + DATASET_CONFIG + ID of the dataset-config or fully qualified identifier for the + dataset-config. + + To set the dataset-config attribute: + ▸ provide the argument dataset_config on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Insights supported Google Cloud location for the dataset-config. + + To set the location attribute: + ▸ provide the argument dataset_config on the command line with a + fully specified name; + ▸ provide the argument --location on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails 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/storage/insights/dataset-configs/help b/gcloud/alpha/storage/insights/dataset-configs/help new file mode 100644 index 000000000..e7f6f7edd --- /dev/null +++ b/gcloud/alpha/storage/insights/dataset-configs/help @@ -0,0 +1,47 @@ +NAME + gcloud alpha storage insights dataset-configs - manage Cloud Storage + insights dataset configurations + +SYNOPSIS + gcloud alpha storage insights dataset-configs COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Manage Cloud Storage insights dataset configurations. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + create + (ALPHA) Create a new dataset config for insights. + + create-link + (ALPHA) Create a link to a BigQuery instance. + + delete + (ALPHA) Delete dataset config for insights. + + delete-link + (ALPHA) Delete a link to a BigQuery instance. + + describe + (ALPHA) Describe dataset config for insights. + + list + (ALPHA) List returns all the insights dataset configs for given + location. + + update + (ALPHA) Updates a dataset config for insights. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails 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/storage/insights/dataset-configs/list b/gcloud/alpha/storage/insights/dataset-configs/list new file mode 100644 index 000000000..6cfd9998c --- /dev/null +++ b/gcloud/alpha/storage/insights/dataset-configs/list @@ -0,0 +1,82 @@ +NAME + gcloud alpha storage insights dataset-configs list - list returns all the + insights dataset configs for given location + +SYNOPSIS + gcloud alpha storage insights dataset-configs list [--location=LOCATION] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) List Cloud storage insights dataset configs. + +EXAMPLES + List all dataset configs in all locations: + + $ gcloud alpha storage insights dataset-configs list + + List all dataset configs for location "us-central1": + + $ gcloud alpha storage insights dataset-configs list \ + --location=us-central1 + + List all dataset configs with a page size of "20": + + $ gcloud alpha storage insights dataset-configs list \ + --location=us-central1 --page-size=20 + + List all dataset configs with JSON formatting: + + $ gcloud alpha storage insights dataset-configs list \ + --location=us-central1 --format=json + +FLAGS + --location=LOCATION + Provide location of the dataset config. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/storage/insights/dataset-configs/update b/gcloud/alpha/storage/insights/dataset-configs/update new file mode 100644 index 000000000..a21cb1dd7 --- /dev/null +++ b/gcloud/alpha/storage/insights/dataset-configs/update @@ -0,0 +1,84 @@ +NAME + gcloud alpha storage insights dataset-configs update - updates a dataset + config for insights + +SYNOPSIS + gcloud alpha storage insights dataset-configs update + (DATASET_CONFIG : --location=LOCATION) [--description=DESCRIPTION] + [--retention-period-days=RETENTION_DAYS] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Update a dataset config for insights. + +EXAMPLES + To update the description for a dataset config "my-config" in location + "us-central1": + + $ gcloud alpha storage insights dataset-configs update my-config \ + --location=us-central1 \ + --description="a user provided description" + + To update the same dataset config with fully specified name: + + $ gcloud alpha storage insights dataset-configs update \ + projects/foo/locations/us-central1/datasetConfigs/my-config + + To update the retention period days for the dataset config "my-config" in + location "us-central1": + + $ gcloud alpha storage insights dataset-configs update my-config \ + --location=us-central1 --retention-period-days=20 + +POSITIONAL ARGUMENTS + Dataset config resource - The Dataset config 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 dataset_config on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + DATASET_CONFIG + ID of the dataset-config or fully qualified identifier for the + dataset-config. + + To set the dataset-config attribute: + ▸ provide the argument dataset_config on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Insights supported Google Cloud location for the dataset-config. + + To set the location attribute: + ▸ provide the argument dataset_config on the command line with a + fully specified name; + ▸ provide the argument --location on the command line. + +FLAGS + --description=DESCRIPTION + Description for dataset config. + + --retention-period-days=RETENTION_DAYS + Provide retention period for the config. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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/storage/insights/help b/gcloud/alpha/storage/insights/help index 597a7b4c7..fea20b83f 100644 --- a/gcloud/alpha/storage/insights/help +++ b/gcloud/alpha/storage/insights/help @@ -15,9 +15,15 @@ GCLOUD WIDE FLAGS GROUPS GROUP is one of the following: + dataset-configs + (ALPHA) Manage Cloud Storage insights dataset configurations. + inventory-reports (ALPHA) Manage Cloud Storage inventory report configurations. + operations + (ALPHA) Manage insights operations. + NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct diff --git a/gcloud/alpha/storage/insights/operations/cancel b/gcloud/alpha/storage/insights/operations/cancel new file mode 100644 index 000000000..f71660679 --- /dev/null +++ b/gcloud/alpha/storage/insights/operations/cancel @@ -0,0 +1,39 @@ +NAME + gcloud alpha storage insights operations cancel - cancel an insights + operation + +SYNOPSIS + gcloud alpha storage insights operations cancel OPERATION_NAME + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Cancel an insights operation. Since operations are asynchronous, + this request is best effort and may fail in cases such as when the + operation is already complete. + +EXAMPLES + To cancel the operation "12345" in "us-central1" for the project + "my-project", run: + + $ gcloud alpha storage insights operations cancel \ + projects/my-project/locations/us-central1/operations/12345 + +POSITIONAL ARGUMENTS + OPERATION_NAME + The operation name in the format + "projects/PROJECT/locations/LOCATION/operations/OPERATION_ID". + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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/storage/insights/operations/describe b/gcloud/alpha/storage/insights/operations/describe new file mode 100644 index 000000000..c941ee1f4 --- /dev/null +++ b/gcloud/alpha/storage/insights/operations/describe @@ -0,0 +1,37 @@ +NAME + gcloud alpha storage insights operations describe - describe an insights + operation + +SYNOPSIS + gcloud alpha storage insights operations describe OPERATION_NAME + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Get details about an insights operation. + +EXAMPLES + To describe the operation "12345" in "us-central1" for the project + "my-project", run: + + $ gcloud alpha storage insights operations describe \ + projects/my-project/locations/us-central1/operations/12345 + +POSITIONAL ARGUMENTS + OPERATION_NAME + The operation name in the format + "projects/PROJECT/locations/LOCATION/operations/OPERATION_ID". + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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/storage/insights/operations/help b/gcloud/alpha/storage/insights/operations/help new file mode 100644 index 000000000..c3cddf7e3 --- /dev/null +++ b/gcloud/alpha/storage/insights/operations/help @@ -0,0 +1,32 @@ +NAME + gcloud alpha storage insights operations - manage insights operations + +SYNOPSIS + gcloud alpha storage insights operations COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Manage insights operations. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + cancel + (ALPHA) Cancel an insights operation. + + describe + (ALPHA) Describe an insights operation. + + list + (ALPHA) List insights operations. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/storage/insights/operations/list b/gcloud/alpha/storage/insights/operations/list new file mode 100644 index 000000000..c675ece61 --- /dev/null +++ b/gcloud/alpha/storage/insights/operations/list @@ -0,0 +1,73 @@ +NAME + gcloud alpha storage insights operations list - list insights operations + +SYNOPSIS + gcloud alpha storage insights operations list PARENT_RESOURCE_NAME + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) List storage operations. + +EXAMPLES + To list all operations in "us-central1" for the project "my-project", run: + + $ gcloud alpha storage insights operations list \ + projects/my-project/locations/us-central1 + + To list operations in JSON format, run: + + $ gcloud alpha storage insights operations list \ + projects/my-project/locations/us-central1 --format=json + +POSITIONAL ARGUMENTS + PARENT_RESOURCE_NAME + The operation parent resource in the format + ""projects/PROJECT/locations/LOCATION". + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails 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/storage/mv b/gcloud/alpha/storage/mv index 1d79868f9..1c0024d4e 100644 --- a/gcloud/alpha/storage/mv +++ b/gcloud/alpha/storage/mv @@ -27,7 +27,9 @@ SYNOPSIS | --remove-custom-metadata=[METADATA_KEYS,...] --update-custom-metadata=[CUSTOM_METADATA_KEYS_AND_VALUES,...]] [--if-generation-match=GENERATION - --if-metageneration-match=METAGENERATION] [GCLOUD_WIDE_FLAG ...] + --if-metageneration-match=METAGENERATION] + [--retain-until=DATETIME --retention-mode=RETENTION_MODE] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) The mv command allows you to move data between your local file @@ -352,6 +354,16 @@ PRECONDITION FLAGS Execute only if the metageneration matches the metageneration of the requested object. +RETENTION FLAGS + --retain-until=DATETIME + Ensures the destination object is retained until the specified time in + RFC 3339 format. + + --retention-mode=RETENTION_MODE + Sets the destination object retention mode to either "Locked" or + "Unlocked". When retention mode is "Locked", the retain until time can + only be increased. RETENTION_MODE must be one of: Locked, Unlocked. + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/alpha/storage/objects/compose b/gcloud/alpha/storage/objects/compose index a0a8d3950..70df7a85d 100644 --- a/gcloud/alpha/storage/objects/compose +++ b/gcloud/alpha/storage/objects/compose @@ -6,7 +6,9 @@ SYNOPSIS gcloud alpha storage objects compose SOURCE [SOURCE ...] DESTINATION [--additional-headers=HEADER=VALUE] [--if-generation-match=GENERATION - --if-metageneration-match=METAGENERATION] [GCLOUD_WIDE_FLAG ...] + --if-metageneration-match=METAGENERATION] + [--retain-until=DATETIME --retention-mode=RETENTION_MODE] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) gcloud alpha storage objects compose creates a new object whose @@ -48,6 +50,16 @@ PRECONDITION FLAGS Execute only if the metageneration matches the metageneration of the requested object. +RETENTION FLAGS + --retain-until=DATETIME + Ensures the destination object is retained until the specified time in + RFC 3339 format. + + --retention-mode=RETENTION_MODE + Sets the destination object retention mode to either "Locked" or + "Unlocked". When retention mode is "Locked", the retain until time can + only be increased. RETENTION_MODE must be one of: Locked, Unlocked. + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/alpha/storage/objects/update b/gcloud/alpha/storage/objects/update index c69c45037..4f8a53ca8 100644 --- a/gcloud/alpha/storage/objects/update +++ b/gcloud/alpha/storage/objects/update @@ -25,7 +25,10 @@ SYNOPSIS | --remove-custom-metadata=[METADATA_KEYS,...] --update-custom-metadata=[CUSTOM_METADATA_KEYS_AND_VALUES,...]] [--if-generation-match=GENERATION - --if-metageneration-match=METAGENERATION] [GCLOUD_WIDE_FLAG ...] + --if-metageneration-match=METAGENERATION] + [--clear-retention --override-unlocked-retention + --retain-until=DATETIME --retention-mode=RETENTION_MODE] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Update Cloud Storage objects. @@ -218,6 +221,26 @@ PRECONDITION FLAGS Execute only if the metageneration matches the metageneration of the requested object. +RETENTION FLAGS + --clear-retention + Clears object retention settings and unlocks the configuration. + Requires --override-unlocked-retention flag as confirmation. + + --override-unlocked-retention + Needed for certain retention configuration modifications, such as + clearing retention settings and reducing retention time. Note that + locked configurations cannot be edited even with this flag. + + --retain-until=DATETIME + Ensures the object is retained until the specified time in RFC 3339 + format. Requires --override-unlocked-retention flag to shorten the + retain-until time in unlocked configurations. + + --retention-mode=RETENTION_MODE + Sets the object retention mode to either "Locked" or "Unlocked". When + retention mode is "Locked", the retain until time can only be + increased. RETENTION_MODE must be one of: Locked, Unlocked. + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/alpha/transfer/jobs/create b/gcloud/alpha/transfer/jobs/create index 33a65d8df..cbe2dec91 100644 --- a/gcloud/alpha/transfer/jobs/create +++ b/gcloud/alpha/transfer/jobs/create @@ -134,7 +134,7 @@ FLAGS Note: Be sure to put quotations around the JSON value strings. Azure: - http://cloud/storage-transfer/docs/reference/rest/v1/TransferSpec#AzureCredentials + https://cloud.google.com/storage-transfer/docs/reference/rest/v1/TransferSpec#AzureCredentials --source-agent-pool=SOURCE_AGENT_POOL If using a POSIX filesystem source, specify the ID of the agent pool diff --git a/gcloud/alpha/transfer/jobs/update b/gcloud/alpha/transfer/jobs/update index a0d176574..a9bea3ad1 100644 --- a/gcloud/alpha/transfer/jobs/update +++ b/gcloud/alpha/transfer/jobs/update @@ -157,7 +157,7 @@ FLAGS Note: Be sure to put quotations around the JSON value strings. Azure: - http://cloud/storage-transfer/docs/reference/rest/v1/TransferSpec#AzureCredentials + https://cloud.google.com/storage-transfer/docs/reference/rest/v1/TransferSpec#AzureCredentials --source-agent-pool=SOURCE_AGENT_POOL If using a POSIX filesystem source, specify the ID of the agent pool diff --git a/gcloud/asset/get-effective-iam-policy b/gcloud/asset/get-effective-iam-policy index e7b0f4220..d5e485ab5 100644 --- a/gcloud/asset/get-effective-iam-policy +++ b/gcloud/asset/get-effective-iam-policy @@ -41,7 +41,7 @@ REQUIRED FLAGS Names refer to a list of full resource names (https://cloud.google.com/asset-inventory/docs/resource-name-format) of searchable asset types - (https://cloud.google.com/asset-inventory/docs/supported-asset-types#searchable_asset_types). + (https://cloud.google.com/asset-inventory/docs/supported-asset-types). For each batch call, total number of names provided is between 1 and 20. diff --git a/gcloud/asset/search-all-iam-policies b/gcloud/asset/search-all-iam-policies index 9f8b89b25..7d8c13516 100644 --- a/gcloud/asset/search-all-iam-policies +++ b/gcloud/asset/search-all-iam-policies @@ -34,7 +34,7 @@ FLAGS List of asset types that the IAM policies are attached to. If empty, it will search the IAM policies that are attached to all the searchable asset types - (https://cloud.google.com/asset-inventory/docs/supported-asset-types#searchable_asset_types). + (https://cloud.google.com/asset-inventory/docs/supported-asset-types). Regular expressions are also supported. For example: diff --git a/gcloud/asset/search-all-resources b/gcloud/asset/search-all-resources index ad96f15fd..1dc116a68 100644 --- a/gcloud/asset/search-all-resources +++ b/gcloud/asset/search-all-resources @@ -26,7 +26,7 @@ FLAGS --asset-types=[ASSET_TYPES,...] A list of asset types that this request searches for. If empty, it will search all the searchable asset types - (https://cloud.google.com/asset-inventory/docs/supported-asset-types#searchable_asset_types). + (https://cloud.google.com/asset-inventory/docs/supported-asset-types). Regular expressions are also supported. For example: diff --git a/gcloud/assured/operations/list b/gcloud/assured/operations/list index 56366ed81..c5843ad03 100644 --- a/gcloud/assured/operations/list +++ b/gcloud/assured/operations/list @@ -29,7 +29,7 @@ REQUIRED FLAGS --location=LOCATION The location of the Assured Workloads operations. For a current list of supported LOCATION values, see Assured Workloads locations - (http://cloud/assured-workloads/docs/locations). + (https://cloud.google.com/assured-workloads/docs/locations). --organization=ORGANIZATION The parent organization of the Assured Workloads operations, provided diff --git a/gcloud/assured/workloads/create b/gcloud/assured/workloads/create index 784d4323b..377e0f39c 100644 --- a/gcloud/assured/workloads/create +++ b/gcloud/assured/workloads/create @@ -60,7 +60,7 @@ REQUIRED FLAGS --location=LOCATION The location of the new Assured Workloads environment. For a current list of supported LOCATION values, see Assured Workloads locations - (http://cloud/assured-workloads/docs/locations). + (https://cloud.google.com/assured-workloads/docs/locations). --organization=ORGANIZATION The parent organization of the new Assured Workloads environment, diff --git a/gcloud/assured/workloads/list b/gcloud/assured/workloads/list index eb3fab830..5e41520cb 100644 --- a/gcloud/assured/workloads/list +++ b/gcloud/assured/workloads/list @@ -29,7 +29,7 @@ REQUIRED FLAGS --location=LOCATION The location of the Assured Workloads environments. For a current list of supported LOCATION values, see Assured Workloads locations - (http://cloud/assured-workloads/docs/locations). + (https://cloud.google.com/assured-workloads/docs/locations). --organization=ORGANIZATION The parent organization of the Assured Workloads environments, provided diff --git a/gcloud/assured/workloads/violations/list b/gcloud/assured/workloads/violations/list index 75228cdb3..455295fec 100644 --- a/gcloud/assured/workloads/violations/list +++ b/gcloud/assured/workloads/violations/list @@ -27,7 +27,7 @@ REQUIRED FLAGS --location=LOCATION The location of the Assured Workloads environments. For a current list of supported LOCATION values, see Assured Workloads locations - (http://cloud/assured-workloads/docs/locations). + (https://cloud.google.com/assured-workloads/docs/locations). --organization=ORGANIZATION The parent organization of the Assured Workloads environments, provided diff --git a/gcloud/beta/asset/search-all-resources b/gcloud/beta/asset/search-all-resources index 84ad8612d..b90a763b4 100644 --- a/gcloud/beta/asset/search-all-resources +++ b/gcloud/beta/asset/search-all-resources @@ -27,7 +27,7 @@ FLAGS --asset-types=[ASSET_TYPES,...] A list of asset types that this request searches for. If empty, it will search all the searchable asset types - (https://cloud.google.com/asset-inventory/docs/supported-asset-types#searchable_asset_types). + (https://cloud.google.com/asset-inventory/docs/supported-asset-types). Regular expressions are also supported. For example: diff --git a/gcloud/beta/assured/operations/list b/gcloud/beta/assured/operations/list index 1f3354d57..a86ae1d90 100644 --- a/gcloud/beta/assured/operations/list +++ b/gcloud/beta/assured/operations/list @@ -29,7 +29,7 @@ REQUIRED FLAGS --location=LOCATION The location of the Assured Workloads operations. For a current list of supported LOCATION values, see Assured Workloads locations - (http://cloud/assured-workloads/docs/locations). + (https://cloud.google.com/assured-workloads/docs/locations). --organization=ORGANIZATION The parent organization of the Assured Workloads operations, provided diff --git a/gcloud/beta/assured/workloads/create b/gcloud/beta/assured/workloads/create index c482f362e..078f20f37 100644 --- a/gcloud/beta/assured/workloads/create +++ b/gcloud/beta/assured/workloads/create @@ -60,7 +60,7 @@ REQUIRED FLAGS --location=LOCATION The location of the new Assured Workloads environment. For a current list of supported LOCATION values, see Assured Workloads locations - (http://cloud/assured-workloads/docs/locations). + (https://cloud.google.com/assured-workloads/docs/locations). --organization=ORGANIZATION The parent organization of the new Assured Workloads environment, diff --git a/gcloud/beta/assured/workloads/list b/gcloud/beta/assured/workloads/list index b76988bd1..34f37cfaa 100644 --- a/gcloud/beta/assured/workloads/list +++ b/gcloud/beta/assured/workloads/list @@ -29,7 +29,7 @@ REQUIRED FLAGS --location=LOCATION The location of the Assured Workloads environments. For a current list of supported LOCATION values, see Assured Workloads locations - (http://cloud/assured-workloads/docs/locations). + (https://cloud.google.com/assured-workloads/docs/locations). --organization=ORGANIZATION The parent organization of the Assured Workloads environments, provided diff --git a/gcloud/beta/assured/workloads/violations/list b/gcloud/beta/assured/workloads/violations/list index 8184533cf..7231da575 100644 --- a/gcloud/beta/assured/workloads/violations/list +++ b/gcloud/beta/assured/workloads/violations/list @@ -28,7 +28,7 @@ REQUIRED FLAGS --location=LOCATION The location of the Assured Workloads environments. For a current list of supported LOCATION values, see Assured Workloads locations - (http://cloud/assured-workloads/docs/locations). + (https://cloud.google.com/assured-workloads/docs/locations). --organization=ORGANIZATION The parent organization of the Assured Workloads environments, provided diff --git a/gcloud/beta/config/get b/gcloud/beta/config/get index fb790062b..4b95de593 100644 --- a/gcloud/beta/config/get +++ b/gcloud/beta/config/get @@ -1235,6 +1235,20 @@ AVAILABLE PROPERTIES max_retry_delay Max second delay between retriable operations. + multipart_chunksize + Specifies partition size in bytes of each part of a multipart + upload made by the Boto3 client. To calculate the maximum size of a + Boto3 client multipart upload, multiply the multipart_chunk value + by the maximum number of parts the API allows. For AWS S3 this + limit is 10000. Values can be provided either in bytes or as + human-readable values (e.g., "150M" to represent 150 mebibytes). + + multipart_threshold + Files larger than this threshold will be partitioned into parts, + uploaded separately by the Boto3 client, and then combined into a + single object. Otherwise, files smaller than this threshold will be + uploaded by the Boto3 client in a single stream. + parallel_composite_upload_compatibility_check Determines if the GET bucket call should be performed to check if the default storage class and retention period for the destination diff --git a/gcloud/beta/config/help b/gcloud/beta/config/help index 8863decea..927b5fa44 100644 --- a/gcloud/beta/config/help +++ b/gcloud/beta/config/help @@ -1267,6 +1267,20 @@ AVAILABLE PROPERTIES max_retry_delay Max second delay between retriable operations. + multipart_chunksize + Specifies partition size in bytes of each part of a multipart + upload made by the Boto3 client. To calculate the maximum size of a + Boto3 client multipart upload, multiply the multipart_chunk value + by the maximum number of parts the API allows. For AWS S3 this + limit is 10000. Values can be provided either in bytes or as + human-readable values (e.g., "150M" to represent 150 mebibytes). + + multipart_threshold + Files larger than this threshold will be partitioned into parts, + uploaded separately by the Boto3 client, and then combined into a + single object. Otherwise, files smaller than this threshold will be + uploaded by the Boto3 client in a single stream. + parallel_composite_upload_compatibility_check Determines if the GET bucket call should be performed to check if the default storage class and retention period for the destination diff --git a/gcloud/beta/config/list b/gcloud/beta/config/list index f01d69688..b5d79f94d 100644 --- a/gcloud/beta/config/list +++ b/gcloud/beta/config/list @@ -1279,6 +1279,20 @@ AVAILABLE PROPERTIES max_retry_delay Max second delay between retriable operations. + multipart_chunksize + Specifies partition size in bytes of each part of a multipart + upload made by the Boto3 client. To calculate the maximum size of a + Boto3 client multipart upload, multiply the multipart_chunk value + by the maximum number of parts the API allows. For AWS S3 this + limit is 10000. Values can be provided either in bytes or as + human-readable values (e.g., "150M" to represent 150 mebibytes). + + multipart_threshold + Files larger than this threshold will be partitioned into parts, + uploaded separately by the Boto3 client, and then combined into a + single object. Otherwise, files smaller than this threshold will be + uploaded by the Boto3 client in a single stream. + parallel_composite_upload_compatibility_check Determines if the GET bucket call should be performed to check if the default storage class and retention period for the destination diff --git a/gcloud/beta/config/set b/gcloud/beta/config/set index 28ed02620..5bcab3658 100644 --- a/gcloud/beta/config/set +++ b/gcloud/beta/config/set @@ -1282,6 +1282,20 @@ AVAILABLE PROPERTIES max_retry_delay Max second delay between retriable operations. + multipart_chunksize + Specifies partition size in bytes of each part of a multipart + upload made by the Boto3 client. To calculate the maximum size of a + Boto3 client multipart upload, multiply the multipart_chunk value + by the maximum number of parts the API allows. For AWS S3 this + limit is 10000. Values can be provided either in bytes or as + human-readable values (e.g., "150M" to represent 150 mebibytes). + + multipart_threshold + Files larger than this threshold will be partitioned into parts, + uploaded separately by the Boto3 client, and then combined into a + single object. Otherwise, files smaller than this threshold will be + uploaded by the Boto3 client in a single stream. + parallel_composite_upload_compatibility_check Determines if the GET bucket call should be performed to check if the default storage class and retention period for the destination diff --git a/gcloud/beta/config/unset b/gcloud/beta/config/unset index fe5366109..3a4e220a8 100644 --- a/gcloud/beta/config/unset +++ b/gcloud/beta/config/unset @@ -1243,6 +1243,20 @@ AVAILABLE PROPERTIES max_retry_delay Max second delay between retriable operations. + multipart_chunksize + Specifies partition size in bytes of each part of a multipart + upload made by the Boto3 client. To calculate the maximum size of a + Boto3 client multipart upload, multiply the multipart_chunk value + by the maximum number of parts the API allows. For AWS S3 this + limit is 10000. Values can be provided either in bytes or as + human-readable values (e.g., "150M" to represent 150 mebibytes). + + multipart_threshold + Files larger than this threshold will be partitioned into parts, + uploaded separately by the Boto3 client, and then combined into a + single object. Otherwise, files smaller than this threshold will be + uploaded by the Boto3 client in a single stream. + parallel_composite_upload_compatibility_check Determines if the GET bucket call should be performed to check if the default storage class and retention period for the destination diff --git a/gcloud/beta/container/binauthz/attestations/list b/gcloud/beta/container/binauthz/attestations/list index 73bffdd08..d9482b255 100644 --- a/gcloud/beta/container/binauthz/attestations/list +++ b/gcloud/beta/container/binauthz/attestations/list @@ -4,16 +4,18 @@ NAME SYNOPSIS gcloud beta container binauthz attestations list - (--attestor=ATTESTOR : --attestor-project=ATTESTOR_PROJECT) - [--artifact-url=ARTIFACT_URL] [--filter=EXPRESSION] [--limit=LIMIT] - [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] - [GCLOUD_WIDE_FLAG ...] + [--artifact-url=ARTIFACT_URL] + [--attestor=ATTESTOR : --attestor-project=ATTESTOR_PROJECT] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) This command lists Binary Authorization attestations for your - project. Command line flags specify which artifact to list the attestations - for. If no artifact is specified, then this lists all URLs with associated - occurrences. + project. Command line flags specify which attestor and artifact to list the + attestations for. If no attestor is specified, this lists all attestations + in the project, which requires the containeranalysis.occurrences.get + permission. If no artifact is specified, then this lists all URLs with + associated occurrences. EXAMPLES List the Occurrence messages for all attestations bound to the passed @@ -29,15 +31,17 @@ EXAMPLES --attestor=projects/foo/attestors/bar \ --artifact-url='gcr.io/foo/example-image@sha256:abcd' -REQUIRED FLAGS +FLAGS + --artifact-url=ARTIFACT_URL + Container URL. May be in the gcr.io/repository/image format, or may + optionally contain the http or https scheme + Attestor resource - The Attestor whose Container Analysis Note will be queried for attestations. Note that the caller must have the containeranalysis.notes.listOccurrences permission on the note being queried. 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. @@ -57,11 +61,6 @@ REQUIRED FLAGS ▸ provide the argument --project on the command line; ▸ set the property core/project. -FLAGS - --artifact-url=ARTIFACT_URL - Container URL. May be in the gcr.io/repository/image format, or may - optionally contain the http or https scheme - LIST COMMAND FLAGS --filter=EXPRESSION Apply a Boolean filter EXPRESSION to each resource item to be listed. diff --git a/gcloud/beta/container/binauthz/attestations/sign-and-create b/gcloud/beta/container/binauthz/attestations/sign-and-create index 4a92f865b..d71afa708 100644 --- a/gcloud/beta/container/binauthz/attestations/sign-and-create +++ b/gcloud/beta/container/binauthz/attestations/sign-and-create @@ -12,8 +12,9 @@ SYNOPSIS --keyversion-project=KEYVERSION_PROJECT) [--dsse-type=DSSE_TYPE; default="application/vnd.dev.cosign.simplesigning.v1+json"] - [--public-key-id-override=PUBLIC_KEY_ID_OVERRIDE] - [--pae-encode-payload | --validate] [GCLOUD_WIDE_FLAG ...] + [--pae-encode-payload] + [--public-key-id-override=PUBLIC_KEY_ID_OVERRIDE] [--validate] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) This command signs and creates a Binary Authorization attestation @@ -122,6 +123,9 @@ OPTIONAL FLAGS --dsse-type=DSSE_TYPE; default="application/vnd.dev.cosign.simplesigning.v1+json" DSSE type used for pae encoding. + --pae-encode-payload + Whether to pae-encode the payload before signing. + --public-key-id-override=PUBLIC_KEY_ID_OVERRIDE If provided, the ID of the public key that will be used to verify the Attestation instead of the default generated one. This ID should match @@ -131,18 +135,9 @@ OPTIONAL FLAGS This parameter is only necessary if the --public-key-id-override flag was provided when this KMS key was added to the Attestor. - exclusive flags - - At most one of these can be specified: - - --pae-encode-payload - Whether to pae-encode the payload before signing. Note: currently - validation is not supported for attestations with pae-encoded - payload. - - --validate - Whether to validate that the Attestation can be verified by the - provided Attestor. + --validate + Whether to validate that the Attestation can be verified by the + provided Attestor. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/beta/container/fleet/create b/gcloud/beta/container/fleet/create index 2aaed7b0b..397036776 100644 --- a/gcloud/beta/container/fleet/create +++ b/gcloud/beta/container/fleet/create @@ -3,7 +3,10 @@ NAME SYNOPSIS gcloud beta container fleet create [--async] [--display-name=DISPLAY_NAME] - [--labels=[KEY=VALUE,...]] [GCLOUD_WIDE_FLAG ...] + [--labels=[KEY=VALUE,...]] + [--security-posture=SECURITY_POSTURE + --workload-vulnerability-scanning=WORKLOAD_VULNERABILITY_SCANNING] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) This command can fail for the following reasons: @@ -36,6 +39,26 @@ FLAGS contain only hyphens (-), underscores (_), lowercase characters, and numbers. + Default cluster configurations to apply across the fleet. + + Security posture config. + + --security-posture=SECURITY_POSTURE + To apply standard security posture to clusters in the fleet, + + $ gcloud beta container fleet create --security-posture=standard + + SECURITY_POSTURE must be one of: disabled, standard. + + --workload-vulnerability-scanning=WORKLOAD_VULNERABILITY_SCANNING + To apply standard vulnerability scanning to clusters in the fleet, + + $ gcloud beta container fleet create \ + --workload-vulnerability-scanning=standard + + WORKLOAD_VULNERABILITY_SCANNING must be one of: disabled, standard, + enterprise. + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/beta/container/fleet/identity-service/apply b/gcloud/beta/container/fleet/identity-service/apply index 79640376b..a1b7e348e 100644 --- a/gcloud/beta/container/fleet/identity-service/apply +++ b/gcloud/beta/container/fleet/identity-service/apply @@ -1,19 +1,16 @@ NAME - gcloud beta container fleet identity-service apply - update an Identity - Service Feature Spec + gcloud beta container fleet identity-service apply - update the Identity + Service Feature SYNOPSIS gcloud beta container fleet identity-service apply - ([--config=CONFIG : [--membership=MEMBERSHIP : --location=LOCATION]]) + (--fleet-default-member-config=FLEET_DEFAULT_MEMBER_CONFIG + [(--config=CONFIG | --origin=ORIGIN) + : [--membership=MEMBERSHIP : --location=LOCATION]]) [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Applies the authentication configuration to the Identity Service - feature spec for this membership. This configuration is now the "source of - truth" for the cluster and can only be updated by using this command or the - Cloud Console. Any local authentication configuration on the cluster is - overwritten by this configuration, including any local updates made after - you run this command. + (BETA) This command updates the Identity Service Feature in a fleet. EXAMPLES To apply an Identity Service configuration to a membership, run: @@ -22,14 +19,31 @@ EXAMPLES --membership=MEMBERSHIP_NAME \ --config=/path/to/identity-service.yaml + To create or modify a fleet-level default membership configuration, run: + + $ gcloud beta container fleet identity-service apply \ + --fleet-default-member-config=/path/to/identity-service.yaml + + To apply an existing fleet-level default membership configuration to a + membership, run: + + $ gcloud beta container fleet identity-service apply \ + --origin=fleet --membership=MEMBERSHIP_NAME + REQUIRED FLAGS At least one of these must be specified: - --config=CONFIG - The path to an identity-service.yaml config file. + --fleet-default-member-config=FLEET_DEFAULT_MEMBER_CONFIG + The path to an identity-service.yaml configuration file. - This flag argument must be specified if any of the other arguments in - this group are specified. + Exactly one of these must be specified: + + --config=CONFIG + The path to an identity-service.yaml configuration file. + + --origin=ORIGIN + Applies the fleet-level default membership configuration to a + membership. ORIGIN must be (only one value is supported): fleet. Membership resource - The group of arguments defining a membership. The arguments in this group can be used to specify the attributes of this diff --git a/gcloud/beta/container/fleet/identity-service/delete b/gcloud/beta/container/fleet/identity-service/delete index 7e48035f5..c86c51adf 100644 --- a/gcloud/beta/container/fleet/identity-service/delete +++ b/gcloud/beta/container/fleet/identity-service/delete @@ -1,6 +1,6 @@ NAME - gcloud beta container fleet identity-service delete - remove the Identity - Service Feature Spec for the given membership + gcloud beta container fleet identity-service delete - delete a resource + from the Identity Service Feature SYNOPSIS gcloud beta container fleet identity-service delete @@ -8,14 +8,19 @@ SYNOPSIS [--membership=MEMBERSHIP : --location=LOCATION] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Removes the Identity Service Feature Spec for the given membership. + (BETA) Deletes a resource from the Identity Service Feature. EXAMPLES - To delete an Identity Service configuration for a membership, run: + To delete the Identity Service configuration from a membership, run: $ gcloud beta container fleet identity-service delete \ --membership=MEMBERSHIP_NAME + To delete the fleet-level default membership configuration, run: + + $ gcloud beta container fleet identity-service delete \ + --fleet-default-member-config + FLAGS --fleet-default-member-config If specified, deletes the default membership configuration present in diff --git a/gcloud/beta/container/fleet/identity-service/enable b/gcloud/beta/container/fleet/identity-service/enable index fe49a417d..a05121e87 100644 --- a/gcloud/beta/container/fleet/identity-service/enable +++ b/gcloud/beta/container/fleet/identity-service/enable @@ -1,5 +1,5 @@ NAME - gcloud beta container fleet identity-service enable - enable Identity + gcloud beta container fleet identity-service enable - enable the Identity Service Feature SYNOPSIS @@ -15,6 +15,12 @@ EXAMPLES $ gcloud beta container fleet identity-service enable + To enable the Identity Service Feature with a fleet-level default + membership configuration, run: + + $ gcloud beta container fleet identity-service enable \ + --fleet-default-member-config=/path/to/identity-service.yaml + FLAGS --fleet-default-member-config=FLEET_DEFAULT_MEMBER_CONFIG The path to an identity-service.yaml identity configuration file. If diff --git a/gcloud/beta/container/fleet/identity-service/help b/gcloud/beta/container/fleet/identity-service/help index d2f08bcc2..4b11ba7ac 100644 --- a/gcloud/beta/container/fleet/identity-service/help +++ b/gcloud/beta/container/fleet/identity-service/help @@ -17,11 +17,10 @@ COMMANDS COMMAND is one of the following: apply - (BETA) Update an Identity Service Feature Spec. + (BETA) Update the Identity Service Feature. delete - (BETA) Remove the Identity Service Feature Spec for the given - membership. + (BETA) Delete a resource from the Identity Service Feature. describe (BETA) Prints the status of all clusters with Identity Service @@ -31,7 +30,7 @@ COMMANDS (BETA) Disable Identity Service Feature. enable - (BETA) Enable Identity Service Feature. + (BETA) Enable the Identity Service Feature. NOTES This command is currently in beta and might change without notice. These diff --git a/gcloud/beta/container/fleet/mesh/disable b/gcloud/beta/container/fleet/mesh/disable index 5b5d8c9dd..b8673b503 100644 --- a/gcloud/beta/container/fleet/mesh/disable +++ b/gcloud/beta/container/fleet/mesh/disable @@ -2,7 +2,8 @@ NAME gcloud beta container fleet mesh disable - disable Service Mesh Feature SYNOPSIS - gcloud beta container fleet mesh disable [--force] [GCLOUD_WIDE_FLAG ...] + gcloud beta container fleet mesh disable [--fleet-default-member-config] + [--force] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Disable the Service Mesh Feature in a fleet. @@ -18,6 +19,16 @@ EXAMPLES --fleet-default-member-config FLAGS + --fleet-default-member-config + If specified, deletes the default membership configuration present in + your fleet. + + To delete the fleet-level default Membership configuration present in + your fleet, run: + + $ gcloud beta container fleet mesh disable \ + --fleet-default-member-config + --force Disable this feature, even if it is currently in use. Force disablement may result in unexpected behavior. diff --git a/gcloud/beta/container/fleet/mesh/enable b/gcloud/beta/container/fleet/mesh/enable index c300053a6..0fbb7ecb8 100644 --- a/gcloud/beta/container/fleet/mesh/enable +++ b/gcloud/beta/container/fleet/mesh/enable @@ -2,7 +2,9 @@ NAME gcloud beta container fleet mesh enable - enable Service Mesh Feature SYNOPSIS - gcloud beta container fleet mesh enable [GCLOUD_WIDE_FLAG ...] + gcloud beta container fleet mesh enable + [--fleet-default-member-config=FLEET_DEFAULT_MEMBER_CONFIG] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Enable the Service Mesh Feature in a fleet. @@ -18,6 +20,16 @@ EXAMPLES $ gcloud beta container fleet mesh enable \ --fleet-default-member-config=/path/to/service-mesh.yaml +FLAGS + --fleet-default-member-config=FLEET_DEFAULT_MEMBER_CONFIG + The path to a service-mesh.yaml configuration file. + + To enable the Service Mesh Feature with a fleet-level default + membership configuration, run: + + $ gcloud beta container fleet mesh enable \ + --fleet-default-member-config=/path/to/service-mesh.yaml + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/beta/container/fleet/update b/gcloud/beta/container/fleet/update index 2846cbf5a..1104307da 100644 --- a/gcloud/beta/container/fleet/update +++ b/gcloud/beta/container/fleet/update @@ -4,6 +4,8 @@ NAME SYNOPSIS gcloud beta container fleet update [--async] [--display-name=DISPLAY_NAME] [--update-labels=[KEY=VALUE,...]] + [--security-posture=SECURITY_POSTURE + --workload-vulnerability-scanning=WORKLOAD_VULNERABILITY_SCANNING] [--clear-labels | --remove-labels=[KEY,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -38,6 +40,26 @@ FLAGS contain only hyphens (-), underscores (_), lowercase characters, and numbers. + Default cluster configurations to apply across the fleet. + + Security posture config. + + --security-posture=SECURITY_POSTURE + To apply standard security posture to clusters in the fleet, + + $ gcloud beta container fleet update --security-posture=standard + + SECURITY_POSTURE must be one of: disabled, standard. + + --workload-vulnerability-scanning=WORKLOAD_VULNERABILITY_SCANNING + To apply standard vulnerability scanning to clusters in the fleet, + + $ gcloud beta container fleet update \ + --workload-vulnerability-scanning=standard + + WORKLOAD_VULNERABILITY_SCANNING must be one of: disabled, standard, + enterprise. + At most one of these can be specified: --clear-labels diff --git a/gcloud/beta/container/hub/create b/gcloud/beta/container/hub/create index 9a8f5a701..9fb79c3c0 100644 --- a/gcloud/beta/container/hub/create +++ b/gcloud/beta/container/hub/create @@ -3,7 +3,10 @@ NAME SYNOPSIS gcloud beta container hub create [--async] [--display-name=DISPLAY_NAME] - [--labels=[KEY=VALUE,...]] [GCLOUD_WIDE_FLAG ...] + [--labels=[KEY=VALUE,...]] + [--security-posture=SECURITY_POSTURE + --workload-vulnerability-scanning=WORKLOAD_VULNERABILITY_SCANNING] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) This command can fail for the following reasons: @@ -36,6 +39,26 @@ FLAGS contain only hyphens (-), underscores (_), lowercase characters, and numbers. + Default cluster configurations to apply across the fleet. + + Security posture config. + + --security-posture=SECURITY_POSTURE + To apply standard security posture to clusters in the fleet, + + $ gcloud beta container hub create --security-posture=standard + + SECURITY_POSTURE must be one of: disabled, standard. + + --workload-vulnerability-scanning=WORKLOAD_VULNERABILITY_SCANNING + To apply standard vulnerability scanning to clusters in the fleet, + + $ gcloud beta container hub create \ + --workload-vulnerability-scanning=standard + + WORKLOAD_VULNERABILITY_SCANNING must be one of: disabled, standard, + enterprise. + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/beta/container/hub/identity-service/apply b/gcloud/beta/container/hub/identity-service/apply index c0ebf4f47..2fd011d7c 100644 --- a/gcloud/beta/container/hub/identity-service/apply +++ b/gcloud/beta/container/hub/identity-service/apply @@ -1,19 +1,16 @@ NAME - gcloud beta container hub identity-service apply - update an Identity - Service Feature Spec + gcloud beta container hub identity-service apply - update the Identity + Service Feature SYNOPSIS gcloud beta container hub identity-service apply - ([--config=CONFIG : [--membership=MEMBERSHIP : --location=LOCATION]]) + (--fleet-default-member-config=FLEET_DEFAULT_MEMBER_CONFIG + [(--config=CONFIG | --origin=ORIGIN) + : [--membership=MEMBERSHIP : --location=LOCATION]]) [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Applies the authentication configuration to the Identity Service - feature spec for this membership. This configuration is now the "source of - truth" for the cluster and can only be updated by using this command or the - Cloud Console. Any local authentication configuration on the cluster is - overwritten by this configuration, including any local updates made after - you run this command. + (BETA) This command updates the Identity Service Feature in a fleet. EXAMPLES To apply an Identity Service configuration to a membership, run: @@ -22,14 +19,31 @@ EXAMPLES --membership=MEMBERSHIP_NAME \ --config=/path/to/identity-service.yaml + To create or modify a fleet-level default membership configuration, run: + + $ gcloud beta container hub identity-service apply \ + --fleet-default-member-config=/path/to/identity-service.yaml + + To apply an existing fleet-level default membership configuration to a + membership, run: + + $ gcloud beta container hub identity-service apply --origin=fleet \ + --membership=MEMBERSHIP_NAME + REQUIRED FLAGS At least one of these must be specified: - --config=CONFIG - The path to an identity-service.yaml config file. + --fleet-default-member-config=FLEET_DEFAULT_MEMBER_CONFIG + The path to an identity-service.yaml configuration file. - This flag argument must be specified if any of the other arguments in - this group are specified. + Exactly one of these must be specified: + + --config=CONFIG + The path to an identity-service.yaml configuration file. + + --origin=ORIGIN + Applies the fleet-level default membership configuration to a + membership. ORIGIN must be (only one value is supported): fleet. Membership resource - The group of arguments defining a membership. The arguments in this group can be used to specify the attributes of this diff --git a/gcloud/beta/container/hub/identity-service/delete b/gcloud/beta/container/hub/identity-service/delete index f4ae7b979..635b3ddb7 100644 --- a/gcloud/beta/container/hub/identity-service/delete +++ b/gcloud/beta/container/hub/identity-service/delete @@ -1,6 +1,6 @@ NAME - gcloud beta container hub identity-service delete - remove the Identity - Service Feature Spec for the given membership + gcloud beta container hub identity-service delete - delete a resource from + the Identity Service Feature SYNOPSIS gcloud beta container hub identity-service delete @@ -8,14 +8,19 @@ SYNOPSIS [--membership=MEMBERSHIP : --location=LOCATION] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Removes the Identity Service Feature Spec for the given membership. + (BETA) Deletes a resource from the Identity Service Feature. EXAMPLES - To delete an Identity Service configuration for a membership, run: + To delete the Identity Service configuration from a membership, run: $ gcloud beta container hub identity-service delete \ --membership=MEMBERSHIP_NAME + To delete the fleet-level default membership configuration, run: + + $ gcloud beta container hub identity-service delete \ + --fleet-default-member-config + FLAGS --fleet-default-member-config If specified, deletes the default membership configuration present in diff --git a/gcloud/beta/container/hub/identity-service/enable b/gcloud/beta/container/hub/identity-service/enable index e8001e8f9..cf3f2ce85 100644 --- a/gcloud/beta/container/hub/identity-service/enable +++ b/gcloud/beta/container/hub/identity-service/enable @@ -1,6 +1,6 @@ NAME - gcloud beta container hub identity-service enable - enable Identity Service - Feature + gcloud beta container hub identity-service enable - enable the Identity + Service Feature SYNOPSIS gcloud beta container hub identity-service enable @@ -15,6 +15,12 @@ EXAMPLES $ gcloud beta container hub identity-service enable + To enable the Identity Service Feature with a fleet-level default + membership configuration, run: + + $ gcloud beta container hub identity-service enable \ + --fleet-default-member-config=/path/to/identity-service.yaml + FLAGS --fleet-default-member-config=FLEET_DEFAULT_MEMBER_CONFIG The path to an identity-service.yaml identity configuration file. If diff --git a/gcloud/beta/container/hub/identity-service/help b/gcloud/beta/container/hub/identity-service/help index f70c5f520..dfff369b8 100644 --- a/gcloud/beta/container/hub/identity-service/help +++ b/gcloud/beta/container/hub/identity-service/help @@ -17,11 +17,10 @@ COMMANDS COMMAND is one of the following: apply - (BETA) Update an Identity Service Feature Spec. + (BETA) Update the Identity Service Feature. delete - (BETA) Remove the Identity Service Feature Spec for the given - membership. + (BETA) Delete a resource from the Identity Service Feature. describe (BETA) Prints the status of all clusters with Identity Service @@ -31,7 +30,7 @@ COMMANDS (BETA) Disable Identity Service Feature. enable - (BETA) Enable Identity Service Feature. + (BETA) Enable the Identity Service Feature. NOTES This command is currently in beta and might change without notice. These diff --git a/gcloud/beta/container/hub/mesh/disable b/gcloud/beta/container/hub/mesh/disable index bb2fdc4e6..c8cbde7d2 100644 --- a/gcloud/beta/container/hub/mesh/disable +++ b/gcloud/beta/container/hub/mesh/disable @@ -2,7 +2,8 @@ NAME gcloud beta container hub mesh disable - disable Service Mesh Feature SYNOPSIS - gcloud beta container hub mesh disable [--force] [GCLOUD_WIDE_FLAG ...] + gcloud beta container hub mesh disable [--fleet-default-member-config] + [--force] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Disable the Service Mesh Feature in a fleet. @@ -18,6 +19,16 @@ EXAMPLES --fleet-default-member-config FLAGS + --fleet-default-member-config + If specified, deletes the default membership configuration present in + your fleet. + + To delete the fleet-level default Membership configuration present in + your fleet, run: + + $ gcloud beta container hub mesh disable \ + --fleet-default-member-config + --force Disable this feature, even if it is currently in use. Force disablement may result in unexpected behavior. diff --git a/gcloud/beta/container/hub/mesh/enable b/gcloud/beta/container/hub/mesh/enable index 89286ce6b..e0d242347 100644 --- a/gcloud/beta/container/hub/mesh/enable +++ b/gcloud/beta/container/hub/mesh/enable @@ -2,7 +2,9 @@ NAME gcloud beta container hub mesh enable - enable Service Mesh Feature SYNOPSIS - gcloud beta container hub mesh enable [GCLOUD_WIDE_FLAG ...] + gcloud beta container hub mesh enable + [--fleet-default-member-config=FLEET_DEFAULT_MEMBER_CONFIG] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Enable the Service Mesh Feature in a fleet. @@ -18,6 +20,16 @@ EXAMPLES $ gcloud beta container hub mesh enable \ --fleet-default-member-config=/path/to/service-mesh.yaml +FLAGS + --fleet-default-member-config=FLEET_DEFAULT_MEMBER_CONFIG + The path to a service-mesh.yaml configuration file. + + To enable the Service Mesh Feature with a fleet-level default + membership configuration, run: + + $ gcloud beta container hub mesh enable \ + --fleet-default-member-config=/path/to/service-mesh.yaml + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/beta/container/hub/update b/gcloud/beta/container/hub/update index f2505e0d6..97b21de41 100644 --- a/gcloud/beta/container/hub/update +++ b/gcloud/beta/container/hub/update @@ -4,6 +4,8 @@ NAME SYNOPSIS gcloud beta container hub update [--async] [--display-name=DISPLAY_NAME] [--update-labels=[KEY=VALUE,...]] + [--security-posture=SECURITY_POSTURE + --workload-vulnerability-scanning=WORKLOAD_VULNERABILITY_SCANNING] [--clear-labels | --remove-labels=[KEY,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -38,6 +40,26 @@ FLAGS contain only hyphens (-), underscores (_), lowercase characters, and numbers. + Default cluster configurations to apply across the fleet. + + Security posture config. + + --security-posture=SECURITY_POSTURE + To apply standard security posture to clusters in the fleet, + + $ gcloud beta container hub update --security-posture=standard + + SECURITY_POSTURE must be one of: disabled, standard. + + --workload-vulnerability-scanning=WORKLOAD_VULNERABILITY_SCANNING + To apply standard vulnerability scanning to clusters in the fleet, + + $ gcloud beta container hub update \ + --workload-vulnerability-scanning=standard + + WORKLOAD_VULNERABILITY_SCANNING must be one of: disabled, standard, + enterprise. + At most one of these can be specified: --clear-labels diff --git a/gcloud/beta/data-fusion/instances/create b/gcloud/beta/data-fusion/instances/create index 40f928e58..c63f3c5dd 100644 --- a/gcloud/beta/data-fusion/instances/create +++ b/gcloud/beta/data-fusion/instances/create @@ -7,7 +7,8 @@ SYNOPSIS [--async] [--edition=EDITION; default="basic"] [--enable_rbac] [--enable_stackdriver_logging] [--enable_stackdriver_monitoring] [--labels=[KEY=VALUE,...]] [--options=[KEY=VALUE,...]] - [--version=VERSION] [--zone=ZONE] [GCLOUD_WIDE_FLAG ...] + [--patch_revision=PATCH_REVISION] [--version=VERSION] [--zone=ZONE] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) If run asynchronously with --async, exits after printing an @@ -86,9 +87,13 @@ FLAGS Options to use for instance creation, specified as KEY1=VALUE1,KEY2=VALUE2. + --patch_revision=PATCH_REVISION + Patch revision version of Cloud Data Fusion to use when creating the + instance.For example: --patch_revision=6.9.2.1. + --version=VERSION The version of Cloud Data Fusion to use when creating the instance. For - example: --version=6.2.2. + example: --version=6.9.2. --zone=ZONE Compute Engine zone in which the instance will be created. Only needed diff --git a/gcloud/beta/data-fusion/instances/update b/gcloud/beta/data-fusion/instances/update index 3b04bb2aa..2b9c2f4c7 100644 --- a/gcloud/beta/data-fusion/instances/update +++ b/gcloud/beta/data-fusion/instances/update @@ -6,7 +6,8 @@ SYNOPSIS gcloud beta data-fusion instances update (INSTANCE : --location=LOCATION) [--async] [--enable_rbac] [--enable_stackdriver_logging] [--enable_stackdriver_monitoring] [--labels=[KEY=VALUE,...]] - [--options=[KEY=VALUE,...]] [--version=VERSION] [GCLOUD_WIDE_FLAG ...] + [--options=[KEY=VALUE,...]] [--patch_revision=PATCH_REVISION] + [--version=VERSION] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) If run asynchronously with --async, exits after printing an @@ -17,10 +18,17 @@ DESCRIPTION EXAMPLES To update instance 'my-instance' in project 'my-project' and location - 'my-location' to version 6.1.0.0, run: + 'my-location' to version 6.9.2, run: $ gcloud beta data-fusion instances update --project=my-project \ - --location=my-location --version=6.1.0.0 my-instance + --location=my-location --version=6.9.2 my-instance + + To update instance 'my-instance' in project 'my-project' and location + 'my-location' to patch revision '6.9.2.1', run: + + $ gcloud beta data-fusion instances update --project=my-project \ + --location=my-location --version=6.9.2 \ + --patch_revision=6.9.2.1 my-instance POSITIONAL ARGUMENTS Instance resource - Instance to update. The arguments in this group can be @@ -80,6 +88,9 @@ FLAGS Options to use for instance update, specified as KEY1=VALUE1,KEY2=VALUE2. + --patch_revision=PATCH_REVISION + Patch revision version of Cloud Data Fusion to update to. + --version=VERSION Version of Datafusion to update to. diff --git a/gcloud/beta/dataproc/clusters/create b/gcloud/beta/dataproc/clusters/create index 5a28fde29..84d8cd20c 100644 --- a/gcloud/beta/dataproc/clusters/create +++ b/gcloud/beta/dataproc/clusters/create @@ -58,6 +58,8 @@ SYNOPSIS [--image=IMAGE | --image-version=VERSION] [--kerberos-config-file=KERBEROS_CONFIG_FILE | --enable-kerberos --kerberos-root-principal-password-uri=KERBEROS_ROOT_PRINCIPAL_PASSWORD_URI [--kerberos-kms-key=KERBEROS_KMS_KEY : --kerberos-kms-key-keyring=KERBEROS_KMS_KEY_KEYRING --kerberos-kms-key-location=KERBEROS_KMS_KEY_LOCATION --kerberos-kms-key-project=KERBEROS_KMS_KEY_PROJECT]] + [--kms-key=KMS_KEY : --kms-keyring=KMS_KEYRING + --kms-location=KMS_LOCATION --kms-project=KMS_PROJECT] [--single-node | --min-num-workers=MIN_NUM_WORKERS --num-secondary-workers=NUM_SECONDARY_WORKERS --num-workers=NUM_WORKERS @@ -759,6 +761,46 @@ FLAGS line; ▫ set the property core/project. + Key resource - The Cloud KMS (Key Management Service) cryptokey that will + be used to protect the cluster. The 'Compute Engine Service Agent' service + account must hold permission 'Cloud KMS CryptoKey Encrypter/Decrypter'. + The arguments in this group can be used to specify the attributes of this + resource. + + --kms-key=KMS_KEY + ID of the key or fully qualified identifier for the key. + + To set the kms-key attribute: + ▸ provide the argument --kms-key on the command line. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --kms-keyring=KMS_KEYRING + The KMS keyring of the key. + + To set the kms-keyring attribute: + ▸ provide the argument --kms-key on the command line with a fully + specified name; + ▸ provide the argument --kms-keyring on the command line. + + --kms-location=KMS_LOCATION + The Google Cloud location for the key. + + To set the kms-location attribute: + ▸ provide the argument --kms-key on the command line with a fully + specified name; + ▸ provide the argument --kms-location on the command line. + + --kms-project=KMS_PROJECT + The Google Cloud project for the key. + + To set the kms-project attribute: + ▸ provide the argument --kms-key on the command line with a fully + specified name; + ▸ provide the argument --kms-project on the command line; + ▸ set the property core/project. + At most one of these can be specified: --single-node diff --git a/gcloud/beta/dataproc/workflow-templates/set-managed-cluster b/gcloud/beta/dataproc/workflow-templates/set-managed-cluster index 765274921..fadd214de 100644 --- a/gcloud/beta/dataproc/workflow-templates/set-managed-cluster +++ b/gcloud/beta/dataproc/workflow-templates/set-managed-cluster @@ -42,6 +42,8 @@ SYNOPSIS [--image=IMAGE | --image-version=VERSION] [--kerberos-config-file=KERBEROS_CONFIG_FILE | --enable-kerberos --kerberos-root-principal-password-uri=KERBEROS_ROOT_PRINCIPAL_PASSWORD_URI [--kerberos-kms-key=KERBEROS_KMS_KEY : --kerberos-kms-key-keyring=KERBEROS_KMS_KEY_KEYRING --kerberos-kms-key-location=KERBEROS_KMS_KEY_LOCATION --kerberos-kms-key-project=KERBEROS_KMS_KEY_PROJECT]] + [--kms-key=KMS_KEY : --kms-keyring=KMS_KEYRING + --kms-location=KMS_LOCATION --kms-project=KMS_PROJECT] [--metadata=KEY=VALUE,[KEY=VALUE,...] --scopes=SCOPE,[SCOPE,...] --service-account=SERVICE_ACCOUNT --tags=TAG,[TAG,...] --network=NETWORK | --subnet=SUBNET @@ -514,6 +516,46 @@ FLAGS line; ▫ set the property core/project. + Key resource - The Cloud KMS (Key Management Service) cryptokey that will + be used to protect the cluster. The 'Compute Engine Service Agent' service + account must hold permission 'Cloud KMS CryptoKey Encrypter/Decrypter'. + The arguments in this group can be used to specify the attributes of this + resource. + + --kms-key=KMS_KEY + ID of the key or fully qualified identifier for the key. + + To set the kms-key attribute: + ▸ provide the argument --kms-key on the command line. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --kms-keyring=KMS_KEYRING + The KMS keyring of the key. + + To set the kms-keyring attribute: + ▸ provide the argument --kms-key on the command line with a fully + specified name; + ▸ provide the argument --kms-keyring on the command line. + + --kms-location=KMS_LOCATION + The Google Cloud location for the key. + + To set the kms-location attribute: + ▸ provide the argument --kms-key on the command line with a fully + specified name; + ▸ provide the argument --kms-location on the command line. + + --kms-project=KMS_PROJECT + The Google Cloud project for the key. + + To set the kms-project attribute: + ▸ provide the argument --kms-key on the command line with a fully + specified name; + ▸ provide the argument --kms-project on the command line; + ▸ set the property core/project. + Compute Engine options for Dataproc clusters. --metadata=KEY=VALUE,[KEY=VALUE,...] diff --git a/gcloud/beta/filestore/instances/create b/gcloud/beta/filestore/instances/create index e65d5a010..c954724df 100644 --- a/gcloud/beta/filestore/instances/create +++ b/gcloud/beta/filestore/instances/create @@ -114,6 +114,7 @@ REQUIRED FLAGS ▫ 1TB-9.75TB in 256GB increments or its multiples. ▫ 10TB-100TB in 2.5TB increments or its multiples. ▸ ENTERPRISE: 1TB-10TB in 256GB increments or its multiples. + ▸ REGIONAL: 1TB-9.75TB in 256GB increments or its multiples. name The desired logical name of the volume. @@ -194,8 +195,8 @@ REQUIRED FLAGS allocated IP address range is specified, it must be one of the ranges associated with the private service access connection. When specified as a direct CIDR value, it must be a /29 CIDR block for - Basic tier or a /24 CIDR block for High Scale, Zonal or Enterprise - tier in one of the internal IP address ranges + Basic tier or a /24 CIDR block for High Scale, Zonal, Enterprise or + Regional tier in one of the internal IP address ranges (https://www.arin.net/knowledge/address_filters.html) that identifies the range of IP addresses reserved for this instance. For example, 10.0.0.0/29 or 192.168.0.0/24. The range you specify @@ -261,7 +262,7 @@ OPTIONAL FLAGS basic-ssd Performant NFS storage system using SSD. enterprise - ENTERPRISE instances offer the features and availability needed for + Enterprise instances offer the features and availability needed for mission-critical workloads. high-scale-ssd High Scale SSD instance, an alias for ZONAL. Use ZONAL instead @@ -269,6 +270,9 @@ OPTIONAL FLAGS premium Premium Filestore instance, An alias for BASIC_SSD. Use BASIC_SSD instead whenever possible. + regional + Regional instances offer the features and availability needed for + mission-critical workloads. standard Standard Filestore instance, An alias for BASIC_HDD. Use BASIC_HDD instead whenever possible. diff --git a/gcloud/beta/filestore/instances/update b/gcloud/beta/filestore/instances/update index 69cfaede3..b24a9cc08 100644 --- a/gcloud/beta/filestore/instances/update +++ b/gcloud/beta/filestore/instances/update @@ -151,6 +151,7 @@ FLAGS ▫ 1TB-9.75TB in 256GB increments or its multiples. ▫ 10TB-100TB in 2.5TB increments or its multiples. ▸ ENTERPRISE: 1TB-10TB in 256GB increments or its multiples. + ▸ REGIONAL: 1TB-9.75TB in 256GB increments or its multiples. name The desired logical name of the volume. diff --git a/gcloud/beta/firestore/databases/delete b/gcloud/beta/firestore/databases/delete new file mode 100644 index 000000000..32494a503 --- /dev/null +++ b/gcloud/beta/firestore/databases/delete @@ -0,0 +1,45 @@ +NAME + gcloud beta firestore databases delete - delete a Google Cloud Firestore + database + +SYNOPSIS + gcloud beta firestore databases delete --database=DATABASE [--etag=ETAG] + [GCLOUD_WIDE_FLAG ...] + +EXAMPLES + To delete a Firestore database test. + + $ gcloud beta firestore databases delete --database=test + + To delete the Firestore (default) database. + + $ gcloud beta firestore databases delete --database=(default) + + To delete a Firestore database test providing etag. + + $ gcloud beta 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 + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha firestore databases delete + diff --git a/gcloud/beta/firestore/databases/help b/gcloud/beta/firestore/databases/help index ed147eb70..1ebd70a3a 100644 --- a/gcloud/beta/firestore/databases/help +++ b/gcloud/beta/firestore/databases/help @@ -19,6 +19,9 @@ COMMANDS create (BETA) Create a Google Cloud Firestore database via Firestore API. + delete + (BETA) Delete a Google Cloud Firestore database. + describe (BETA) Describes information about a Cloud Firestore database. diff --git a/gcloud/beta/firestore/export b/gcloud/beta/firestore/export index 0e907c78a..4ad8991be 100644 --- a/gcloud/beta/firestore/export +++ b/gcloud/beta/firestore/export @@ -79,14 +79,11 @@ FLAGS --snapshot-time=SNAPSHOT_TIME The version of the database to export. - The timestamp must be rounded to the minute, in the past, and not older - than 5 days. Please choose a reasonable timestamp based on prior - knowledge on how long exports take as data at provided snapshot - timestamp can expire during export. - - If specified, then the exported documents will represent a consistent - view of the database at the provided time. Otherwise, there are no - guarantees about the consistency of the exported documents. + The timestamp must be in the past, rounded to the minute and not older + than earliestVersionTime. If specified, then the exported documents + will represent a consistent view of the database at the provided time. + Otherwise, there are no guarantees about the consistency of the + exported documents. For example, to operate on snapshot time 2023-05-26T10:20:00.00Z: diff --git a/gcloud/beta/metastore/services/update b/gcloud/beta/metastore/services/update index 8d9310260..842b6b1f9 100644 --- a/gcloud/beta/metastore/services/update +++ b/gcloud/beta/metastore/services/update @@ -75,8 +75,8 @@ FLAGS complete. --data-catalog-sync - A boolean flag to determine whether Dataproc Metastore metadata sync to - Data Catalog should be enabled, false if unspecified. Mutually + Boolean flag to determine whether or not Dataproc Metastore metadata + sync to Data Catalog is enabled, false if unspecified. Mutually exclusive with flag --encryption-kms-key. Cannot be updated if the service uses customer-managed encryption keys. diff --git a/gcloud/beta/run/jobs/executions/cancel b/gcloud/beta/run/jobs/executions/cancel index bfb61bb3d..a18bd87e7 100644 --- a/gcloud/beta/run/jobs/executions/cancel +++ b/gcloud/beta/run/jobs/executions/cancel @@ -51,8 +51,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud run jobs executions cancel $ gcloud alpha run jobs executions cancel diff --git a/gcloud/beta/sql/instances/create b/gcloud/beta/sql/instances/create index bf99f633e..d0e335c3f 100644 --- a/gcloud/beta/sql/instances/create +++ b/gcloud/beta/sql/instances/create @@ -309,6 +309,10 @@ FLAGS production Production updates are stable and recommended for applications in production. + week5 + week5 updates release after the production updates. Use the week5 + channel to receive a 5 week advance notification about the upcoming + maintenance, so you can prepare your application for the release. --maintenance-window-day=MAINTENANCE_WINDOW_DAY Day of week for maintenance window, in UTC time zone. diff --git a/gcloud/beta/sql/instances/list b/gcloud/beta/sql/instances/list index 450572998..a305df659 100644 --- a/gcloud/beta/sql/instances/list +++ b/gcloud/beta/sql/instances/list @@ -3,8 +3,9 @@ NAME project SYNOPSIS - gcloud beta sql instances list [--show-edition] [--filter=EXPRESSION] - [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + gcloud beta sql instances list [--show-edition] + [--show-sql-network-architecture] [--filter=EXPRESSION] [--limit=LIMIT] + [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -15,6 +16,12 @@ FLAGS --show-edition Show the edition field. + --show-sql-network-architecture + Show the instance's current SqlNetworkArchitecture backend in addition + to the default output list. An instance could use either the old or new + network architecture. The new network architecture offers better + isolation, reliability, and faster new feature adoption. + LIST COMMAND FLAGS --filter=EXPRESSION Apply a Boolean filter EXPRESSION to each resource item to be listed. diff --git a/gcloud/beta/sql/instances/patch b/gcloud/beta/sql/instances/patch index 76a526aa7..c38239920 100644 --- a/gcloud/beta/sql/instances/patch +++ b/gcloud/beta/sql/instances/patch @@ -44,6 +44,7 @@ SYNOPSIS [--storage-auto-increase-limit=STORAGE_AUTO_INCREASE_LIMIT] [--storage-size=STORAGE_SIZE] [--threads-per-core=THREADS_PER_CORE] [--tier=TIER, -t TIER] [--update-labels=[KEY=VALUE,...]] + [--upgrade-sql-network-architecture] [--allowed-psc-projects=PROJECT,[PROJECT,...] | --clear-allowed-psc-projects] [--authorized-gae-apps=APP,[APP,...] | --clear-gae-apps] @@ -247,6 +248,10 @@ FLAGS production Production updates are stable and recommended for applications in production. + week5 + week5 updates release after the production updates. Use the week5 + channel to receive a 5 week advance notification about the upcoming + maintenance, so you can prepare your application for the release. --maintenance-version=MAINTENANCE_VERSION The desired maintenance version of the instance. @@ -388,6 +393,11 @@ FLAGS contain only hyphens (-), underscores (_), lowercase characters, and numbers. + --upgrade-sql-network-architecture + Upgrade from old network architecture to new network architecture. The + new network architecture offers better isolation, reliability, and + faster new feature adoption. + At most one of these can be specified: --allowed-psc-projects=PROJECT,[PROJECT,...] diff --git a/gcloud/compute/tpus/tpu-vm/update b/gcloud/compute/tpus/tpu-vm/update index 2cc6b7f49..a12a4b098 100644 --- a/gcloud/compute/tpus/tpu-vm/update +++ b/gcloud/compute/tpus/tpu-vm/update @@ -5,6 +5,7 @@ SYNOPSIS gcloud compute tpus tpu-vm update (TPU : --zone=ZONE) [--add-tags=[TAGS,...]] [--async] [--description=DESCRIPTION] [--internal-ips] [--update-labels=[KEY=VALUE,...]] + [--attach-disk=[SOURCE=DATA_DISK,...] | --detach-disk=DATA_DISK] [--clear-labels | --remove-labels=[KEY,...]] [--clear-tags | --remove-tags=[TAG,...]] [GCLOUD_WIDE_FLAG ...] @@ -96,6 +97,45 @@ FLAGS See https://cloud.google.com/compute/docs/labeling-resources for details. + At most one of these can be specified: + + --attach-disk=[SOURCE=DATA_DISK,...] + Attach a data disk to the TPU VM. For example, + + $ gcloud compute tpus tpu-vm update example-tpu \ + --attach-disk \ + source=projects/my-project/zones/us-central1-c/disks/my-disk,\ + mode=read-only --zone=us-central1-c + + attaches the disk named + 'projects/my-project/zones/us-central1-c/disks/my-disk' to a TPU VM + named 'example-tpu' in read-only mode in zone us-central1-c. + + The following keys are allowed: + + source + Specify the full path to an existing disk. Required. The disk + must be in the same zone. + + mode + Specify the mode in which to attach this disk. Valid options are + 'read-write', 'read-only'. If not specified, the default is + 'read-write'. + + --detach-disk=DATA_DISK + Detach a data disk from the TPU VM. For example, + + This flag must be repeated to provide multiple data disks. For + example: + + $ gcloud compute tpus tpu-vm update example-tpu \ + --detach-disk=projects/my-project/zones/us-central1-c/disks/\ + my-disk --zone=us-central1-c + + detaches the disk named + 'projects/my-project/zones/us-central1-c/disks/my-disk' from a TPU VM + named 'example-tpu' in zone us-central1-c. + At most one of these can be specified: --clear-labels diff --git a/gcloud/config/get b/gcloud/config/get index 45a4f9c0b..69e46b88d 100644 --- a/gcloud/config/get +++ b/gcloud/config/get @@ -1235,6 +1235,20 @@ AVAILABLE PROPERTIES max_retry_delay Max second delay between retriable operations. + multipart_chunksize + Specifies partition size in bytes of each part of a multipart + upload made by the Boto3 client. To calculate the maximum size of a + Boto3 client multipart upload, multiply the multipart_chunk value + by the maximum number of parts the API allows. For AWS S3 this + limit is 10000. Values can be provided either in bytes or as + human-readable values (e.g., "150M" to represent 150 mebibytes). + + multipart_threshold + Files larger than this threshold will be partitioned into parts, + uploaded separately by the Boto3 client, and then combined into a + single object. Otherwise, files smaller than this threshold will be + uploaded by the Boto3 client in a single stream. + parallel_composite_upload_compatibility_check Determines if the GET bucket call should be performed to check if the default storage class and retention period for the destination diff --git a/gcloud/config/help b/gcloud/config/help index bdf9f8871..6e0a71952 100644 --- a/gcloud/config/help +++ b/gcloud/config/help @@ -1267,6 +1267,20 @@ AVAILABLE PROPERTIES max_retry_delay Max second delay between retriable operations. + multipart_chunksize + Specifies partition size in bytes of each part of a multipart + upload made by the Boto3 client. To calculate the maximum size of a + Boto3 client multipart upload, multiply the multipart_chunk value + by the maximum number of parts the API allows. For AWS S3 this + limit is 10000. Values can be provided either in bytes or as + human-readable values (e.g., "150M" to represent 150 mebibytes). + + multipart_threshold + Files larger than this threshold will be partitioned into parts, + uploaded separately by the Boto3 client, and then combined into a + single object. Otherwise, files smaller than this threshold will be + uploaded by the Boto3 client in a single stream. + parallel_composite_upload_compatibility_check Determines if the GET bucket call should be performed to check if the default storage class and retention period for the destination diff --git a/gcloud/config/list b/gcloud/config/list index 88a85ca63..6cbbb51f8 100644 --- a/gcloud/config/list +++ b/gcloud/config/list @@ -1279,6 +1279,20 @@ AVAILABLE PROPERTIES max_retry_delay Max second delay between retriable operations. + multipart_chunksize + Specifies partition size in bytes of each part of a multipart + upload made by the Boto3 client. To calculate the maximum size of a + Boto3 client multipart upload, multiply the multipart_chunk value + by the maximum number of parts the API allows. For AWS S3 this + limit is 10000. Values can be provided either in bytes or as + human-readable values (e.g., "150M" to represent 150 mebibytes). + + multipart_threshold + Files larger than this threshold will be partitioned into parts, + uploaded separately by the Boto3 client, and then combined into a + single object. Otherwise, files smaller than this threshold will be + uploaded by the Boto3 client in a single stream. + parallel_composite_upload_compatibility_check Determines if the GET bucket call should be performed to check if the default storage class and retention period for the destination diff --git a/gcloud/config/set b/gcloud/config/set index 7e6329bbb..9971742d8 100644 --- a/gcloud/config/set +++ b/gcloud/config/set @@ -1282,6 +1282,20 @@ AVAILABLE PROPERTIES max_retry_delay Max second delay between retriable operations. + multipart_chunksize + Specifies partition size in bytes of each part of a multipart + upload made by the Boto3 client. To calculate the maximum size of a + Boto3 client multipart upload, multiply the multipart_chunk value + by the maximum number of parts the API allows. For AWS S3 this + limit is 10000. Values can be provided either in bytes or as + human-readable values (e.g., "150M" to represent 150 mebibytes). + + multipart_threshold + Files larger than this threshold will be partitioned into parts, + uploaded separately by the Boto3 client, and then combined into a + single object. Otherwise, files smaller than this threshold will be + uploaded by the Boto3 client in a single stream. + parallel_composite_upload_compatibility_check Determines if the GET bucket call should be performed to check if the default storage class and retention period for the destination diff --git a/gcloud/config/unset b/gcloud/config/unset index acf21fbab..ec4363af1 100644 --- a/gcloud/config/unset +++ b/gcloud/config/unset @@ -1243,6 +1243,20 @@ AVAILABLE PROPERTIES max_retry_delay Max second delay between retriable operations. + multipart_chunksize + Specifies partition size in bytes of each part of a multipart + upload made by the Boto3 client. To calculate the maximum size of a + Boto3 client multipart upload, multiply the multipart_chunk value + by the maximum number of parts the API allows. For AWS S3 this + limit is 10000. Values can be provided either in bytes or as + human-readable values (e.g., "150M" to represent 150 mebibytes). + + multipart_threshold + Files larger than this threshold will be partitioned into parts, + uploaded separately by the Boto3 client, and then combined into a + single object. Otherwise, files smaller than this threshold will be + uploaded by the Boto3 client in a single stream. + parallel_composite_upload_compatibility_check Determines if the GET bucket call should be performed to check if the default storage class and retention period for the destination diff --git a/gcloud/container/binauthz/attestations/list b/gcloud/container/binauthz/attestations/list index 0dce0538f..de4d7c1cc 100644 --- a/gcloud/container/binauthz/attestations/list +++ b/gcloud/container/binauthz/attestations/list @@ -3,17 +3,18 @@ NAME attestations SYNOPSIS - gcloud container binauthz attestations list - (--attestor=ATTESTOR : --attestor-project=ATTESTOR_PROJECT) - [--artifact-url=ARTIFACT_URL] [--filter=EXPRESSION] [--limit=LIMIT] - [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] - [GCLOUD_WIDE_FLAG ...] + gcloud container binauthz attestations list [--artifact-url=ARTIFACT_URL] + [--attestor=ATTESTOR : --attestor-project=ATTESTOR_PROJECT] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] DESCRIPTION This command lists Binary Authorization attestations for your project. - Command line flags specify which artifact to list the attestations for. If - no artifact is specified, then this lists all URLs with associated - occurrences. + Command line flags specify which attestor and artifact to list the + attestations for. If no attestor is specified, this lists all attestations + in the project, which requires the containeranalysis.occurrences.get + permission. If no artifact is specified, then this lists all URLs with + associated occurrences. EXAMPLES List the Occurrence messages for all attestations bound to the passed @@ -29,15 +30,17 @@ EXAMPLES --attestor=projects/foo/attestors/bar \ --artifact-url='gcr.io/foo/example-image@sha256:abcd' -REQUIRED FLAGS +FLAGS + --artifact-url=ARTIFACT_URL + Container URL. May be in the gcr.io/repository/image format, or may + optionally contain the http or https scheme + Attestor resource - The Attestor whose Container Analysis Note will be queried for attestations. Note that the caller must have the containeranalysis.notes.listOccurrences permission on the note being queried. 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. @@ -57,11 +60,6 @@ REQUIRED FLAGS ▸ provide the argument --project on the command line; ▸ set the property core/project. -FLAGS - --artifact-url=ARTIFACT_URL - Container URL. May be in the gcr.io/repository/image format, or may - optionally contain the http or https scheme - LIST COMMAND FLAGS --filter=EXPRESSION Apply a Boolean filter EXPRESSION to each resource item to be listed. diff --git a/gcloud/container/fleet/create b/gcloud/container/fleet/create index 535f42401..1520503ff 100644 --- a/gcloud/container/fleet/create +++ b/gcloud/container/fleet/create @@ -3,7 +3,10 @@ NAME SYNOPSIS gcloud container fleet create [--async] [--display-name=DISPLAY_NAME] - [--labels=[KEY=VALUE,...]] [GCLOUD_WIDE_FLAG ...] + [--labels=[KEY=VALUE,...]] + [--security-posture=SECURITY_POSTURE + --workload-vulnerability-scanning=WORKLOAD_VULNERABILITY_SCANNING] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION This command can fail for the following reasons: @@ -36,6 +39,26 @@ FLAGS contain only hyphens (-), underscores (_), lowercase characters, and numbers. + Default cluster configurations to apply across the fleet. + + Security posture config. + + --security-posture=SECURITY_POSTURE + To apply standard security posture to clusters in the fleet, + + $ gcloud container fleet create --security-posture=standard + + SECURITY_POSTURE must be one of: disabled, standard. + + --workload-vulnerability-scanning=WORKLOAD_VULNERABILITY_SCANNING + To apply standard vulnerability scanning to clusters in the fleet, + + $ gcloud container fleet create \ + --workload-vulnerability-scanning=standard + + WORKLOAD_VULNERABILITY_SCANNING must be one of: disabled, standard, + enterprise. + 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/container/fleet/identity-service/apply b/gcloud/container/fleet/identity-service/apply index e473cf175..018aa8803 100644 --- a/gcloud/container/fleet/identity-service/apply +++ b/gcloud/container/fleet/identity-service/apply @@ -1,19 +1,16 @@ NAME - gcloud container fleet identity-service apply - update an Identity Service - Feature Spec + gcloud container fleet identity-service apply - update the Identity Service + Feature SYNOPSIS gcloud container fleet identity-service apply - ([--config=CONFIG : [--membership=MEMBERSHIP : --location=LOCATION]]) + (--fleet-default-member-config=FLEET_DEFAULT_MEMBER_CONFIG + [(--config=CONFIG | --origin=ORIGIN) + : [--membership=MEMBERSHIP : --location=LOCATION]]) [GCLOUD_WIDE_FLAG ...] DESCRIPTION - Applies the authentication configuration to the Identity Service feature - spec for this membership. This configuration is now the "source of truth" - for the cluster and can only be updated by using this command or the Cloud - Console. Any local authentication configuration on the cluster is - overwritten by this configuration, including any local updates made after - you run this command. + This command updates the Identity Service Feature in a fleet. EXAMPLES To apply an Identity Service configuration to a membership, run: @@ -22,14 +19,31 @@ EXAMPLES --membership=MEMBERSHIP_NAME \ --config=/path/to/identity-service.yaml + To create or modify a fleet-level default membership configuration, run: + + $ gcloud container fleet identity-service apply \ + --fleet-default-member-config=/path/to/identity-service.yaml + + To apply an existing fleet-level default membership configuration to a + membership, run: + + $ gcloud container fleet identity-service apply --origin=fleet \ + --membership=MEMBERSHIP_NAME + REQUIRED FLAGS At least one of these must be specified: - --config=CONFIG - The path to an identity-service.yaml config file. + --fleet-default-member-config=FLEET_DEFAULT_MEMBER_CONFIG + The path to an identity-service.yaml configuration file. - This flag argument must be specified if any of the other arguments in - this group are specified. + Exactly one of these must be specified: + + --config=CONFIG + The path to an identity-service.yaml configuration file. + + --origin=ORIGIN + Applies the fleet-level default membership configuration to a + membership. ORIGIN must be (only one value is supported): fleet. Membership resource - The group of arguments defining a membership. The arguments in this group can be used to specify the attributes of this diff --git a/gcloud/container/fleet/identity-service/delete b/gcloud/container/fleet/identity-service/delete index 91b8d4fbd..4e2141e29 100644 --- a/gcloud/container/fleet/identity-service/delete +++ b/gcloud/container/fleet/identity-service/delete @@ -1,21 +1,37 @@ NAME - gcloud container fleet identity-service delete - remove the Identity - Service Feature Spec for the given membership + gcloud container fleet identity-service delete - delete a resource from the + Identity Service Feature SYNOPSIS gcloud container fleet identity-service delete + [--fleet-default-member-config] [--membership=MEMBERSHIP : --location=LOCATION] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - Removes the Identity Service Feature Spec for the given membership. + Deletes a resource from the Identity Service Feature. EXAMPLES - To delete an Identity Service configuration for a membership, run: + To delete the Identity Service configuration from a membership, run: $ gcloud container fleet identity-service delete \ --membership=MEMBERSHIP_NAME + To delete the fleet-level default membership configuration, run: + + $ gcloud container fleet identity-service delete \ + --fleet-default-member-config + FLAGS + --fleet-default-member-config + If specified, deletes the default membership configuration present in + your fleet. + + To delete the default membership configuration present in your + fleet, run: + + $ gcloud container fleet identity-service delete \ + --fleet-default-member-config + Membership resource - The group of arguments defining a membership. The arguments in this group can be used to specify the attributes of this resource. (NOTE) Some attributes are not given arguments in this group but diff --git a/gcloud/container/fleet/identity-service/enable b/gcloud/container/fleet/identity-service/enable index 4d4d0c874..67c135856 100644 --- a/gcloud/container/fleet/identity-service/enable +++ b/gcloud/container/fleet/identity-service/enable @@ -1,9 +1,11 @@ NAME - gcloud container fleet identity-service enable - enable Identity Service - Feature + gcloud container fleet identity-service enable - enable the Identity + Service Feature SYNOPSIS - gcloud container fleet identity-service enable [GCLOUD_WIDE_FLAG ...] + gcloud container fleet identity-service enable + [--fleet-default-member-config=FLEET_DEFAULT_MEMBER_CONFIG] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION This command enables the Identity Service Feature in a fleet. @@ -13,6 +15,26 @@ EXAMPLES $ gcloud container fleet identity-service enable + To enable the Identity Service Feature with a fleet-level default + membership configuration, run: + + $ gcloud container fleet identity-service enable \ + --fleet-default-member-config=/path/to/identity-service.yaml + +FLAGS + --fleet-default-member-config=FLEET_DEFAULT_MEMBER_CONFIG + The path to an identity-service.yaml identity configuration file. If + specified, this configuration would be the default Identity Service + configuration for all memberships in your fleet. It could be overridden + with a membership-specific configuration by using the the Apply command + with the --config argument. + + To enable the Identity Service Feature with a fleet-level default + membership configuration, run: + + $ gcloud container fleet identity-service enable \ + --fleet-default-member-config=/path/to/identity-service.yaml + 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/container/fleet/identity-service/help b/gcloud/container/fleet/identity-service/help index 781c77264..b4bdb2b75 100644 --- a/gcloud/container/fleet/identity-service/help +++ b/gcloud/container/fleet/identity-service/help @@ -16,10 +16,10 @@ COMMANDS COMMAND is one of the following: apply - Update an Identity Service Feature Spec. + Update the Identity Service Feature. delete - Remove the Identity Service Feature Spec for the given membership. + Delete a resource from the Identity Service Feature. describe Prints the status of all clusters with Identity Service installed. @@ -28,7 +28,7 @@ COMMANDS Disable Identity Service Feature. enable - Enable Identity Service Feature. + Enable the Identity Service Feature. NOTES These variants are also available: diff --git a/gcloud/container/fleet/mesh/disable b/gcloud/container/fleet/mesh/disable index fd3c8f376..18c0a64ac 100644 --- a/gcloud/container/fleet/mesh/disable +++ b/gcloud/container/fleet/mesh/disable @@ -2,7 +2,8 @@ NAME gcloud container fleet mesh disable - disable Service Mesh Feature SYNOPSIS - gcloud container fleet mesh disable [--force] [GCLOUD_WIDE_FLAG ...] + gcloud container fleet mesh disable [--fleet-default-member-config] + [--force] [GCLOUD_WIDE_FLAG ...] DESCRIPTION Disable the Service Mesh Feature in a fleet. @@ -17,6 +18,15 @@ EXAMPLES $ gcloud container fleet mesh disable --fleet-default-member-config FLAGS + --fleet-default-member-config + If specified, deletes the default membership configuration present in + your fleet. + + To delete the fleet-level default Membership configuration present in + your fleet, run: + + $ gcloud container fleet mesh disable --fleet-default-member-config + --force Disable this feature, even if it is currently in use. Force disablement may result in unexpected behavior. diff --git a/gcloud/container/fleet/mesh/enable b/gcloud/container/fleet/mesh/enable index c0c6eef46..7aa7c9d33 100644 --- a/gcloud/container/fleet/mesh/enable +++ b/gcloud/container/fleet/mesh/enable @@ -2,7 +2,9 @@ NAME gcloud container fleet mesh enable - enable Service Mesh Feature SYNOPSIS - gcloud container fleet mesh enable [GCLOUD_WIDE_FLAG ...] + gcloud container fleet mesh enable + [--fleet-default-member-config=FLEET_DEFAULT_MEMBER_CONFIG] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION Enable the Service Mesh Feature in a fleet. @@ -18,6 +20,16 @@ EXAMPLES $ gcloud container fleet mesh enable \ --fleet-default-member-config=/path/to/service-mesh.yaml +FLAGS + --fleet-default-member-config=FLEET_DEFAULT_MEMBER_CONFIG + The path to a service-mesh.yaml configuration file. + + To enable the Service Mesh Feature with a fleet-level default + membership configuration, run: + + $ gcloud container fleet mesh enable \ + --fleet-default-member-config=/path/to/service-mesh.yaml + 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/container/fleet/mesh/update b/gcloud/container/fleet/mesh/update index f67553d9b..28e765a2b 100644 --- a/gcloud/container/fleet/mesh/update +++ b/gcloud/container/fleet/mesh/update @@ -4,7 +4,9 @@ NAME SYNOPSIS gcloud container fleet mesh update - ([(--control-plane=CONTROL_PLANE --management=MANAGEMENT) + (--fleet-default-member-config=FLEET_DEFAULT_MEMBER_CONFIG + | [(--control-plane=CONTROL_PLANE + --management=MANAGEMENT --origin=ORIGIN) : [--memberships=[MEMBERSHIPS,...] : --location=LOCATION]]) [GCLOUD_WIDE_FLAG ...] @@ -22,6 +24,15 @@ EXAMPLES REQUIRED FLAGS Exactly one of these must be specified: + --fleet-default-member-config=FLEET_DEFAULT_MEMBER_CONFIG + The path to a service-mesh.yaml configuration file. + + To enable the Service Mesh Feature with a fleet-level default + membership configuration, run: + + $ gcloud container fleet mesh update \ + --fleet-default-member-config=/path/to/service-mesh.yaml + At least one of these must be specified: --control-plane=CONTROL_PLANE @@ -36,6 +47,10 @@ REQUIRED FLAGS The management mode to update to. MANAGEMENT must be one of: automatic, manual. + --origin=ORIGIN + Changing the origin of the membership. ORIGIN must be (only one + value is supported): fleet. + Membership resource - The group of arguments defining one or more memberships. The arguments in this group can be used to specify the attributes of this resource. (NOTE) Some attributes are not given diff --git a/gcloud/container/fleet/update b/gcloud/container/fleet/update index 7bddb5ef8..dec1e2079 100644 --- a/gcloud/container/fleet/update +++ b/gcloud/container/fleet/update @@ -4,6 +4,8 @@ NAME SYNOPSIS gcloud container fleet update [--async] [--display-name=DISPLAY_NAME] [--update-labels=[KEY=VALUE,...]] + [--security-posture=SECURITY_POSTURE + --workload-vulnerability-scanning=WORKLOAD_VULNERABILITY_SCANNING] [--clear-labels | --remove-labels=[KEY,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -38,6 +40,26 @@ FLAGS contain only hyphens (-), underscores (_), lowercase characters, and numbers. + Default cluster configurations to apply across the fleet. + + Security posture config. + + --security-posture=SECURITY_POSTURE + To apply standard security posture to clusters in the fleet, + + $ gcloud container fleet update --security-posture=standard + + SECURITY_POSTURE must be one of: disabled, standard. + + --workload-vulnerability-scanning=WORKLOAD_VULNERABILITY_SCANNING + To apply standard vulnerability scanning to clusters in the fleet, + + $ gcloud container fleet update \ + --workload-vulnerability-scanning=standard + + WORKLOAD_VULNERABILITY_SCANNING must be one of: disabled, standard, + enterprise. + At most one of these can be specified: --clear-labels diff --git a/gcloud/container/hub/create b/gcloud/container/hub/create index a8fad8825..704275d40 100644 --- a/gcloud/container/hub/create +++ b/gcloud/container/hub/create @@ -3,7 +3,10 @@ NAME SYNOPSIS gcloud container hub create [--async] [--display-name=DISPLAY_NAME] - [--labels=[KEY=VALUE,...]] [GCLOUD_WIDE_FLAG ...] + [--labels=[KEY=VALUE,...]] + [--security-posture=SECURITY_POSTURE + --workload-vulnerability-scanning=WORKLOAD_VULNERABILITY_SCANNING] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION This command can fail for the following reasons: @@ -36,6 +39,26 @@ FLAGS contain only hyphens (-), underscores (_), lowercase characters, and numbers. + Default cluster configurations to apply across the fleet. + + Security posture config. + + --security-posture=SECURITY_POSTURE + To apply standard security posture to clusters in the fleet, + + $ gcloud container hub create --security-posture=standard + + SECURITY_POSTURE must be one of: disabled, standard. + + --workload-vulnerability-scanning=WORKLOAD_VULNERABILITY_SCANNING + To apply standard vulnerability scanning to clusters in the fleet, + + $ gcloud container hub create \ + --workload-vulnerability-scanning=standard + + WORKLOAD_VULNERABILITY_SCANNING must be one of: disabled, standard, + enterprise. + 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/container/hub/identity-service/apply b/gcloud/container/hub/identity-service/apply index 2f88d9343..86806ce88 100644 --- a/gcloud/container/hub/identity-service/apply +++ b/gcloud/container/hub/identity-service/apply @@ -1,19 +1,16 @@ NAME - gcloud container hub identity-service apply - update an Identity Service - Feature Spec + gcloud container hub identity-service apply - update the Identity Service + Feature SYNOPSIS gcloud container hub identity-service apply - ([--config=CONFIG : [--membership=MEMBERSHIP : --location=LOCATION]]) + (--fleet-default-member-config=FLEET_DEFAULT_MEMBER_CONFIG + [(--config=CONFIG | --origin=ORIGIN) + : [--membership=MEMBERSHIP : --location=LOCATION]]) [GCLOUD_WIDE_FLAG ...] DESCRIPTION - Applies the authentication configuration to the Identity Service feature - spec for this membership. This configuration is now the "source of truth" - for the cluster and can only be updated by using this command or the Cloud - Console. Any local authentication configuration on the cluster is - overwritten by this configuration, including any local updates made after - you run this command. + This command updates the Identity Service Feature in a fleet. EXAMPLES To apply an Identity Service configuration to a membership, run: @@ -22,14 +19,31 @@ EXAMPLES --membership=MEMBERSHIP_NAME \ --config=/path/to/identity-service.yaml + To create or modify a fleet-level default membership configuration, run: + + $ gcloud container hub identity-service apply \ + --fleet-default-member-config=/path/to/identity-service.yaml + + To apply an existing fleet-level default membership configuration to a + membership, run: + + $ gcloud container hub identity-service apply --origin=fleet \ + --membership=MEMBERSHIP_NAME + REQUIRED FLAGS At least one of these must be specified: - --config=CONFIG - The path to an identity-service.yaml config file. + --fleet-default-member-config=FLEET_DEFAULT_MEMBER_CONFIG + The path to an identity-service.yaml configuration file. - This flag argument must be specified if any of the other arguments in - this group are specified. + Exactly one of these must be specified: + + --config=CONFIG + The path to an identity-service.yaml configuration file. + + --origin=ORIGIN + Applies the fleet-level default membership configuration to a + membership. ORIGIN must be (only one value is supported): fleet. Membership resource - The group of arguments defining a membership. The arguments in this group can be used to specify the attributes of this diff --git a/gcloud/container/hub/identity-service/delete b/gcloud/container/hub/identity-service/delete index eab98eeb7..2afb43b2a 100644 --- a/gcloud/container/hub/identity-service/delete +++ b/gcloud/container/hub/identity-service/delete @@ -1,21 +1,37 @@ NAME - gcloud container hub identity-service delete - remove the Identity Service - Feature Spec for the given membership + gcloud container hub identity-service delete - delete a resource from the + Identity Service Feature SYNOPSIS gcloud container hub identity-service delete + [--fleet-default-member-config] [--membership=MEMBERSHIP : --location=LOCATION] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - Removes the Identity Service Feature Spec for the given membership. + Deletes a resource from the Identity Service Feature. EXAMPLES - To delete an Identity Service configuration for a membership, run: + To delete the Identity Service configuration from a membership, run: $ gcloud container hub identity-service delete \ --membership=MEMBERSHIP_NAME + To delete the fleet-level default membership configuration, run: + + $ gcloud container hub identity-service delete \ + --fleet-default-member-config + FLAGS + --fleet-default-member-config + If specified, deletes the default membership configuration present in + your fleet. + + To delete the default membership configuration present in your + fleet, run: + + $ gcloud container hub identity-service delete \ + --fleet-default-member-config + Membership resource - The group of arguments defining a membership. The arguments in this group can be used to specify the attributes of this resource. (NOTE) Some attributes are not given arguments in this group but diff --git a/gcloud/container/hub/identity-service/enable b/gcloud/container/hub/identity-service/enable index 307ec6a12..09896c753 100644 --- a/gcloud/container/hub/identity-service/enable +++ b/gcloud/container/hub/identity-service/enable @@ -1,9 +1,11 @@ NAME - gcloud container hub identity-service enable - enable Identity Service + gcloud container hub identity-service enable - enable the Identity Service Feature SYNOPSIS - gcloud container hub identity-service enable [GCLOUD_WIDE_FLAG ...] + gcloud container hub identity-service enable + [--fleet-default-member-config=FLEET_DEFAULT_MEMBER_CONFIG] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION This command enables the Identity Service Feature in a fleet. @@ -13,6 +15,26 @@ EXAMPLES $ gcloud container hub identity-service enable + To enable the Identity Service Feature with a fleet-level default + membership configuration, run: + + $ gcloud container hub identity-service enable \ + --fleet-default-member-config=/path/to/identity-service.yaml + +FLAGS + --fleet-default-member-config=FLEET_DEFAULT_MEMBER_CONFIG + The path to an identity-service.yaml identity configuration file. If + specified, this configuration would be the default Identity Service + configuration for all memberships in your fleet. It could be overridden + with a membership-specific configuration by using the the Apply command + with the --config argument. + + To enable the Identity Service Feature with a fleet-level default + membership configuration, run: + + $ gcloud container hub identity-service enable \ + --fleet-default-member-config=/path/to/identity-service.yaml + 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/container/hub/identity-service/help b/gcloud/container/hub/identity-service/help index 613c1df73..234923052 100644 --- a/gcloud/container/hub/identity-service/help +++ b/gcloud/container/hub/identity-service/help @@ -16,10 +16,10 @@ COMMANDS COMMAND is one of the following: apply - Update an Identity Service Feature Spec. + Update the Identity Service Feature. delete - Remove the Identity Service Feature Spec for the given membership. + Delete a resource from the Identity Service Feature. describe Prints the status of all clusters with Identity Service installed. @@ -28,7 +28,7 @@ COMMANDS Disable Identity Service Feature. enable - Enable Identity Service Feature. + Enable the Identity Service Feature. NOTES These variants are also available: diff --git a/gcloud/container/hub/mesh/disable b/gcloud/container/hub/mesh/disable index e73e147c0..2943e42a8 100644 --- a/gcloud/container/hub/mesh/disable +++ b/gcloud/container/hub/mesh/disable @@ -2,7 +2,8 @@ NAME gcloud container hub mesh disable - disable Service Mesh Feature SYNOPSIS - gcloud container hub mesh disable [--force] [GCLOUD_WIDE_FLAG ...] + gcloud container hub mesh disable [--fleet-default-member-config] [--force] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION Disable the Service Mesh Feature in a fleet. @@ -17,6 +18,15 @@ EXAMPLES $ gcloud container hub mesh disable --fleet-default-member-config FLAGS + --fleet-default-member-config + If specified, deletes the default membership configuration present in + your fleet. + + To delete the fleet-level default Membership configuration present in + your fleet, run: + + $ gcloud container hub mesh disable --fleet-default-member-config + --force Disable this feature, even if it is currently in use. Force disablement may result in unexpected behavior. diff --git a/gcloud/container/hub/mesh/enable b/gcloud/container/hub/mesh/enable index 72dd739e0..f4fa88e73 100644 --- a/gcloud/container/hub/mesh/enable +++ b/gcloud/container/hub/mesh/enable @@ -2,7 +2,9 @@ NAME gcloud container hub mesh enable - enable Service Mesh Feature SYNOPSIS - gcloud container hub mesh enable [GCLOUD_WIDE_FLAG ...] + gcloud container hub mesh enable + [--fleet-default-member-config=FLEET_DEFAULT_MEMBER_CONFIG] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION Enable the Service Mesh Feature in a fleet. @@ -18,6 +20,16 @@ EXAMPLES $ gcloud container hub mesh enable \ --fleet-default-member-config=/path/to/service-mesh.yaml +FLAGS + --fleet-default-member-config=FLEET_DEFAULT_MEMBER_CONFIG + The path to a service-mesh.yaml configuration file. + + To enable the Service Mesh Feature with a fleet-level default + membership configuration, run: + + $ gcloud container hub mesh enable \ + --fleet-default-member-config=/path/to/service-mesh.yaml + 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/container/hub/mesh/update b/gcloud/container/hub/mesh/update index 709a41dd6..2861336b5 100644 --- a/gcloud/container/hub/mesh/update +++ b/gcloud/container/hub/mesh/update @@ -4,7 +4,9 @@ NAME SYNOPSIS gcloud container hub mesh update - ([(--control-plane=CONTROL_PLANE --management=MANAGEMENT) + (--fleet-default-member-config=FLEET_DEFAULT_MEMBER_CONFIG + | [(--control-plane=CONTROL_PLANE + --management=MANAGEMENT --origin=ORIGIN) : [--memberships=[MEMBERSHIPS,...] : --location=LOCATION]]) [GCLOUD_WIDE_FLAG ...] @@ -22,6 +24,15 @@ EXAMPLES REQUIRED FLAGS Exactly one of these must be specified: + --fleet-default-member-config=FLEET_DEFAULT_MEMBER_CONFIG + The path to a service-mesh.yaml configuration file. + + To enable the Service Mesh Feature with a fleet-level default + membership configuration, run: + + $ gcloud container hub mesh update \ + --fleet-default-member-config=/path/to/service-mesh.yaml + At least one of these must be specified: --control-plane=CONTROL_PLANE @@ -36,6 +47,10 @@ REQUIRED FLAGS The management mode to update to. MANAGEMENT must be one of: automatic, manual. + --origin=ORIGIN + Changing the origin of the membership. ORIGIN must be (only one + value is supported): fleet. + Membership resource - The group of arguments defining one or more memberships. The arguments in this group can be used to specify the attributes of this resource. (NOTE) Some attributes are not given diff --git a/gcloud/container/hub/update b/gcloud/container/hub/update index dab2e8d25..ebf374c2b 100644 --- a/gcloud/container/hub/update +++ b/gcloud/container/hub/update @@ -4,6 +4,8 @@ NAME SYNOPSIS gcloud container hub update [--async] [--display-name=DISPLAY_NAME] [--update-labels=[KEY=VALUE,...]] + [--security-posture=SECURITY_POSTURE + --workload-vulnerability-scanning=WORKLOAD_VULNERABILITY_SCANNING] [--clear-labels | --remove-labels=[KEY,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -38,6 +40,26 @@ FLAGS contain only hyphens (-), underscores (_), lowercase characters, and numbers. + Default cluster configurations to apply across the fleet. + + Security posture config. + + --security-posture=SECURITY_POSTURE + To apply standard security posture to clusters in the fleet, + + $ gcloud container hub update --security-posture=standard + + SECURITY_POSTURE must be one of: disabled, standard. + + --workload-vulnerability-scanning=WORKLOAD_VULNERABILITY_SCANNING + To apply standard vulnerability scanning to clusters in the fleet, + + $ gcloud container hub update \ + --workload-vulnerability-scanning=standard + + WORKLOAD_VULNERABILITY_SCANNING must be one of: disabled, standard, + enterprise. + At most one of these can be specified: --clear-labels diff --git a/gcloud/dataproc/clusters/create b/gcloud/dataproc/clusters/create index 6884cd185..3940d34ae 100644 --- a/gcloud/dataproc/clusters/create +++ b/gcloud/dataproc/clusters/create @@ -57,6 +57,8 @@ SYNOPSIS [--image=IMAGE | --image-version=VERSION] [--kerberos-config-file=KERBEROS_CONFIG_FILE | --enable-kerberos --kerberos-root-principal-password-uri=KERBEROS_ROOT_PRINCIPAL_PASSWORD_URI [--kerberos-kms-key=KERBEROS_KMS_KEY : --kerberos-kms-key-keyring=KERBEROS_KMS_KEY_KEYRING --kerberos-kms-key-location=KERBEROS_KMS_KEY_LOCATION --kerberos-kms-key-project=KERBEROS_KMS_KEY_PROJECT]] + [--kms-key=KMS_KEY : --kms-keyring=KMS_KEYRING + --kms-location=KMS_LOCATION --kms-project=KMS_PROJECT] [--metadata=KEY=VALUE,[KEY=VALUE,...] --scopes=SCOPE,[SCOPE,...] --service-account=SERVICE_ACCOUNT --tags=TAG,[TAG,...] --network=NETWORK | --subnet=SUBNET @@ -685,6 +687,46 @@ FLAGS line; ▫ set the property core/project. + Key resource - The Cloud KMS (Key Management Service) cryptokey that will + be used to protect the cluster. The 'Compute Engine Service Agent' service + account must hold permission 'Cloud KMS CryptoKey Encrypter/Decrypter'. + The arguments in this group can be used to specify the attributes of this + resource. + + --kms-key=KMS_KEY + ID of the key or fully qualified identifier for the key. + + To set the kms-key attribute: + ▸ provide the argument --kms-key on the command line. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --kms-keyring=KMS_KEYRING + The KMS keyring of the key. + + To set the kms-keyring attribute: + ▸ provide the argument --kms-key on the command line with a fully + specified name; + ▸ provide the argument --kms-keyring on the command line. + + --kms-location=KMS_LOCATION + The Google Cloud location for the key. + + To set the kms-location attribute: + ▸ provide the argument --kms-key on the command line with a fully + specified name; + ▸ provide the argument --kms-location on the command line. + + --kms-project=KMS_PROJECT + The Google Cloud project for the key. + + To set the kms-project attribute: + ▸ provide the argument --kms-key on the command line with a fully + specified name; + ▸ provide the argument --kms-project on the command line; + ▸ set the property core/project. + Compute Engine options for Dataproc clusters. --metadata=KEY=VALUE,[KEY=VALUE,...] diff --git a/gcloud/dataproc/workflow-templates/set-managed-cluster b/gcloud/dataproc/workflow-templates/set-managed-cluster index 0a1305009..a56360ee6 100644 --- a/gcloud/dataproc/workflow-templates/set-managed-cluster +++ b/gcloud/dataproc/workflow-templates/set-managed-cluster @@ -44,6 +44,8 @@ SYNOPSIS [--image=IMAGE | --image-version=VERSION] [--kerberos-config-file=KERBEROS_CONFIG_FILE | --enable-kerberos --kerberos-root-principal-password-uri=KERBEROS_ROOT_PRINCIPAL_PASSWORD_URI [--kerberos-kms-key=KERBEROS_KMS_KEY : --kerberos-kms-key-keyring=KERBEROS_KMS_KEY_KEYRING --kerberos-kms-key-location=KERBEROS_KMS_KEY_LOCATION --kerberos-kms-key-project=KERBEROS_KMS_KEY_PROJECT]] + [--kms-key=KMS_KEY : --kms-keyring=KMS_KEYRING + --kms-location=KMS_LOCATION --kms-project=KMS_PROJECT] [--metadata=KEY=VALUE,[KEY=VALUE,...] --scopes=SCOPE,[SCOPE,...] --service-account=SERVICE_ACCOUNT --tags=TAG,[TAG,...] --network=NETWORK | --subnet=SUBNET @@ -551,6 +553,46 @@ FLAGS line; ▫ set the property core/project. + Key resource - The Cloud KMS (Key Management Service) cryptokey that will + be used to protect the cluster. The 'Compute Engine Service Agent' service + account must hold permission 'Cloud KMS CryptoKey Encrypter/Decrypter'. + The arguments in this group can be used to specify the attributes of this + resource. + + --kms-key=KMS_KEY + ID of the key or fully qualified identifier for the key. + + To set the kms-key attribute: + ▸ provide the argument --kms-key on the command line. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --kms-keyring=KMS_KEYRING + The KMS keyring of the key. + + To set the kms-keyring attribute: + ▸ provide the argument --kms-key on the command line with a fully + specified name; + ▸ provide the argument --kms-keyring on the command line. + + --kms-location=KMS_LOCATION + The Google Cloud location for the key. + + To set the kms-location attribute: + ▸ provide the argument --kms-key on the command line with a fully + specified name; + ▸ provide the argument --kms-location on the command line. + + --kms-project=KMS_PROJECT + The Google Cloud project for the key. + + To set the kms-project attribute: + ▸ provide the argument --kms-key on the command line with a fully + specified name; + ▸ provide the argument --kms-project on the command line; + ▸ set the property core/project. + Compute Engine options for Dataproc clusters. --metadata=KEY=VALUE,[KEY=VALUE,...] diff --git a/gcloud/filestore/instances/create b/gcloud/filestore/instances/create index 67fcb9702..b623f4a2d 100644 --- a/gcloud/filestore/instances/create +++ b/gcloud/filestore/instances/create @@ -106,6 +106,7 @@ REQUIRED FLAGS ▫ 1TB-9.75TB in 256GB increments or its multiples. ▫ 10TB-100TB in 2.5TB increments or its multiples. ▸ ENTERPRISE: 1TB-10TB in 256GB increments or its multiples. + ▸ REGIONAL: 1TB-9.75TB in 256GB increments or its multiples. name The desired logical name of the volume. @@ -172,8 +173,8 @@ REQUIRED FLAGS allocated IP address range is specified, it must be one of the ranges associated with the private service access connection. When specified as a direct CIDR value, it must be a /29 CIDR block for - Basic tier or a /24 CIDR block for High Scale, Zonal or Enterprise - tier in one of the internal IP address ranges + Basic tier or a /24 CIDR block for High Scale, Zonal, Enterprise or + Regional tier in one of the internal IP address ranges (https://www.arin.net/knowledge/address_filters.html) that identifies the range of IP addresses reserved for this instance. For example, 10.0.0.0/29 or 192.168.0.0/24. The range you specify @@ -217,7 +218,7 @@ OPTIONAL FLAGS basic-ssd Performant NFS storage system using SSD. enterprise - ENTERPRISE instances offer the features and availability needed for + Enterprise instances offer the features and availability needed for mission-critical workloads. high-scale-ssd High Scale SSD instance, an alias for ZONAL. Use ZONAL instead @@ -225,6 +226,9 @@ OPTIONAL FLAGS premium Premium Filestore instance, An alias for BASIC_SSD. Use BASIC_SSD instead whenever possible. + regional + Regional instances offer the features and availability needed for + mission-critical workloads. standard Standard Filestore instance, An alias for BASIC_HDD. Use BASIC_HDD instead whenever possible. diff --git a/gcloud/filestore/instances/update b/gcloud/filestore/instances/update index dc701a174..61aa211af 100644 --- a/gcloud/filestore/instances/update +++ b/gcloud/filestore/instances/update @@ -151,6 +151,7 @@ FLAGS ▫ 1TB-9.75TB in 256GB increments or its multiples. ▫ 10TB-100TB in 2.5TB increments or its multiples. ▸ ENTERPRISE: 1TB-10TB in 256GB increments or its multiples. + ▸ REGIONAL: 1TB-9.75TB in 256GB increments or its multiples. name The desired logical name of the volume. diff --git a/gcloud/firestore/export b/gcloud/firestore/export index c3a077942..c21471f8e 100644 --- a/gcloud/firestore/export +++ b/gcloud/firestore/export @@ -79,14 +79,11 @@ FLAGS --snapshot-time=SNAPSHOT_TIME The version of the database to export. - The timestamp must be rounded to the minute, in the past, and not older - than 5 days. Please choose a reasonable timestamp based on prior - knowledge on how long exports take as data at provided snapshot - timestamp can expire during export. - - If specified, then the exported documents will represent a consistent - view of the database at the provided time. Otherwise, there are no - guarantees about the consistency of the exported documents. + The timestamp must be in the past, rounded to the minute and not older + than earliestVersionTime. If specified, then the exported documents + will represent a consistent view of the database at the provided time. + Otherwise, there are no guarantees about the consistency of the + exported documents. For example, to operate on snapshot time 2023-05-26T10:20:00.00Z: diff --git a/gcloud/functions/deploy b/gcloud/functions/deploy index 03554d738..743c821dc 100644 --- a/gcloud/functions/deploy +++ b/gcloud/functions/deploy @@ -3,10 +3,10 @@ NAME SYNOPSIS gcloud functions deploy (NAME : --region=REGION) - [--[no-]allow-unauthenticated] [--docker-registry=DOCKER_REGISTRY] - [--egress-settings=EGRESS_SETTINGS] [--entry-point=ENTRY_POINT] - [--gen2] [--ignore-file=IGNORE_FILE] - [--ingress-settings=INGRESS_SETTINGS] [--memory=MEMORY] [--retry] + [--[no-]allow-unauthenticated] [--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] [--security-level=SECURITY_LEVEL; default="secure-always"] [--serve-all-traffic-latest-revision] @@ -38,6 +38,7 @@ SYNOPSIS /secret_path=SECRET_VALUE_REF, /mount_path:/secret_file_path=SECRET_VALUE_REF,...]] [--clear-vpc-connector | --vpc-connector=VPC_CONNECTOR] + [--memory=MEMORY : --cpu=CPU] [--trigger-bucket=TRIGGER_BUCKET | --trigger-http | --trigger-topic=TRIGGER_TOPIC | --trigger-event=EVENT_TYPE --trigger-resource=RESOURCE @@ -100,6 +101,11 @@ FLAGS without checking authentication. Use --allow-unauthenticated to enable and --no-allow-unauthenticated to disable. + --concurrency=CONCURRENCY + Set the maximum number of concurrent requests allowed per container + instance. Leave concurrency unspecified to receive the server default + value. Only applicable when the --gen2 flag is provided. + --docker-registry=DOCKER_REGISTRY Docker Registry to use for storing the function's Docker images. The option container-registry is used by default. @@ -136,22 +142,6 @@ FLAGS default all will be used. INGRESS_SETTINGS must be one of: all, internal-only, internal-and-gclb. - --memory=MEMORY - Limit on the amount of memory the function can use. - - Allowed values for v1 are: 128MB, 256MB, 512MB, 1024MB, 2048MB, 4096MB, - and 8192MB. - - Allowed values for GCF 2nd gen are in the format: with - allowed units of "k", "M", "G", "Ki", "Mi", "Gi". Ending 'b' or 'B' is - allowed. - - Examples: 100000k, 128M, 10Mb, 1024Mi, 750K, 4Gi. - - By default, a new function is limited to 256MB of memory. When - deploying an update to an existing function, the function keeps its old - memory limit unless you specify this flag. - --retry If specified, then the function will be retried in case of a failure. @@ -553,6 +543,38 @@ FLAGS To set the connector attribute: ▫ provide the argument --vpc-connector on the command line. + --memory=MEMORY + Limit on the amount of memory the function can use. + + Allowed values for v1 are: 128MB, 256MB, 512MB, 1024MB, 2048MB, 4096MB, + and 8192MB. + + Allowed values for GCF 2nd gen are in the format: with + allowed units of "k", "M", "G", "Ki", "Mi", "Gi". Ending 'b' or 'B' is + allowed. + + Examples: 100000k, 128M, 10Mb, 1024Mi, 750K, 4Gi. + + By default, a new function is limited to 256MB of memory. When + deploying an update to an existing function, the function keeps its old + memory limit unless you specify this flag. + + --cpu=CPU + The number of available CPUs to set. Only valid when --gen2 and + --memory=MEMORY are specified. + + Examples: .5, 2, 2.0, 2000m. + + By default, a new function's available CPUs is determined based on its + memory value. + + When deploying an update that includes memory changes to an existing + function, the function's available CPUs will be recalculated based on + the new memory unless this flag is specified. When deploying an update + that does not include memory changes to an existing function, the + function's "available CPUs" setting will keep its old value unless you + use this flag to change the setting. + If you don't specify a trigger when deploying an update to an existing function it will keep its current trigger. You must specify one of the following when deploying a new function: diff --git a/gcloud/metastore/services/create b/gcloud/metastore/services/create index 5202b1ace..d649c1dfc 100644 --- a/gcloud/metastore/services/create +++ b/gcloud/metastore/services/create @@ -3,7 +3,7 @@ NAME SYNOPSIS gcloud metastore services create (SERVICE : --location=LOCATION) [--async] - [--database-type=DATABASE_TYPE; default="mysql"] + [--data-catalog-sync] [--database-type=DATABASE_TYPE; default="mysql"] [--encryption-kms-key=ENCRYPTION_KMS_KEY] [--endpoint-protocol=ENDPOINT_PROTOCOL; default="thrift"] [--hive-metastore-version=HIVE_METASTORE_VERSION] @@ -84,6 +84,11 @@ FLAGS Return immediately, without waiting for the operation in progress to complete. + --data-catalog-sync + A boolean flag to determine whether Dataproc Metastore metadata sync to + Data Catalog should be enabled, false if unspecified. Mutually + exclusive with flag --encryption-kms-key. + --database-type=DATABASE_TYPE; default="mysql" The type of database the Dataproc Metastore service will store data in. DATABASE_TYPE must be one of: diff --git a/gcloud/metastore/services/update b/gcloud/metastore/services/update index 8745c6bc5..6e30cc6f1 100644 --- a/gcloud/metastore/services/update +++ b/gcloud/metastore/services/update @@ -3,8 +3,8 @@ NAME SYNOPSIS gcloud metastore services update (SERVICE : --location=LOCATION) [--async] - [--endpoint-protocol=ENDPOINT_PROTOCOL] [--port=PORT] - [--update-labels=[KEY=VALUE,...]] + [--data-catalog-sync] [--endpoint-protocol=ENDPOINT_PROTOCOL] + [--port=PORT] [--update-labels=[KEY=VALUE,...]] [--clear-labels | --remove-labels=[KEY,...]] [--instance-size=INSTANCE_SIZE | --scaling-factor=SCALING_FACTOR | --tier=TIER] @@ -74,6 +74,12 @@ FLAGS Return immediately, without waiting for the operation in progress to complete. + --data-catalog-sync + Boolean flag to determine whether or not Dataproc Metastore metadata + sync to Data Catalog is enabled, false if unspecified. Mutually + exclusive with flag --encryption-kms-key. Cannot be updated if the + service uses customer-managed encryption keys. + --endpoint-protocol=ENDPOINT_PROTOCOL The protocol to use for the metastore service endpoint. ENDPOINT_PROTOCOL must be one of: diff --git a/gcloud/network-connectivity/spokes/accept b/gcloud/network-connectivity/spokes/accept deleted file mode 100644 index 27e0fc2da..000000000 --- a/gcloud/network-connectivity/spokes/accept +++ /dev/null @@ -1,66 +0,0 @@ -NAME - gcloud network-connectivity spokes accept - accept a spoke - -SYNOPSIS - gcloud network-connectivity spokes accept SPOKE [--async] [--global] - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (DEPRECATED) Accept a spoke. - - This command is deprecated. Please use gcloud network-connectivity hubs - accept-spoke instead. - - Accept a proposed or previously rejected VPC spoke. By accepting a spoke, - you permit connectivity between the associated VPC network and other VPC - networks that are attached to the same hub. - -EXAMPLES - To accept a spoke named myspoke, run: - - $ gcloud network-connectivity spokes accept myspoke --global - -POSITIONAL ARGUMENTS - Spoke resource - Name of the spoke to accept. 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 spoke 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 spoke on the command line with a fully specified - name; - ◆ provide the argument --global on the command line. - - This must be specified. - - SPOKE - ID of the spoke or fully qualified identifier for the spoke. - - To set the spoke attribute: - ▸ provide the argument spoke on the command line. - -FLAGS - --async - Return immediately, without waiting for the operation in progress to - complete. - - --global - Indicates that the spoke is global. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -API REFERENCE - This command uses the networkconnectivity/v1 API. The full documentation - for this API can be found at: - https://cloud.google.com/network-connectivity/docs/reference/networkconnectivity/rest diff --git a/gcloud/network-connectivity/spokes/help b/gcloud/network-connectivity/spokes/help index b57fc60da..bb357d652 100644 --- a/gcloud/network-connectivity/spokes/help +++ b/gcloud/network-connectivity/spokes/help @@ -31,9 +31,6 @@ GROUPS COMMANDS COMMAND is one of the following: - accept - (DEPRECATED) Accept a spoke. - delete Delete a spoke. @@ -43,9 +40,6 @@ COMMANDS list List spokes. - reject - (DEPRECATED) Reject a spoke. - NOTES This variant is also available: diff --git a/gcloud/network-connectivity/spokes/reject b/gcloud/network-connectivity/spokes/reject deleted file mode 100644 index 2ac611cc7..000000000 --- a/gcloud/network-connectivity/spokes/reject +++ /dev/null @@ -1,70 +0,0 @@ -NAME - gcloud network-connectivity spokes reject - reject a spoke - -SYNOPSIS - gcloud network-connectivity spokes reject SPOKE [--async] - [--details=DETAILS] [--global] [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (DEPRECATED) Reject a spoke. - - This command is deprecated. Please use gcloud network-connectivity hubs - reject-spoke instead. - - Reject a VPC spoke. By rejecting a spoke, you prevent or remove - connectivity between the associated VPC network and any other VPC networks - that are attached to the same hub. - -EXAMPLES - To reject a spoke named myspoke with reason myreason, run: - - $ gcloud network-connectivity spokes reject myspoke \ - --details="myreason" --global - -POSITIONAL ARGUMENTS - Spoke resource - Name of the spoke to reject. 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 spoke 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 spoke on the command line with a fully specified - name; - ◆ provide the argument --global on the command line. - - This must be specified. - - SPOKE - ID of the spoke or fully qualified identifier for the spoke. - - To set the spoke attribute: - ▸ provide the argument spoke on the command line. - -FLAGS - --async - Return immediately, without waiting for the operation in progress to - complete. - - --details=DETAILS - Additional details behind the rejection - - --global - Indicates that the spoke is global. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -API REFERENCE - This command uses the networkconnectivity/v1 API. The full documentation - for this API can be found at: - https://cloud.google.com/network-connectivity/docs/reference/networkconnectivity/rest diff --git a/gcloud/run/jobs/executions/cancel b/gcloud/run/jobs/executions/cancel new file mode 100644 index 000000000..1eb843275 --- /dev/null +++ b/gcloud/run/jobs/executions/cancel @@ -0,0 +1,59 @@ +NAME + gcloud run jobs executions cancel - cancel an execution + +SYNOPSIS + gcloud run jobs executions cancel EXECUTION [--[no-]async] + [--region=REGION] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Cancel an execution. + +EXAMPLES + To cancel an execution: + + $ gcloud run jobs executions cancel my-execution + +POSITIONAL ARGUMENTS + Execution resource - Execution to cancel. This represents a Cloud + resource. (NOTE) Some attributes are not given arguments in this group but + can be set in other ways. + + To set the project attribute: + ◆ provide the argument EXECUTION on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + EXECUTION + ID of the Execution or fully qualified identifier for the Execution. + + To set the executions attribute: + ▸ provide the argument EXECUTION on the command line. + +FLAGS + --[no-]async + Return immediately, without waiting for the operation in progress to + complete. Defaults to --no-async. Use --async to enable and --no-async + to disable. + + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha run jobs executions cancel + + $ gcloud beta run jobs executions cancel + diff --git a/gcloud/run/jobs/executions/help b/gcloud/run/jobs/executions/help index 69e7542d0..824b14213 100644 --- a/gcloud/run/jobs/executions/help +++ b/gcloud/run/jobs/executions/help @@ -33,6 +33,9 @@ GROUPS COMMANDS COMMAND is one of the following: + cancel + Cancel an execution. + delete Delete an execution. diff --git a/gcloud/scc/custom-modules/sha/help b/gcloud/scc/custom-modules/sha/help index 7981a7d84..06d7b90b7 100644 --- a/gcloud/scc/custom-modules/sha/help +++ b/gcloud/scc/custom-modules/sha/help @@ -40,6 +40,9 @@ COMMANDS List the details of Security Health Analytics custom modules with effective enablement states. + simulate + Validates a Security Health Analytics custom module. + update Update a Security Health Analytics custom module. diff --git a/gcloud/scc/custom-modules/sha/simulate b/gcloud/scc/custom-modules/sha/simulate new file mode 100644 index 000000000..e31ec4065 --- /dev/null +++ b/gcloud/scc/custom-modules/sha/simulate @@ -0,0 +1,77 @@ +NAME + gcloud scc custom-modules sha simulate - validates a Security Health + Analytics custom module + +SYNOPSIS + gcloud scc custom-modules sha simulate + --custom-config-from-file=CUSTOM_CONFIG_FROM_FILE + --resource-from-file=RESOURCE_FROM_FILE + (--folder=FOLDER | --organization=ORGANIZATION | --project=PROJECT) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Validates a given Security Health Analytics custom module and resource. + +EXAMPLES + To validate a Security Health Analytics custom module against a custom + resource for organization 123, run: + + $ gcloud scc custom-modules sha simulate \ + --organization=organizations/123 \ + --custom-config-from-file=/tmp/custom_config.yaml \ + --resource-from-file=/tmp/resource.yaml + + To validate a Security Health Analytics custom module against a custom + resource for folder 456, run: + + $ gcloud scc custom-modules sha simulate --folder=folders/456 \ + --custom-config-from-file=/tmp/custom_config.yaml \ + --resource-from-file=/tmp/resource.yaml + + To validate a Security Health Analytics custom module against a custom + resource for project 789, run: + + $ gcloud scc custom-modules sha simulate --project=projects/789 \ + --custom-config-from-file=/tmp/custom_config.yaml \ + --resource-from-file=/tmp/resource.yaml + +REQUIRED FLAGS + --custom-config-from-file=CUSTOM_CONFIG_FROM_FILE + Path to a YAML file that contains the configuration for the Security + Health Analytics custom module. + + --resource-from-file=RESOURCE_FROM_FILE + Path to a YAML file that contains the resource data to validate the + Security Health Analytics custom module against. + + Exactly one of these must be specified: + + --folder=FOLDER + Folder that will own the Security Health Analytics custom module. + Formatted as folders/456 or just 456. + + --organization=ORGANIZATION + Organization that will own the Security Health Analytics custom + module. Formatted as organizations/123 or just 123. + + --project=PROJECT + ID or number of the project that will own the Security Health + Analytics custom module. Formatted as projects/789 or just 789. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the securitycenter/v1 API. The full documentation for + this API can be found at: https://cloud.google.com/security-command-center + +NOTES + This variant is also available: + + $ gcloud alpha scc custom-modules sha simulate + diff --git a/gcloud/sql/instances/create b/gcloud/sql/instances/create index 40091105e..d41b1e0d8 100644 --- a/gcloud/sql/instances/create +++ b/gcloud/sql/instances/create @@ -293,6 +293,10 @@ FLAGS production Production updates are stable and recommended for applications in production. + week5 + week5 updates release after the production updates. Use the week5 + channel to receive a 5 week advance notification about the upcoming + maintenance, so you can prepare your application for the release. --maintenance-window-day=MAINTENANCE_WINDOW_DAY Day of week for maintenance window, in UTC time zone. diff --git a/gcloud/sql/instances/list b/gcloud/sql/instances/list index 06f444fe0..81fe6c0b6 100644 --- a/gcloud/sql/instances/list +++ b/gcloud/sql/instances/list @@ -2,8 +2,9 @@ NAME gcloud sql instances list - lists Cloud SQL instances in a given project SYNOPSIS - gcloud sql instances list [--show-edition] [--filter=EXPRESSION] - [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + gcloud sql instances list [--show-edition] + [--show-sql-network-architecture] [--filter=EXPRESSION] [--limit=LIMIT] + [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -14,6 +15,12 @@ FLAGS --show-edition Show the edition field. + --show-sql-network-architecture + Show the instance's current SqlNetworkArchitecture backend in addition + to the default output list. An instance could use either the old or new + network architecture. The new network architecture offers better + isolation, reliability, and faster new feature adoption. + LIST COMMAND FLAGS --filter=EXPRESSION Apply a Boolean filter EXPRESSION to each resource item to be listed. diff --git a/gcloud/sql/instances/patch b/gcloud/sql/instances/patch index 8fd383dd9..20c655a11 100644 --- a/gcloud/sql/instances/patch +++ b/gcloud/sql/instances/patch @@ -39,6 +39,7 @@ SYNOPSIS [--[no-]require-ssl] [--ssl-mode=SSL_MODE] [--[no-]storage-auto-increase] [--storage-size=STORAGE_SIZE] [--threads-per-core=THREADS_PER_CORE] [--tier=TIER, -t TIER] + [--upgrade-sql-network-architecture] [--allowed-psc-projects=PROJECT,[PROJECT,...] | --clear-allowed-psc-projects] [--authorized-gae-apps=APP,[APP,...] | --clear-gae-apps] @@ -244,6 +245,10 @@ FLAGS production Production updates are stable and recommended for applications in production. + week5 + week5 updates release after the production updates. Use the week5 + channel to receive a 5 week advance notification about the upcoming + maintenance, so you can prepare your application for the release. --maintenance-version=MAINTENANCE_VERSION The desired maintenance version of the instance. @@ -371,6 +376,11 @@ FLAGS https://cloud.google.com/sql/pricing. WARNING: Instance will be restarted. + --upgrade-sql-network-architecture + Upgrade from old network architecture to new network architecture. The + new network architecture offers better isolation, reliability, and + faster new feature adoption. + At most one of these can be specified: --allowed-psc-projects=PROJECT,[PROJECT,...] diff --git a/gcloud/storage/buckets/create b/gcloud/storage/buckets/create index 83cf7dbeb..bc98f7603 100644 --- a/gcloud/storage/buckets/create +++ b/gcloud/storage/buckets/create @@ -8,7 +8,7 @@ SYNOPSIS -k DEFAULT_ENCRYPTION_KEY] [--default-storage-class=DEFAULT_STORAGE_CLASS, -c DEFAULT_STORAGE_CLASS, -s DEFAULT_STORAGE_CLASS] - [--location=LOCATION, -l LOCATION] + [--enable-per-object-retention] [--location=LOCATION, -l LOCATION] [--[no-]pap, --[no-]public-access-prevention] [--placement=REGION,REGION] [--recovery-point-objective=SETTING, --rpo=SETTING] @@ -56,6 +56,10 @@ FLAGS If not specified, the default storage class used by Cloud Storage is "Standard". + --enable-per-object-retention + Enables each object in the bucket to have its own retention settings, + which prevents deletion until stored for a specific length of time. + --location=LOCATION, -l LOCATION Location (https://cloud.google.com/storage/docs/locations) for the bucket. If not specified, the location used by Cloud Storage is us. A diff --git a/gcloud/storage/cp b/gcloud/storage/cp index a0043f8c3..947257cf2 100644 --- a/gcloud/storage/cp +++ b/gcloud/storage/cp @@ -28,7 +28,9 @@ SYNOPSIS | --remove-custom-metadata=[METADATA_KEYS,...] --update-custom-metadata=[CUSTOM_METADATA_KEYS_AND_VALUES,...]] [--if-generation-match=GENERATION - --if-metageneration-match=METAGENERATION] [GCLOUD_WIDE_FLAG ...] + --if-metageneration-match=METAGENERATION] + [--retain-until=DATETIME --retention-mode=RETENTION_MODE] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION Copy data between your local file system and the cloud, within the cloud, @@ -339,6 +341,16 @@ PRECONDITION FLAGS Execute only if the metageneration matches the metageneration of the requested object. +RETENTION FLAGS + --retain-until=DATETIME + Ensures the destination object is retained until the specified time in + RFC 3339 format. + + --retention-mode=RETENTION_MODE + Sets the destination object retention mode to either "Locked" or + "Unlocked". When retention mode is "Locked", the retain until time can + only be increased. RETENTION_MODE must be one of: Locked, Unlocked. + 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/storage/mv b/gcloud/storage/mv index 276546e5f..bb3687142 100644 --- a/gcloud/storage/mv +++ b/gcloud/storage/mv @@ -27,7 +27,9 @@ SYNOPSIS | --remove-custom-metadata=[METADATA_KEYS,...] --update-custom-metadata=[CUSTOM_METADATA_KEYS_AND_VALUES,...]] [--if-generation-match=GENERATION - --if-metageneration-match=METAGENERATION] [GCLOUD_WIDE_FLAG ...] + --if-metageneration-match=METAGENERATION] + [--retain-until=DATETIME --retention-mode=RETENTION_MODE] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION The mv command allows you to move data between your local file system and @@ -344,6 +346,16 @@ PRECONDITION FLAGS Execute only if the metageneration matches the metageneration of the requested object. +RETENTION FLAGS + --retain-until=DATETIME + Ensures the destination object is retained until the specified time in + RFC 3339 format. + + --retention-mode=RETENTION_MODE + Sets the destination object retention mode to either "Locked" or + "Unlocked". When retention mode is "Locked", the retain until time can + only be increased. RETENTION_MODE must be one of: Locked, Unlocked. + 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/storage/objects/compose b/gcloud/storage/objects/compose index 139569880..e331469cd 100644 --- a/gcloud/storage/objects/compose +++ b/gcloud/storage/objects/compose @@ -6,7 +6,9 @@ SYNOPSIS gcloud storage objects compose SOURCE [SOURCE ...] DESTINATION [--additional-headers=HEADER=VALUE] [--if-generation-match=GENERATION - --if-metageneration-match=METAGENERATION] [GCLOUD_WIDE_FLAG ...] + --if-metageneration-match=METAGENERATION] + [--retain-until=DATETIME --retention-mode=RETENTION_MODE] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION gcloud storage objects compose creates a new object whose content is the @@ -48,6 +50,16 @@ PRECONDITION FLAGS Execute only if the metageneration matches the metageneration of the requested object. +RETENTION FLAGS + --retain-until=DATETIME + Ensures the destination object is retained until the specified time in + RFC 3339 format. + + --retention-mode=RETENTION_MODE + Sets the destination object retention mode to either "Locked" or + "Unlocked". When retention mode is "Locked", the retain until time can + only be increased. RETENTION_MODE must be one of: Locked, Unlocked. + 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/storage/objects/update b/gcloud/storage/objects/update index 2a3f27853..a4a5fe3fb 100644 --- a/gcloud/storage/objects/update +++ b/gcloud/storage/objects/update @@ -24,7 +24,10 @@ SYNOPSIS | --remove-custom-metadata=[METADATA_KEYS,...] --update-custom-metadata=[CUSTOM_METADATA_KEYS_AND_VALUES,...]] [--if-generation-match=GENERATION - --if-metageneration-match=METAGENERATION] [GCLOUD_WIDE_FLAG ...] + --if-metageneration-match=METAGENERATION] + [--clear-retention --override-unlocked-retention + --retain-until=DATETIME --retention-mode=RETENTION_MODE] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION Update Cloud Storage objects. @@ -217,6 +220,26 @@ PRECONDITION FLAGS Execute only if the metageneration matches the metageneration of the requested object. +RETENTION FLAGS + --clear-retention + Clears object retention settings and unlocks the configuration. + Requires --override-unlocked-retention flag as confirmation. + + --override-unlocked-retention + Needed for certain retention configuration modifications, such as + clearing retention settings and reducing retention time. Note that + locked configurations cannot be edited even with this flag. + + --retain-until=DATETIME + Ensures the object is retained until the specified time in RFC 3339 + format. Requires --override-unlocked-retention flag to shorten the + retain-until time in unlocked configurations. + + --retention-mode=RETENTION_MODE + Sets the object retention mode to either "Locked" or "Unlocked". When + retention mode is "Locked", the retain until time can only be + increased. RETENTION_MODE must be one of: Locked, Unlocked. + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/transfer/jobs/create b/gcloud/transfer/jobs/create index 2384385c8..b6e70fcdf 100644 --- a/gcloud/transfer/jobs/create +++ b/gcloud/transfer/jobs/create @@ -133,7 +133,7 @@ FLAGS Note: Be sure to put quotations around the JSON value strings. Azure: - http://cloud/storage-transfer/docs/reference/rest/v1/TransferSpec#AzureCredentials + https://cloud.google.com/storage-transfer/docs/reference/rest/v1/TransferSpec#AzureCredentials --source-agent-pool=SOURCE_AGENT_POOL If using a POSIX filesystem source, specify the ID of the agent pool diff --git a/gcloud/transfer/jobs/update b/gcloud/transfer/jobs/update index e9f0805d3..3979f1d36 100644 --- a/gcloud/transfer/jobs/update +++ b/gcloud/transfer/jobs/update @@ -157,7 +157,7 @@ FLAGS Note: Be sure to put quotations around the JSON value strings. Azure: - http://cloud/storage-transfer/docs/reference/rest/v1/TransferSpec#AzureCredentials + https://cloud.google.com/storage-transfer/docs/reference/rest/v1/TransferSpec#AzureCredentials --source-agent-pool=SOURCE_AGENT_POOL If using a POSIX filesystem source, specify the ID of the agent pool diff --git a/gcloud/vmware/dns-bind-permission/describe b/gcloud/vmware/dns-bind-permission/describe new file mode 100644 index 000000000..cdbe0dd9e --- /dev/null +++ b/gcloud/vmware/dns-bind-permission/describe @@ -0,0 +1,31 @@ +NAME + gcloud vmware dns-bind-permission describe - get all users and service + accounts having bind permission + +SYNOPSIS + gcloud vmware dns-bind-permission describe [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Gets all the users and service accounts having bind permission on the + intranet VPC associated with the consumer project granted by the Grant API. + +EXAMPLES + To get all the users and service accounts having bind permission on the + intranet VPC associated with the consumer project my-project, run: + + $ gcloud vmware dns-bind-permission describe --project=my-project + + Or: + + $ gcloud vmware dns-bind-permission describe + + In the second example, the project is taken from gcloud properties + core/project. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. diff --git a/gcloud/vmware/dns-bind-permission/grant b/gcloud/vmware/dns-bind-permission/grant new file mode 100644 index 000000000..e97a87796 --- /dev/null +++ b/gcloud/vmware/dns-bind-permission/grant @@ -0,0 +1,71 @@ +NAME + gcloud vmware dns-bind-permission grant - grants a DNS Bind Permission + +SYNOPSIS + gcloud vmware dns-bind-permission grant + (--service-account=SERVICE_ACCOUNT | --user=USER) [--async] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Grants the bind permission to the customer provided user/service account to + bind their DNS zone with the intranet VPC associated with the project. + +EXAMPLES + To grant the bind permission to the customer provided user user@abc.com to + bind their DNS zone with the intranet VPC associated with project + my-project, run: + + $ gcloud vmware dns-bind-permission grant --user=user@abc.com \ + --project=my-project + + Or: + + $ gcloud vmware dns-bind-permission grant --user=user@abc.com + + In the second example, the project is taken from gcloud properties + core/project. + + To grant the bind permission to the customer provided service account + service-account@gserviceaccount.com to bind their DNS zone with the + intranet VPC associated with project my-project, run: + + $ gcloud vmware dns-bind-permission grant \ + --service-account=service-account@gserviceaccount.com \ + --project=my-project + + Or: + + $ gcloud vmware dns-bind-permission grant \ + --service-account=service-account@gserviceaccount.com + + In the second example, the project is taken from gcloud properties + core/project. + +REQUIRED FLAGS + Exactly one of these must be specified: + + --service-account=SERVICE_ACCOUNT + The consumer provided service account which needs to be granted + permission to bind with the intranet VPC corresponding to the + consumer project. If this field is not provided then the user should + be provided. + + --user=USER + The consumer provided user which needs to be granted permission to + bind with the intranet VPC corresponding to the consumer project. If + this field is not provided then the service-account should be + provided. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. The default is True. Enabled by default, use --no-async to + disable. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. diff --git a/gcloud/vmware/dns-bind-permission/help b/gcloud/vmware/dns-bind-permission/help new file mode 100644 index 000000000..4de373b1c --- /dev/null +++ b/gcloud/vmware/dns-bind-permission/help @@ -0,0 +1,26 @@ +NAME + gcloud vmware dns-bind-permission - manage DNS binding permission in Google + Cloud VMware Engine + +SYNOPSIS + gcloud vmware dns-bind-permission COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Manage DNS binding permission in Google Cloud VMware Engine. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + describe + Get all users and service accounts having bind permission. + + grant + Grants a DNS Bind Permission. + + revoke + Revokes a DNS Bind Permission. diff --git a/gcloud/vmware/dns-bind-permission/revoke b/gcloud/vmware/dns-bind-permission/revoke new file mode 100644 index 000000000..a7c693498 --- /dev/null +++ b/gcloud/vmware/dns-bind-permission/revoke @@ -0,0 +1,68 @@ +NAME + gcloud vmware dns-bind-permission revoke - revokes a DNS Bind Permission + +SYNOPSIS + gcloud vmware dns-bind-permission revoke + (--service-account=SERVICE_ACCOUNT | --user=USER) [--async] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Revokes the bind permission from the customer provided user/service account + on the intranet VPC associated with the consumer project. + +EXAMPLES + To revoke the bind permission to the customer provided user user@abc.com on + the intranet VPC associated with the consumer project my-project, run: + + $ gcloud vmware dns-bind-permission revoke --user=user@abc.com \ + --project=my-project + + Or: + + $ gcloud vmware dns-bind-permission revoke --user=user@abc.com + + In the second example, the project is taken from gcloud properties + core/project. + + To revoke the bind permission to the customer provided service account + service-account@gserviceaccount.com on the intranet VPC associated with the + consumer project my-project, run: + + $ gcloud vmware dns-bind-permission revoke \ + --service-account=service-account@gserviceaccount.com \ + --project=my-project + + Or: + + $ gcloud vmware dns-bind-permission revoke \ + --service-account=service-account@gserviceaccount.com + + In the second example, the project is taken from gcloud properties + core/project. + +REQUIRED FLAGS + Exactly one of these must be specified: + + --service-account=SERVICE_ACCOUNT + The consumer provided service account whose permission needs to be + revoked on the intranet VPC corresponding to the consumer project. If + this field is not provided then the user should be provided. + + --user=USER + The consumer provided user whose permission needs to be revoked on + the intranet VPC corresponding to the consumer project. If this field + is not provided then the service-account should be provided. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. The default is True. Enabled by default, use --no-async to + disable. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. diff --git a/gcloud/vmware/help b/gcloud/vmware/help index a758c8e24..dfff85a5b 100644 --- a/gcloud/vmware/help +++ b/gcloud/vmware/help @@ -15,9 +15,15 @@ GCLOUD WIDE FLAGS GROUPS GROUP is one of the following: + dns-bind-permission + Manage DNS binding permission in Google Cloud VMware Engine. + locations List locations in Google Cloud VMware Engine. + network-peerings + Manage VMware Engine VPC peering using Google Cloud VMware Engine. + network-policies Manage VMware Engine network policies in Google Cloud VMware Engine. diff --git a/gcloud/vmware/network-peerings/create b/gcloud/vmware/network-peerings/create new file mode 100644 index 000000000..1e6e7bfe4 --- /dev/null +++ b/gcloud/vmware/network-peerings/create @@ -0,0 +1,135 @@ +NAME + gcloud vmware network-peerings create - create a VMware Engine VPC network + peering + +SYNOPSIS + gcloud vmware network-peerings create NETWORK_PEERING + --peer-network=PEER_NETWORK --peer-network-type=PEER_NETWORK_TYPE + --vmware-engine-network=VMWARE_ENGINE_NETWORK [--async] + [--description=DESCRIPTION] [--no-exchange-subnet-routes] + [--no-export-custom-routes] [--no-export-custom-routes-with-public-ip] + [--no-import-custom-routes] [--no-import-custom-routes-with-public-ip] + [--peer-mtu=PEER_MTU] [--peer-project=PEER_PROJECT] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Create a VMware Engine VPC network peering. VPC network peering creation is + considered finished when the network peering is in ACTIVE state. Check the + progress of a VPC network peering using gcloud vmware network-peerings + list. + +EXAMPLES + To create a VPC network peering called new-peering that connects the VMware + Engine network my-vmware-engine-network with another VMware Engine network + another-vmware-engine-network from project another-project, run: + + $ gcloud vmware network-peerings create new-peering \ + --vmware-engine-network=my-vmware-engine-network \ + --peer-network=another-vmware-engine-network \ + --peer-network-type=VMWARE_ENGINE_NETWORK \ + --peer-project=another-project + + In this example, the project is taken from gcloud properties core/project + and location is taken as global. + +POSITIONAL ARGUMENTS + VMware Engine VPC network peering resource - network_peering. This + represents a Cloud resource. (NOTE) Some attributes are not given + arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument network_peering on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + NETWORK_PEERING + ID of the VMware Engine VPC network peering or fully qualified + identifier for the VMware Engine VPC network peering. + + To set the network-peering attribute: + ▸ provide the argument network_peering on the command line. + +REQUIRED FLAGS + --peer-network=PEER_NETWORK + ID of the network to peer with the VMware Engine network. The peer + network can be a consumer VPC network or another VMware Engine network. + + --peer-network-type=PEER_NETWORK_TYPE + Type of the VPC network to peer with the VMware Engine network. + PEER_NETWORK_TYPE must be one of the following: + ◆ STANDARD: Peering connection used for connecting to another VPC + network established by the same user. For example, a peering + connection to another VPC network in the same project or to an + on-premises network. + ◆ VMWARE_ENGINE_NETWORK: Peering connection used for connecting to + another VMware Engine network. + ◆ PRIVATE_SERVICES_ACCESS: Peering connection used for establishing + private services access. + ◆ NETAPP_CLOUD_VOLUMES: Peering connection used for connecting to + NetApp Cloud Volumes. + ◆ THIRD_PARTY_SERVICE: Peering connection used for connecting to + third-party services. Most third-party services require manual setup + of reverse peering on the VPC network associated with the third-party + service. + ◆ DELL_POWERSCALE: Peering connection used for connecting to Dell + PowerScale Filers. PEER_NETWORK_TYPE must be one of: + PEER_NETWORK_TYPE_UNSPECIFIED, STANDARD, VMWARE_ENGINE_NETWORK, + PRIVATE_SERVICES_ACCESS, NETAPP_CLOUD_VOLUMES, THIRD_PARTY_SERVICE, + DELL_POWERSCALE. + + --vmware-engine-network=VMWARE_ENGINE_NETWORK + ID of the VMware Engine network to attach the new peering to. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. The default is True. Enabled by default, use --no-async to + disable. + + --description=DESCRIPTION + User-provided description of the VPC network peering. + + --exchange-subnet-routes + True if full-mesh connectivity is created and managed automatically + between peered VPC networks; false otherwise. This field is always true + because Google Compute Engine automatically creates and manages + subnetwork routes between two VPC networks when the peering state is + ACTIVE. Enabled by default, use --no-exchange-subnet-routes to disable. + + --export-custom-routes + True if custom routes are exported to the peered VPC network; false + otherwise. The default value is true. Enabled by default, use + --no-export-custom-routes to disable. + + --export-custom-routes-with-public-ip + True if all subnet routes with public IP address range are exported; + false otherwise. The default value is true. Enabled by default, use + --no-export-custom-routes-with-public-ip to disable. + + --import-custom-routes + True if custom routes are imported to the peered VPC network; false + otherwise. The default value is true. Enabled by default, use + --no-import-custom-routes to disable. + + --import-custom-routes-with-public-ip + True if all subnet routes with public IP address range are imported; + false otherwise. The default value is true. Enabled by default, use + --no-import-custom-routes-with-public-ip to disable. + + --peer-mtu=PEER_MTU + Maximum transmission unit (MTU) in bytes. + + --peer-project=PEER_PROJECT + Project ID or project number of the peer network. Use this flag when + the peer network is in another project. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. diff --git a/gcloud/vmware/network-peerings/delete b/gcloud/vmware/network-peerings/delete new file mode 100644 index 000000000..53838c5b6 --- /dev/null +++ b/gcloud/vmware/network-peerings/delete @@ -0,0 +1,54 @@ +NAME + gcloud vmware network-peerings delete - delete a Google Cloud VMware Engine + VPC network peering + +SYNOPSIS + gcloud vmware network-peerings delete NETWORK_PEERING [--async] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Delete a VPC network peering. After you delete a VPC network peering, you + won't be able to access the corresponding VMware Engine network through the + peer network. + +EXAMPLES + To delete a VPC network peering with name my-peering, run: + + $ gcloud vmware network-peerings delete my-peering + + In this example, the project is taken from gcloud properties core/project + and location is taken as global. + +POSITIONAL ARGUMENTS + VMware Engine VPC network peering resource - network_peering. This + represents a Cloud resource. (NOTE) Some attributes are not given + arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument network_peering on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + NETWORK_PEERING + ID of the VMware Engine VPC network peering or fully qualified + identifier for the VMware Engine VPC network peering. + + To set the network-peering attribute: + ▸ provide the argument network_peering on the command line. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. The default is True. Enabled by default, use --no-async to + disable. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. diff --git a/gcloud/vmware/network-peerings/describe b/gcloud/vmware/network-peerings/describe new file mode 100644 index 000000000..aa8cb7759 --- /dev/null +++ b/gcloud/vmware/network-peerings/describe @@ -0,0 +1,46 @@ +NAME + gcloud vmware network-peerings describe - describe a Google Cloud VMware + Engine VPC network peering + +SYNOPSIS + gcloud vmware network-peerings describe NETWORK_PEERING + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Get information about a VPC network peering. + +EXAMPLES + To get information about a VPC network peering called new-peering, run: + + $ gcloud vmware network-peerings describe new-peering + + In this example, the project is taken from gcloud properties core/project + and location is taken as global. + +POSITIONAL ARGUMENTS + VMware Engine VPC network peering resource - network_peering. This + represents a Cloud resource. (NOTE) Some attributes are not given + arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument network_peering on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + NETWORK_PEERING + ID of the VMware Engine VPC network peering or fully qualified + identifier for the VMware Engine VPC network peering. + + To set the network-peering attribute: + ▸ provide the argument network_peering on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. diff --git a/gcloud/vmware/network-peerings/help b/gcloud/vmware/network-peerings/help new file mode 100644 index 000000000..44c606963 --- /dev/null +++ b/gcloud/vmware/network-peerings/help @@ -0,0 +1,39 @@ +NAME + gcloud vmware network-peerings - manage VMware Engine VPC peering using + Google Cloud VMware Engine + +SYNOPSIS + gcloud vmware network-peerings GROUP | COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Manage VMware Engine VPC peering using Google Cloud VMware Engine. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +GROUPS + GROUP is one of the following: + + routes + Manage VMware Engine VPC peering routes using Google Cloud VMware + Engine. + +COMMANDS + COMMAND is one of the following: + + create + Create a VMware Engine VPC network peering. + + delete + Delete a Google Cloud VMware Engine VPC network peering. + + describe + Describe a Google Cloud VMware Engine VPC network peering. + + list + List Google Cloud VMware Engine VPC network peerings. + + update + Update a Google Cloud VMware Engine VPC network peering. diff --git a/gcloud/vmware/network-peerings/list b/gcloud/vmware/network-peerings/list new file mode 100644 index 000000000..876d3182f --- /dev/null +++ b/gcloud/vmware/network-peerings/list @@ -0,0 +1,81 @@ +NAME + gcloud vmware network-peerings list - list Google Cloud VMware Engine VPC + network peerings + +SYNOPSIS + gcloud vmware network-peerings list [--location=LOCATION] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + List VPC network peerings across all locations in your project. + +EXAMPLES + To list all the VPC network peerings created on or after April 12, 2021, + sorted from oldest to newest, run: + + $ gcloud vmware network-peerings list \ + --filter="createTime > 2021-04-12T00:00:00.00Z" \ + --sort-by=createTime + + In this example, the location is taken as global. + +FLAGS + Location resource - location. This represents a Cloud resource. (NOTE) + Some attributes are not given arguments in this group but can be set in + other ways. + + To set the project attribute: + ◆ provide the argument --location on the command line with a fully + specified name; + ◆ set location as 'global' (default) or a region with a fully specified + name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + --location=LOCATION + ID of the location or fully qualified identifier for the location. + + To set the location attribute: + ▸ provide the argument --location on the command line; + ▸ set location as 'global' (default) or a region. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. diff --git a/gcloud/vmware/network-peerings/routes/help b/gcloud/vmware/network-peerings/routes/help new file mode 100644 index 000000000..b7a700ce2 --- /dev/null +++ b/gcloud/vmware/network-peerings/routes/help @@ -0,0 +1,20 @@ +NAME + gcloud vmware network-peerings routes - manage VMware Engine VPC peering + routes using Google Cloud VMware Engine + +SYNOPSIS + gcloud vmware network-peerings routes COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Manage VMware Engine VPC peering routes using Google Cloud VMware Engine. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + list + List Google Cloud VMware Engine VPC network peering routes. diff --git a/gcloud/vmware/network-peerings/routes/list b/gcloud/vmware/network-peerings/routes/list new file mode 100644 index 000000000..f63538bfa --- /dev/null +++ b/gcloud/vmware/network-peerings/routes/list @@ -0,0 +1,85 @@ +NAME + gcloud vmware network-peerings routes list - list Google Cloud VMware + Engine VPC network peering routes + +SYNOPSIS + gcloud vmware network-peerings routes list + --network-peering=NETWORK_PEERING [--filter=EXPRESSION] [--limit=LIMIT] + [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + List VPC network peering routes across all locations in your project. + +EXAMPLES + To list peering routes imported from peer network via my-peering: + + $ gcloud vmware network-peerings routes list \ + --network-peering=my-peering --filter="direction=INCOMING" + + To list peering routes exported to peer network via my-peering: + + $ gcloud vmware network-peerings routes list \ + --network-peering=my-peering --filter="direction=OUTGOING" + + In above examples, the location is taken as global. + +REQUIRED FLAGS + VMware Engine VPC network peering resource - network_peering. This + represents a Cloud resource. (NOTE) Some attributes are not given + arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument --network-peering on the command line with a + fully specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + --network-peering=NETWORK_PEERING + ID of the VMware Engine VPC network peering or fully qualified + identifier for the VMware Engine VPC network peering. + + To set the network-peering attribute: + ▸ provide the argument --network-peering on the command line. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. diff --git a/gcloud/vmware/network-peerings/update b/gcloud/vmware/network-peerings/update new file mode 100644 index 000000000..86553e94f --- /dev/null +++ b/gcloud/vmware/network-peerings/update @@ -0,0 +1,57 @@ +NAME + gcloud vmware network-peerings update - update a Google Cloud VMware Engine + VPC network peering + +SYNOPSIS + gcloud vmware network-peerings update NETWORK_PEERING [--async] + [--description=DESCRIPTION] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Update a VMware Engine VPC network peering description. + +EXAMPLES + To update only the description of a VPC network peering named my-peering to + Example description, run: + + $ gcloud vmware network-peerings update my-peering \ + --description="Example description" + + In this example, the project is taken from gcloud properties core/project + and location is taken as global. + +POSITIONAL ARGUMENTS + VMware Engine VPC network peering resource - network_peering. This + represents a Cloud resource. (NOTE) Some attributes are not given + arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument network_peering on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + NETWORK_PEERING + ID of the VMware Engine VPC network peering or fully qualified + identifier for the VMware Engine VPC network peering. + + To set the network-peering attribute: + ▸ provide the argument network_peering on the command line. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. The default is True. Enabled by default, use --no-async to + disable. + + --description=DESCRIPTION + Updated description for this VPC network peering. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. diff --git a/gcloud/vmware/network-policies/external-access-rules/create b/gcloud/vmware/network-policies/external-access-rules/create new file mode 100644 index 000000000..776a07c56 --- /dev/null +++ b/gcloud/vmware/network-policies/external-access-rules/create @@ -0,0 +1,141 @@ +NAME + gcloud vmware network-policies external-access-rules create - create a + VMware Engine external access firewall rule + +SYNOPSIS + gcloud vmware network-policies external-access-rules create + (EXTERNAL_ACCESS_RULE + : --location=LOCATION --network-policy=NETWORK_POLICY) + --destination-ranges=DESTINATION_IP_RANGES,[...] + --ip-protocol=IP_PROTOCOL --priority=PRIORITY + --source-ranges=SOURCE_IP_RANGES,[...] + [--action=ACTION; default="ALLOW"] [--async] + [--description=DESCRIPTION] + [--destination-ports=DESTINATION_PORTS,[...]] + [--source-ports=SOURCE_PORTS,[...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Create a VMware Engine external access firewall rule. Check the progress of + a VMware Engine external access firewall rule creation using gcloud vmware + network-policies external-access-rules list. + +EXAMPLES + To create an external access firewall rule called my-external-access-rule + associated with the network policy my-network-policy in the us-west2 + region, run: + + $ gcloud vmware network-policies external-access-rules create \ + my-external-access-rule --network-policy=my-network-policy \ + --priority=1000 --ip-protocol=TCP \ + --source-ranges=34.148.30.114/32 \ + --destination-ranges=projects/sample-project/locations/\ + us-west2-a/privateClouds/my-private-cloud/externalAddresses/\ + my-external-address --source-ports=22,10000-11000 \ + --destination-ports=22 --action=ALLOW --location=us-west2 \ + --project=sample-project + + Or: + + $ gcloud vmware network-policies external-access-rules create \ + my-external-access-rule --network-policy=my-network-policy \ + --priority=1000 --ip-protocol=TCP \ + --source-ranges=34.148.30.114/32 \ + --destination-ranges=projects/sample-project/locations/\ + us-west2-a/privateClouds/my-private-cloud/externalAddresses/\ + my-external-address --source-ports=22,10000-11000 \ + --destination-ports=22 + + In the second example, the project and the location are taken from gcloud + properties core/project and compute/region respectively. The --action field + also isn't specified, so its value defaults to ALLOW. + +POSITIONAL ARGUMENTS + VMware Engine External Access Rule resource - external_access_rule. The + arguments in this group can be used to specify the attributes of this + resource. (NOTE) Some attributes are not given arguments in this group but + can be set in other ways. + + To set the project attribute: + ◆ provide the argument external_access_rule 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. + + EXTERNAL_ACCESS_RULE + ID of the VMware Engine External Access Rule or fully qualified + identifier for the VMware Engine External Access Rule. + + To set the external-access-rule attribute: + ▸ provide the argument external_access_rule on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The resource name of the location. + + To set the location attribute: + ▸ provide the argument external_access_rule on the command line + with a fully specified name; + ▸ provide the argument --location on the command line; + ▸ set the property compute/region. + + --network-policy=NETWORK_POLICY + VMware Engine network policy + + To set the network-policy attribute: + ▸ provide the argument external_access_rule on the command line + with a fully specified name; + ▸ provide the argument --network-policy on the command line. + +REQUIRED FLAGS + --destination-ranges=DESTINATION_IP_RANGES,[...] + A list of destination IP addresses that the rule applies to. Each entry + in the list can be an ExternalAddress resource name or 0.0.0.0/0. When + the value is set to 0.0.0.0/0, all IP addresses are allowed. + + --ip-protocol=IP_PROTOCOL + Internet protocol covered by the rule. Valid values are TCP, UDP, and + ICMP. IP_PROTOCOL must be one of: TCP, UDP, ICMP. + + --priority=PRIORITY + Priority of this external access rule. Valid values are numbers between + 100 and 4096, with 100 being the highest priority. Firewall rules are + processed from highest to lowest priority. + + --source-ranges=SOURCE_IP_RANGES,[...] + A list of source IP addresses that the rule applies to. Each entry in + the list can be a CIDR notation or a single IP address. When the value + is set to 0.0.0.0/0, all IP addresses are allowed. + +OPTIONAL FLAGS + --action=ACTION; default="ALLOW" + Whether the firewall rule allows or denies traffic based on a + successful rule match. By default, the action is ALLOW. ACTION must be + one of: ALLOW, DENY. + + --async + Return immediately, without waiting for the operation in progress to + complete. The default is True. Enabled by default, use --no-async to + disable. + + --description=DESCRIPTION + User-provided description of the external access rule. + + --destination-ports=DESTINATION_PORTS,[...] + List of allowed destination ports. Each entry must be either an integer + or a range. + + --source-ports=SOURCE_PORTS,[...] + List of allowed source ports. Each entry must be either an integer or a + range. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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/vmware/network-policies/external-access-rules/delete b/gcloud/vmware/network-policies/external-access-rules/delete new file mode 100644 index 000000000..653a2411d --- /dev/null +++ b/gcloud/vmware/network-policies/external-access-rules/delete @@ -0,0 +1,84 @@ +NAME + gcloud vmware network-policies external-access-rules delete - delete a + VMware Engine external access rule + +SYNOPSIS + gcloud vmware network-policies external-access-rules delete + (EXTERNAL_ACCESS_RULE + : --location=LOCATION --network-policy=NETWORK_POLICY) [--async] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Delete a VMware Engine external access firewall rule. + +EXAMPLES + To delete an external access firewall rule called my-external-access-rule + in project my-project and region us-west2 associated with network policy + my-network-policy, run: + + $ gcloud vmware network-policies external-access-rules delete \ + my-external-access-rule --location=us-west2 \ + --project=my-project --network-policy=my-network-policy + + Or: + + $ gcloud vmware network-policies external-access-rules delete \ + my-external-access-rule --network-policy=my-network-policy + + In the second example, the project and the location are taken from gcloud + properties core/project and compute/region respectively. + +POSITIONAL ARGUMENTS + VMware Engine External Access Rule resource - external_access_rule. The + arguments in this group can be used to specify the attributes of this + resource. (NOTE) Some attributes are not given arguments in this group but + can be set in other ways. + + To set the project attribute: + ◆ provide the argument external_access_rule 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. + + EXTERNAL_ACCESS_RULE + ID of the VMware Engine External Access Rule or fully qualified + identifier for the VMware Engine External Access Rule. + + To set the external-access-rule attribute: + ▸ provide the argument external_access_rule on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The resource name of the location. + + To set the location attribute: + ▸ provide the argument external_access_rule on the command line + with a fully specified name; + ▸ provide the argument --location on the command line; + ▸ set the property compute/region. + + --network-policy=NETWORK_POLICY + VMware Engine network policy + + To set the network-policy attribute: + ▸ provide the argument external_access_rule on the command line + with a fully specified name; + ▸ provide the argument --network-policy on the command line. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. The default is True. Enabled by default, use --no-async to + disable. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. diff --git a/gcloud/vmware/network-policies/external-access-rules/describe b/gcloud/vmware/network-policies/external-access-rules/describe new file mode 100644 index 000000000..ae4110ffa --- /dev/null +++ b/gcloud/vmware/network-policies/external-access-rules/describe @@ -0,0 +1,78 @@ +NAME + gcloud vmware network-policies external-access-rules describe - describe a + VMware Engine external access rule + +SYNOPSIS + gcloud vmware network-policies external-access-rules describe + (EXTERNAL_ACCESS_RULE + : --location=LOCATION --network-policy=NETWORK_POLICY) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Describe a VMware Engine external access firewall rule. + +EXAMPLES + To get a description of an external access firewall rule called + my-external-access-rule in project my-project and region us-west2 + associated with network policy my-network-policy, run: + + $ gcloud vmware network-policies external-access-rules describe \ + my-external-access-rule --network-policy=my-network-policy \ + --location=us-west2 --project=my-project + + Or: + + $ gcloud vmware network-policies external-access-rules describe \ + my-external-access-rule --network-policy=my-network-policy + + In the second example, the project and the location are taken from gcloud + properties core/project and compute/region respectively. + +POSITIONAL ARGUMENTS + VMware Engine External Access Rule resource - external_access_rule. The + arguments in this group can be used to specify the attributes of this + resource. (NOTE) Some attributes are not given arguments in this group but + can be set in other ways. + + To set the project attribute: + ◆ provide the argument external_access_rule 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. + + EXTERNAL_ACCESS_RULE + ID of the VMware Engine External Access Rule or fully qualified + identifier for the VMware Engine External Access Rule. + + To set the external-access-rule attribute: + ▸ provide the argument external_access_rule on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The resource name of the location. + + To set the location attribute: + ▸ provide the argument external_access_rule on the command line + with a fully specified name; + ▸ provide the argument --location on the command line; + ▸ set the property compute/region. + + --network-policy=NETWORK_POLICY + VMware Engine network policy + + To set the network-policy attribute: + ▸ provide the argument external_access_rule on the command line + with a fully specified name; + ▸ provide the argument --network-policy 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. diff --git a/gcloud/vmware/network-policies/external-access-rules/help b/gcloud/vmware/network-policies/external-access-rules/help new file mode 100644 index 000000000..71b7fae45 --- /dev/null +++ b/gcloud/vmware/network-policies/external-access-rules/help @@ -0,0 +1,34 @@ +NAME + gcloud vmware network-policies external-access-rules - manage VMware Engine + external access firewall rules in Google Cloud VMware Engine + +SYNOPSIS + gcloud vmware network-policies external-access-rules COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Manage VMware Engine external access firewall rules in Google Cloud VMware + Engine. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + create + Create a VMware Engine external access firewall rule. + + delete + Delete a VMware Engine external access rule. + + describe + Describe a VMware Engine external access rule. + + list + List VMware Engine external access rules. + + update + Update a VMware Engine network policy. diff --git a/gcloud/vmware/network-policies/external-access-rules/list b/gcloud/vmware/network-policies/external-access-rules/list new file mode 100644 index 000000000..d9f225306 --- /dev/null +++ b/gcloud/vmware/network-policies/external-access-rules/list @@ -0,0 +1,117 @@ +NAME + gcloud vmware network-policies external-access-rules list - list VMware + Engine external access rules + +SYNOPSIS + gcloud vmware network-policies external-access-rules list + (--network-policy=NETWORK_POLICY : --location=LOCATION) + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + List VMware Engine external access firewall rules. + +EXAMPLES + To list external access firewall rules in your project in the region + us-west2 associated with network policy my-network-policy, sorted from + oldest to newest, run: + + $ gcloud vmware network-policies external-access-rules list \ + --location=us-west2 --project=my-project \ + --network-policy=my-network-policy --sort-by=~create_time + + Or: + + $ gcloud vmware network-policies external-access-rules list \ + --sort-by=~create_time --network-policy=my-network-policy + + In the second example, the project and the location are taken from gcloud + properties core/project and compute/region respectively. + + To list custom set of fields of external access firewall rules in a + project, run: + + $ gcloud vmware network-policies external-access-rules list \ + --format="table( + name.segment(-1):label=NAME,, + priority, + ipProtocol, + sourceIpRanges.flatten(show='values'), + sourcePorts.list(), + destinationIpRanges.flatten(show='values'), + destinationPorts.list(), + action + )" + +REQUIRED FLAGS + VMware Engine Network Policy resource - network_policy. The arguments in + this group can be used to specify the attributes of this resource. (NOTE) + Some attributes are not given arguments in this group but can be set in + other ways. + + To set the project attribute: + ◆ provide the argument --network-policy on the command line with a + fully specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + --network-policy=NETWORK_POLICY + ID of the VMware Engine Network Policy or fully qualified identifier + for the VMware Engine Network Policy. + + To set the network-policy attribute: + ▸ provide the argument --network-policy on the command line. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + The resource name of the location. + + To set the location attribute: + ▸ provide the argument --network-policy on the command line with a + fully specified name; + ▸ provide the argument --location on the command line; + ▸ set the property compute/region. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. diff --git a/gcloud/vmware/network-policies/external-access-rules/update b/gcloud/vmware/network-policies/external-access-rules/update new file mode 100644 index 000000000..8c116e83b --- /dev/null +++ b/gcloud/vmware/network-policies/external-access-rules/update @@ -0,0 +1,123 @@ +NAME + gcloud vmware network-policies external-access-rules update - update a + VMware Engine network policy + +SYNOPSIS + gcloud vmware network-policies external-access-rules update + (EXTERNAL_ACCESS_RULE + : --location=LOCATION --network-policy=NETWORK_POLICY) + [--action=ACTION] [--async] [--description=DESCRIPTION] + [--destination-ports=DESTINATION_PORTS,[...]] + [--destination-ranges=DESTINATION_IP_RANGES,[...]] + [--ip-protocol=IP_PROTOCOL] [--priority=PRIORITY] + [--source-ports=SOURCE_PORTS,[...]] + [--source-ranges=SOURCE_IP_RANGES,[...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Update a VMware Engine external access firewall rule. + +EXAMPLES + To update an external access firewall rule named my-external-access-rule so + that it denies the traffic for that rule, run: + + $ gcloud vmware network-policies external-access-rules update \ + my-external-access-rule --network-policy=my-network-policy \ + --action=DENY --location=us-west2 --project=my-project + + Or: + + $ gcloud vmware network-policies external-access-rules update \ + my-external-access-rule --network-policy=my-network-policy \ + --action=DENY + + In the second example, the project and the location are taken from gcloud + properties core/project and compute/regions respectively. + +POSITIONAL ARGUMENTS + VMware Engine External Access Rule resource - external_access_rule. The + arguments in this group can be used to specify the attributes of this + resource. (NOTE) Some attributes are not given arguments in this group but + can be set in other ways. + + To set the project attribute: + ◆ provide the argument external_access_rule 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. + + EXTERNAL_ACCESS_RULE + ID of the VMware Engine External Access Rule or fully qualified + identifier for the VMware Engine External Access Rule. + + To set the external-access-rule attribute: + ▸ provide the argument external_access_rule on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The resource name of the location. + + To set the location attribute: + ▸ provide the argument external_access_rule on the command line + with a fully specified name; + ▸ provide the argument --location on the command line; + ▸ set the property compute/region. + + --network-policy=NETWORK_POLICY + VMware Engine network policy + + To set the network-policy attribute: + ▸ provide the argument external_access_rule on the command line + with a fully specified name; + ▸ provide the argument --network-policy on the command line. + +FLAGS + --action=ACTION + Whether the firewall rule allows or denies traffic based on a + successful rule match. ACTION must be one of: ALLOW, DENY. + + --async + Return immediately, without waiting for the operation in progress to + complete. The default is True. Enabled by default, use --no-async to + disable. + + --description=DESCRIPTION + User-provided description of the external access rule. + + --destination-ports=DESTINATION_PORTS,[...] + List of allowed destination ports. Each entry must be either an integer + or a range. + + --destination-ranges=DESTINATION_IP_RANGES,[...] + A list of destination IP addresses that the rule applies to. Each entry + in the list be an ExternalAddress resource name or 0.0.0.0/0. When the + value is set to 0.0.0.0/0, all IP addresses are allowed. + + --ip-protocol=IP_PROTOCOL + Internet protocol covered by the rule. Valid values are TCP, UDP, and + ICMP. IP_PROTOCOL must be one of: TCP, UDP, ICMP. + + --priority=PRIORITY + Priority of this external access rule. Valid values are numbers between + 100 and 4096, with 100 being the highest priority. Firewall rules are + processed from highest to lowest priority. + + --source-ports=SOURCE_PORTS,[...] + List of allowed source ports. Each entry must be either an integer or a + range. + + --source-ranges=SOURCE_IP_RANGES,[...] + A list of source IP addresses that the rule applies to. Each entry in + the list can be a CIDR notation or a single IP address. When the value + is set to 0.0.0.0/0, all IP addresses are allowed. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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/vmware/network-policies/help b/gcloud/vmware/network-policies/help index 9a81b4f69..72ca5730f 100644 --- a/gcloud/vmware/network-policies/help +++ b/gcloud/vmware/network-policies/help @@ -13,6 +13,13 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. +GROUPS + GROUP is one of the following: + + external-access-rules + Manage VMware Engine external access firewall rules in Google Cloud + VMware Engine. + COMMANDS COMMAND is one of the following: diff --git a/gcloud/vmware/private-clouds/clusters/help b/gcloud/vmware/private-clouds/clusters/help index c36006b2b..d8b063500 100644 --- a/gcloud/vmware/private-clouds/clusters/help +++ b/gcloud/vmware/private-clouds/clusters/help @@ -14,6 +14,12 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. +GROUPS + GROUP is one of the following: + + nodes + Manage nodes in Google Cloud VMware Engine. + COMMANDS COMMAND is one of the following: diff --git a/gcloud/vmware/private-clouds/clusters/nodes/describe b/gcloud/vmware/private-clouds/clusters/nodes/describe new file mode 100644 index 000000000..07c285a85 --- /dev/null +++ b/gcloud/vmware/private-clouds/clusters/nodes/describe @@ -0,0 +1,83 @@ +NAME + gcloud vmware private-clouds clusters nodes describe - describe a Google + Cloud VMware Engine node + +SYNOPSIS + gcloud vmware private-clouds clusters nodes describe + (NODE : --cluster=CLUSTER + --location=LOCATION --private-cloud=PRIVATE_CLOUD) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Display data associated with a VMware Engine node, such as its name, state, + node type, ip, fqdn. + +EXAMPLES + To describe a node called my-node in private cloud my-private-cloud cluster + my-cluster and zone us-west2-a, run: + + $ gcloud vmware private-clouds clusters nodes describe my-node \ + --location=us-west2-a --project=my-project \ + --private-cloud=my-private-cloud --cluster=my-cluster + + Or: + + $ gcloud vmware private-clouds clusters nodes describe my-node \ + --private-cloud=my-private-cloud --cluster=my-cluster + + In the second example, the project and location are taken from gcloud properties core/project and compute/zone. + +POSITIONAL ARGUMENTS + Node resource - node. The arguments in this group can be used to specify + the attributes of this resource. (NOTE) Some attributes are not given + arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument node on the command line with a fully specified + name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + NODE + ID of the node or fully qualified identifier for the node. + + To set the node attribute: + ▸ provide the argument node on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --cluster=CLUSTER + Resource ID of the cluster + + To set the cluster attribute: + ▸ provide the argument node on the command line with a fully + specified name; + ▸ provide the argument --cluster on the command line. + + --location=LOCATION + Location of the private cloud or cluster. + + To set the location attribute: + ▸ provide the argument node on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property compute/zone. + + --private-cloud=PRIVATE_CLOUD + VMware Engine private cloud. + + To set the private-cloud attribute: + ▸ provide the argument node on the command line with a fully + specified name; + ▸ provide the argument --private-cloud on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. diff --git a/gcloud/vmware/private-clouds/clusters/nodes/help b/gcloud/vmware/private-clouds/clusters/nodes/help new file mode 100644 index 000000000..d42e762f0 --- /dev/null +++ b/gcloud/vmware/private-clouds/clusters/nodes/help @@ -0,0 +1,23 @@ +NAME + gcloud vmware private-clouds clusters nodes - manage nodes in Google Cloud + VMware Engine + +SYNOPSIS + gcloud vmware private-clouds clusters nodes COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Manage nodes in Google Cloud VMware Engine. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + describe + Describe a Google Cloud VMware Engine node. + + list + List nodes in a Google Cloud VMware Engine private cloud's cluster. diff --git a/gcloud/vmware/private-clouds/clusters/nodes/list b/gcloud/vmware/private-clouds/clusters/nodes/list new file mode 100644 index 000000000..b98a049a6 --- /dev/null +++ b/gcloud/vmware/private-clouds/clusters/nodes/list @@ -0,0 +1,106 @@ +NAME + gcloud vmware private-clouds clusters nodes list - list nodes in a Google + Cloud VMware Engine private cloud's cluster + +SYNOPSIS + gcloud vmware private-clouds clusters nodes list + (--cluster=CLUSTER : --location=LOCATION --private-cloud=PRIVATE_CLOUD) + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + List nodes in a VMware Engine private cloud's cluster. + +EXAMPLES + To list nodes in the my-private-cloud private cloud and my-cluster cluster: + + $ gcloud vmware private-clouds clusters nodes list \ + --location=us-west2-a --project=my-project \ + --private-cloud=my-private-cloud --cluster=my-cluster + + Or: + + $ gcloud vmware private-clouds clusters nodes list \ + --private-cloud=my-private-cloud --cluster=my-cluster + + In the second example, the project and location are taken from gcloud + properties core/project and compute/zone. + +REQUIRED FLAGS + Cluster resource - cluster. The arguments in this group can be used to + specify the attributes of this resource. (NOTE) Some attributes are not + given arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument --cluster on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + --cluster=CLUSTER + ID of the cluster or fully qualified identifier for the cluster. + + To set the cluster attribute: + ▸ provide the argument --cluster on the command line. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + Location of the private cloud or cluster. + + To set the location attribute: + ▸ provide the argument --cluster on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property compute/zone. + + --private-cloud=PRIVATE_CLOUD + VMware Engine private cloud. + + To set the private-cloud attribute: + ▸ provide the argument --cluster on the command line with a fully + specified name; + ▸ provide the argument --private-cloud on the command line. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. diff --git a/gcloud/vmware/private-clouds/create b/gcloud/vmware/private-clouds/create index f943360ff..6c8716ee7 100644 --- a/gcloud/vmware/private-clouds/create +++ b/gcloud/vmware/private-clouds/create @@ -7,7 +7,9 @@ SYNOPSIS --node-type-config=[count=COUNT], [custom-core-count=CUSTOM-CORE-COUNT],[type=TYPE] --vmware-engine-network=VMWARE_ENGINE_NETWORK [--async] - [--description=DESCRIPTION] [GCLOUD_WIDE_FLAG ...] + [--description=DESCRIPTION] [--preferred-zone=PREFERRED_ZONE] + [--secondary-zone=SECONDARY_ZONE] [--type=TYPE; default="STANDARD"] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION Create a VMware Engine private cloud. Private cloud creation is considered @@ -140,6 +142,31 @@ OPTIONAL FLAGS --description=DESCRIPTION Text describing the private cloud. + --preferred-zone=PREFERRED_ZONE + Zone that will remain operational when connection between the two zones + is lost. Specify the resource name of a zone that belongs to the region + of the private cloud. + + --secondary-zone=SECONDARY_ZONE + Additional zone for a higher level of availability and load balancing. + Specify the resource name of a zone that belongs to the region of the + private cloud. + + --type=TYPE; default="STANDARD" + Type of the private cloud. TYPE must be one of: + + STANDARD + Standard private is a zonal resource, with 3 or more nodes nodes. + Default type. + STRETCHED + Stretched private cloud is a regional resource with redundancy, + with a minimum of 6 nodes, nodes count has to be even. + TIME_LIMITED + Time limited private cloud is a zonal resource, can have only 1 + node and has limited life span. Will be deleted after defined + period of time, can be converted into standard private cloud by + expanding it up to 3 or more nodes. + 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/vmware/private-clouds/dns-forwarding/describe b/gcloud/vmware/private-clouds/dns-forwarding/describe new file mode 100644 index 000000000..6c3522470 --- /dev/null +++ b/gcloud/vmware/private-clouds/dns-forwarding/describe @@ -0,0 +1,67 @@ +NAME + gcloud vmware private-clouds dns-forwarding describe - describe a Google + Cloud VMware Engine dns-forwarding + +SYNOPSIS + gcloud vmware private-clouds dns-forwarding describe + (--private-cloud=PRIVATE_CLOUD : --location=LOCATION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Display data associated with a VMware Engine DNS forwarding, such as the + domains and their respective name servers. + +EXAMPLES + To describe a DNS forwarding config in private cloud my-private-cloud and + zone us-west2-a, run: + + $ gcloud vmware private-clouds dns-forwarding describe \ + --location=us-west2-a --project=my-project \ + --private-cloud=my-private-cloud + + Or: + + $ gcloud vmware private-clouds dns-forwarding describe \ + --private-cloud=my-private-cloud + + In the second example, the project and location are taken from gcloud properties core/project and compute/zone. + +REQUIRED FLAGS + Private cloud resource - private_cloud. The arguments in this group can be + used to specify the attributes of this resource. (NOTE) Some attributes + are not given arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument --private-cloud on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + --private-cloud=PRIVATE_CLOUD + ID of the private cloud or fully qualified identifier for the private + cloud. + + To set the private-cloud attribute: + ▸ provide the argument --private-cloud on the command line. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + Location of the private cloud or cluster. + + To set the location attribute: + ▸ provide the argument --private-cloud on the command line with a + fully specified name; + ▸ provide the argument --location on the command line; + ▸ set the property compute/zone. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. diff --git a/gcloud/vmware/private-clouds/dns-forwarding/help b/gcloud/vmware/private-clouds/dns-forwarding/help new file mode 100644 index 000000000..b8a4c8357 --- /dev/null +++ b/gcloud/vmware/private-clouds/dns-forwarding/help @@ -0,0 +1,23 @@ +NAME + gcloud vmware private-clouds dns-forwarding - manage dns-forwarding in + Google Cloud VMware Engine + +SYNOPSIS + gcloud vmware private-clouds dns-forwarding COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Manage dns-forwarding in Google Cloud VMware Engine. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + describe + Describe a Google Cloud VMware Engine dns-forwarding. + + update + Update a Google Cloud VMware Engine dns-forwarding. diff --git a/gcloud/vmware/private-clouds/dns-forwarding/update b/gcloud/vmware/private-clouds/dns-forwarding/update new file mode 100644 index 000000000..0e0797494 --- /dev/null +++ b/gcloud/vmware/private-clouds/dns-forwarding/update @@ -0,0 +1,88 @@ +NAME + gcloud vmware private-clouds dns-forwarding update - update a Google Cloud + VMware Engine dns-forwarding + +SYNOPSIS + gcloud vmware private-clouds dns-forwarding update + (--private-cloud=PRIVATE_CLOUD : --location=LOCATION) [--async] + [--rule=[domain=DOMAIN, + name-servers="NAME_SERVER1;NAME_SERVER2[;NAME_SERVER3]",...]] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Update DNS forwarding. + +EXAMPLES + To update a DNS forwarding config in private cloud my-private-cloud and + zone us-west2-a to forward DNS requests for domain activedirectory.my.corp + to name servers 192.168.20.15 and 192.168.20.16 and for domain + proxy.my.corp to nameservers 192.168.30.15 and 192.168.30.16, run: + + $ gcloud vmware private-clouds dns-forwarding update \ + --location=us-west2-a --project=my-project \ + --private-cloud=my-private-cloud \ + --rule=domain=activedirectory.my.corp,\ + name-servers=192.168.20.15;192.168.20.16 \ + --rule=domain=proxy.my.corp,name-servers=192.168.30.15;\ + 192.168.30.16 + + Or: + + $ gcloud vmware private-clouds dns-forwarding update \ + --private-cloud=my-private-cloud \ + --rule=domain=activedirectory.my.corp,\ + name-servers=192.168.20.15;192.168.20.16 \ + --rule=domain=proxy.my.corp,name-servers=192.168.30.15;\ + 192.168.30.16 + + In the second example, the project and location are taken from gcloud properties core/project and compute/zone. + +REQUIRED FLAGS + Private cloud resource - private_cloud. The arguments in this group can be + used to specify the attributes of this resource. (NOTE) Some attributes + are not given arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument --private-cloud on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + --private-cloud=PRIVATE_CLOUD + ID of the private cloud or fully qualified identifier for the private + cloud. + + To set the private-cloud attribute: + ▸ provide the argument --private-cloud on the command line. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + Location of the private cloud or cluster. + + To set the location attribute: + ▸ provide the argument --private-cloud on the command line with a + fully specified name; + ▸ provide the argument --location on the command line; + ▸ set the property compute/zone. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. The default is True. Enabled by default, use --no-async to + disable. + + --rule=[domain=DOMAIN,name-servers="NAME_SERVER1;NAME_SERVER2[;NAME_SERVER3]",...] + Domain name and the name servers used to resolve DNS requests for this + domain. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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/vmware/private-clouds/external-addresses/create b/gcloud/vmware/private-clouds/external-addresses/create new file mode 100644 index 000000000..f7764323c --- /dev/null +++ b/gcloud/vmware/private-clouds/external-addresses/create @@ -0,0 +1,94 @@ +NAME + gcloud vmware private-clouds external-addresses create - create an external + IP address + +SYNOPSIS + gcloud vmware private-clouds external-addresses create + (EXTERNAL_ADDRESS : --location=LOCATION --private-cloud=PRIVATE_CLOUD) + --internal-ip=INTERNAL_IP [--async] [--description=DESCRIPTION] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Create an external IP address that represents an allocated external IP + address and its corresponding internal IP address in the private cloud. + +EXAMPLES + To create an external IP address called myip that corresponds to the + internal IP address 165.87.54.14 that belongs to the private cloud + my-private-cloud in project my-project and location us-east2-b, run: + + $ gcloud vmware private-clouds external-addresses create myip \ + --project=my-project --private-cloud=my-private-cloud \ + --location=us-east2-b --internal-ip=165.87.54.14 \ + --description="A short description for the new external address" + + Or: + + $ gcloud vmware private-clouds external-addresses create myip \ + --private-cloud=my-private-cloud --internal-ip=165.87.54.14 \ + --description="A short description for the new external address" + + In the second example, the project and region are taken from gcloud + properties core/project and vmware/region. + +POSITIONAL ARGUMENTS + External address resource - external_address. The arguments in this group + can be used to specify the attributes of this resource. (NOTE) Some + attributes are not given arguments in this group but can be set in other + ways. + + To set the project attribute: + ◆ provide the argument external_address 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. + + EXTERNAL_ADDRESS + ID of the external address or fully qualified identifier for the + external address. + + To set the external-address attribute: + ▸ provide the argument external_address on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Location of the private cloud or cluster. + + To set the location attribute: + ▸ provide the argument external_address on the command line with a + fully specified name; + ▸ provide the argument --location on the command line; + ▸ set the property compute/zone. + + --private-cloud=PRIVATE_CLOUD + VMware Engine private cloud. + + To set the private-cloud attribute: + ▸ provide the argument external_address on the command line with a + fully specified name; + ▸ provide the argument --private-cloud on the command line. + +REQUIRED FLAGS + --internal-ip=INTERNAL_IP + internal ip address to which external address will be linked + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. The default is True. Enabled by default, use --no-async to + disable. + + --description=DESCRIPTION + Text describing the external address + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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/vmware/private-clouds/external-addresses/delete b/gcloud/vmware/private-clouds/external-addresses/delete new file mode 100644 index 000000000..c9f9ba873 --- /dev/null +++ b/gcloud/vmware/private-clouds/external-addresses/delete @@ -0,0 +1,82 @@ +NAME + gcloud vmware private-clouds external-addresses delete - delete external IP + address from a VMware Engine private cloud + +SYNOPSIS + gcloud vmware private-clouds external-addresses delete + (EXTERNAL_ADDRESS : --location=LOCATION --private-cloud=PRIVATE_CLOUD) + [--async] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Delete external IP address from a VMware Engine private cloud. + +EXAMPLES + To delete an external IP address called first-ip in private cloud + my-privatecloud and location us-east2-b, run: + + $ gcloud vmware private-clouds external-addresses delete first-ip \ + --private-cloud=my-privatecloud --location=us-east2-b \ + --project=my-project + + Or: + + $ gcloud vmware private-clouds external-addresses delete first-ip \ + --private-cloud=my-privatecloud + + In the second example, the project and region are taken from gcloud + properties core/project and vmware/region. + +POSITIONAL ARGUMENTS + External address resource - external_address. The arguments in this group + can be used to specify the attributes of this resource. (NOTE) Some + attributes are not given arguments in this group but can be set in other + ways. + + To set the project attribute: + ◆ provide the argument external_address 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. + + EXTERNAL_ADDRESS + ID of the external address or fully qualified identifier for the + external address. + + To set the external-address attribute: + ▸ provide the argument external_address on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Location of the private cloud or cluster. + + To set the location attribute: + ▸ provide the argument external_address on the command line with a + fully specified name; + ▸ provide the argument --location on the command line; + ▸ set the property compute/zone. + + --private-cloud=PRIVATE_CLOUD + VMware Engine private cloud. + + To set the private-cloud attribute: + ▸ provide the argument external_address on the command line with a + fully specified name; + ▸ provide the argument --private-cloud on the command line. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. The default is True. Enabled by default, use --no-async to + disable. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. diff --git a/gcloud/vmware/private-clouds/external-addresses/describe b/gcloud/vmware/private-clouds/external-addresses/describe new file mode 100644 index 000000000..5a1ec0790 --- /dev/null +++ b/gcloud/vmware/private-clouds/external-addresses/describe @@ -0,0 +1,76 @@ +NAME + gcloud vmware private-clouds external-addresses describe - describe an + external IP address in a VMware Engine private cloud + +SYNOPSIS + gcloud vmware private-clouds external-addresses describe + (EXTERNAL_ADDRESS : --location=LOCATION --private-cloud=PRIVATE_CLOUD) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Describe an external IP address in a VMware Engine private cloud. + +EXAMPLES + To get a description of an address called first-ip in the my-privatecloud + private cloud in the us-east2-b location, run: + + $ gcloud vmware private-clouds external-addresses describe \ + first-ip --private-cloud=my-privatecloud --location=us-east2-b \ + --project=my-project + + Or: + + $ gcloud vmware private-clouds external-addresses describe \ + first-ip --private-cloud=my-privatecloud + + In the second example, the project and region are taken from gcloud + properties core/project and vmware/region. + +POSITIONAL ARGUMENTS + External address resource - external_address. The arguments in this group + can be used to specify the attributes of this resource. (NOTE) Some + attributes are not given arguments in this group but can be set in other + ways. + + To set the project attribute: + ◆ provide the argument external_address 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. + + EXTERNAL_ADDRESS + ID of the external address or fully qualified identifier for the + external address. + + To set the external-address attribute: + ▸ provide the argument external_address on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Location of the private cloud or cluster. + + To set the location attribute: + ▸ provide the argument external_address on the command line with a + fully specified name; + ▸ provide the argument --location on the command line; + ▸ set the property compute/zone. + + --private-cloud=PRIVATE_CLOUD + VMware Engine private cloud. + + To set the private-cloud attribute: + ▸ provide the argument external_address on the command line with a + fully specified name; + ▸ provide the argument --private-cloud on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. diff --git a/gcloud/vmware/private-clouds/external-addresses/help b/gcloud/vmware/private-clouds/external-addresses/help new file mode 100644 index 000000000..a96bad489 --- /dev/null +++ b/gcloud/vmware/private-clouds/external-addresses/help @@ -0,0 +1,33 @@ +NAME + gcloud vmware private-clouds external-addresses - manage external IP + addresses in Google Cloud VMware Engine + +SYNOPSIS + gcloud vmware private-clouds external-addresses COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Manage external IP addresses in Google Cloud VMware Engine. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + create + Create an external IP address. + + delete + Delete external IP address from a VMware Engine private cloud. + + describe + Describe an external IP address in a VMware Engine private cloud. + + list + List external IP addresses in a VMware Engine private cloud. + + update + Update an external IP address in a VMware Engine private cloud. diff --git a/gcloud/vmware/private-clouds/external-addresses/list b/gcloud/vmware/private-clouds/external-addresses/list new file mode 100644 index 000000000..fe6a47d8a --- /dev/null +++ b/gcloud/vmware/private-clouds/external-addresses/list @@ -0,0 +1,91 @@ +NAME + gcloud vmware private-clouds external-addresses list - list external IP + addresses in a VMware Engine private cloud + +SYNOPSIS + gcloud vmware private-clouds external-addresses list + (--private-cloud=PRIVATE_CLOUD : --location=LOCATION) + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + List external IP addresses in a VMware Engine private cloud. + +EXAMPLES + To list external IP addresses in the my-privatecloud private cloud, run: + + $ gcloud vmware private-clouds external-addresses list \ + --private-cloud=my-privatecloud --project=my-project \ + --location=us-east2-b + +REQUIRED FLAGS + Private cloud resource - private_cloud. The arguments in this group can be + used to specify the attributes of this resource. (NOTE) Some attributes + are not given arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument --private-cloud on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + --private-cloud=PRIVATE_CLOUD + ID of the private cloud or fully qualified identifier for the private + cloud. + + To set the private-cloud attribute: + ▸ provide the argument --private-cloud on the command line. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + Location of the private cloud or cluster. + + To set the location attribute: + ▸ provide the argument --private-cloud on the command line with a + fully specified name; + ▸ provide the argument --location on the command line; + ▸ set the property compute/zone. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. diff --git a/gcloud/vmware/private-clouds/external-addresses/update b/gcloud/vmware/private-clouds/external-addresses/update new file mode 100644 index 000000000..d180a38b6 --- /dev/null +++ b/gcloud/vmware/private-clouds/external-addresses/update @@ -0,0 +1,94 @@ +NAME + gcloud vmware private-clouds external-addresses update - update an external + IP address in a VMware Engine private cloud + +SYNOPSIS + gcloud vmware private-clouds external-addresses update + (EXTERNAL_ADDRESS : --location=LOCATION --private-cloud=PRIVATE_CLOUD) + [--async] [--description=DESCRIPTION] [--internal-ip=INTERNAL_IP] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Updates an external IP address in a VMware Engine private cloud. Only + description and internal-ip can be updated. + +EXAMPLES + To update an external IP address called myip that belongs to the private + cloud my-private-cloud in project my-project and location us-west1-a by + changing its description to "Updated description for the external IP + address" and internal-ip to 165.87.54.14, run: + + $ gcloud vmware private-clouds external-addresses update myip \ + --project=my-project --private-cloud=my-private-cloud \ + --location=us-west1-a --internal-ip=165.87.54.14 \ + --description="Updated description for the external IP address" + + Or: + + $ gcloud vmware private-clouds external-addresses update myip \ + --private-cloud=my-private-cloud --internal-ip=165.87.54.14 \ + --description="Updated description for the external IP address" + + In the second example, the project and region are taken from gcloud + properties core/project and vmware/region. + +POSITIONAL ARGUMENTS + External address resource - external_address. The arguments in this group + can be used to specify the attributes of this resource. (NOTE) Some + attributes are not given arguments in this group but can be set in other + ways. + + To set the project attribute: + ◆ provide the argument external_address 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. + + EXTERNAL_ADDRESS + ID of the external address or fully qualified identifier for the + external address. + + To set the external-address attribute: + ▸ provide the argument external_address on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Location of the private cloud or cluster. + + To set the location attribute: + ▸ provide the argument external_address on the command line with a + fully specified name; + ▸ provide the argument --location on the command line; + ▸ set the property compute/zone. + + --private-cloud=PRIVATE_CLOUD + VMware Engine private cloud. + + To set the private-cloud attribute: + ▸ provide the argument external_address on the command line with a + fully specified name; + ▸ provide the argument --private-cloud on the command line. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. The default is True. Enabled by default, use --no-async to + disable. + + --description=DESCRIPTION + Updated description for this external address + + --internal-ip=INTERNAL_IP + Updated internal ip address for this external address + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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/vmware/private-clouds/help b/gcloud/vmware/private-clouds/help index 8cc486a5b..9cf71936b 100644 --- a/gcloud/vmware/private-clouds/help +++ b/gcloud/vmware/private-clouds/help @@ -19,9 +19,21 @@ GROUPS clusters Manage clusters in Google Cloud VMware Engine. + dns-forwarding + Manage dns-forwarding in Google Cloud VMware Engine. + + external-addresses + Manage external IP addresses in Google Cloud VMware Engine. + hcx Manage HCX using Google Cloud VMware Engine. + logging-servers + Manage logging-server in Google Cloud VMware Engine. + + management-dns-zone-bindings + Manage Management DNS zone bindings in Google Cloud VMware Engine. + nsx Manage NSX using Google Cloud VMware Engine. diff --git a/gcloud/vmware/private-clouds/logging-servers/create b/gcloud/vmware/private-clouds/logging-servers/create new file mode 100644 index 000000000..c1293a6ea --- /dev/null +++ b/gcloud/vmware/private-clouds/logging-servers/create @@ -0,0 +1,101 @@ +NAME + gcloud vmware private-clouds logging-servers create - create a Google Cloud + VMware Engine logging-server + +SYNOPSIS + gcloud vmware private-clouds logging-servers create + (LOGGING_SERVER : --location=LOCATION --private-cloud=PRIVATE_CLOUD) + --hostname=HOSTNAME --port=PORT --protocol=PROTOCOL + --source-type=SOURCE_TYPE [--async] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Create a logging-server in a VMware Engine private cloud to forward VCSA or + ESXI logs to it. + +EXAMPLES + To create a logging-server called my-logging-server in private cloud + my-private-cloud, with source type ESXI, host name 192.168.0.30, protocol + UDP and port 514, run: + + $ gcloud vmware private-clouds logging-servers create \ + my-logging-server --location=us-west2-a --project=my-project \ + --private-cloud=my-private-cloud --source-type=ESXI \ + --hostname=192.168.0.30 --protocol=UDP --port=514 + + Or: + + $ gcloud vmware private-clouds logging-servers create \ + my-logging-server --private-cloud=my-private-cloud \ + --source-type=ESXI --hostname=192.168.0.30 --protocol=UDP \ + --port=514 + + In the second example, the project and location are taken from gcloud properties core/project and compute/zone. + +POSITIONAL ARGUMENTS + Logging Server resource - logging_server. The arguments in this group can + be used to specify the attributes of this resource. (NOTE) Some attributes + are not given arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument logging_server 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. + + LOGGING_SERVER + ID of the Logging Server or fully qualified identifier for the + Logging Server. + + To set the logging-server attribute: + ▸ provide the argument logging_server on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Location of the private cloud or cluster. + + To set the location attribute: + ▸ provide the argument logging_server on the command line with a + fully specified name; + ▸ provide the argument --location on the command line; + ▸ set the property compute/zone. + + --private-cloud=PRIVATE_CLOUD + VMware Engine private cloud. + + To set the private-cloud attribute: + ▸ provide the argument logging_server on the command line with a + fully specified name; + ▸ provide the argument --private-cloud on the command line. + +REQUIRED FLAGS + --hostname=HOSTNAME + Fully-qualified domain name (FQDN) or IP Address of the logging server. + + --port=PORT + Port number at which the logging server receives logs. + + --protocol=PROTOCOL + Defines possible protocols used to send logs to a logging server. + PROTOCOL must be one of: UDP, TCP. + + --source-type=SOURCE_TYPE + The type of component that produces logs that will be forwarded to this + logging server. SOURCE_TYPE must be one of: VCSA, ESXI. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. The default is True. Enabled by default, use --no-async to + disable. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. diff --git a/gcloud/vmware/private-clouds/logging-servers/delete b/gcloud/vmware/private-clouds/logging-servers/delete new file mode 100644 index 000000000..0b9ef82f7 --- /dev/null +++ b/gcloud/vmware/private-clouds/logging-servers/delete @@ -0,0 +1,81 @@ +NAME + gcloud vmware private-clouds logging-servers delete - delete logging-server + from a VMware Engine private cloud + +SYNOPSIS + gcloud vmware private-clouds logging-servers delete + (LOGGING_SERVER : --location=LOCATION --private-cloud=PRIVATE_CLOUD) + [--async] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Delete logging-server from a VMware Engine private cloud. + +EXAMPLES + To delete an logging-server called my-logging-server in private cloud + my-private-cloud and location us-east2-b, run: + + $ gcloud vmware private-clouds logging-servers delete \ + my-logging-server --private-cloud=my-private-cloud \ + --location=us-east2-b --project=my-project + + Or: + + $ gcloud vmware private-clouds logging-servers delete \ + my-logging-server --private-cloud=my-private-cloud + + In the second example, the project and region are taken from gcloud + properties core/project and vmware/region. + +POSITIONAL ARGUMENTS + Logging Server resource - logging_server. The arguments in this group can + be used to specify the attributes of this resource. (NOTE) Some attributes + are not given arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument logging_server 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. + + LOGGING_SERVER + ID of the Logging Server or fully qualified identifier for the + Logging Server. + + To set the logging-server attribute: + ▸ provide the argument logging_server on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Location of the private cloud or cluster. + + To set the location attribute: + ▸ provide the argument logging_server on the command line with a + fully specified name; + ▸ provide the argument --location on the command line; + ▸ set the property compute/zone. + + --private-cloud=PRIVATE_CLOUD + VMware Engine private cloud. + + To set the private-cloud attribute: + ▸ provide the argument logging_server on the command line with a + fully specified name; + ▸ provide the argument --private-cloud on the command line. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. The default is True. Enabled by default, use --no-async to + disable. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. diff --git a/gcloud/vmware/private-clouds/logging-servers/describe b/gcloud/vmware/private-clouds/logging-servers/describe new file mode 100644 index 000000000..bed881ec2 --- /dev/null +++ b/gcloud/vmware/private-clouds/logging-servers/describe @@ -0,0 +1,75 @@ +NAME + gcloud vmware private-clouds logging-servers describe - describe a Google + Cloud VMware Engine logging-server + +SYNOPSIS + gcloud vmware private-clouds logging-servers describe + (LOGGING_SERVER : --location=LOCATION --private-cloud=PRIVATE_CLOUD) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Display data associated with a VMware Engine logging-server, such as its + host name, port, protocol, and source type. + +EXAMPLES + To describe a logging-server called my-logging-server in private cloud + my-private-cloud and zone us-west2-a, run: + + $ gcloud vmware private-clouds logging-servers describe \ + my-logging-server --location=us-west2-a --project=my-project \ + --private-cloud=my-private-cloud + + Or: + + $ gcloud vmware private-clouds logging-servers describe \ + my-logging-server --private-cloud=my-private-cloud + + In the second example, the project and location are taken from gcloud properties core/project and compute/zone. + +POSITIONAL ARGUMENTS + Logging Server resource - logging_server. The arguments in this group can + be used to specify the attributes of this resource. (NOTE) Some attributes + are not given arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument logging_server 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. + + LOGGING_SERVER + ID of the Logging Server or fully qualified identifier for the + Logging Server. + + To set the logging-server attribute: + ▸ provide the argument logging_server on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Location of the private cloud or cluster. + + To set the location attribute: + ▸ provide the argument logging_server on the command line with a + fully specified name; + ▸ provide the argument --location on the command line; + ▸ set the property compute/zone. + + --private-cloud=PRIVATE_CLOUD + VMware Engine private cloud. + + To set the private-cloud attribute: + ▸ provide the argument logging_server on the command line with a + fully specified name; + ▸ provide the argument --private-cloud on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. diff --git a/gcloud/vmware/private-clouds/logging-servers/help b/gcloud/vmware/private-clouds/logging-servers/help new file mode 100644 index 000000000..58041f88a --- /dev/null +++ b/gcloud/vmware/private-clouds/logging-servers/help @@ -0,0 +1,32 @@ +NAME + gcloud vmware private-clouds logging-servers - manage logging-server in + Google Cloud VMware Engine + +SYNOPSIS + gcloud vmware private-clouds logging-servers COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Manage logging-server in Google Cloud VMware Engine. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + create + Create a Google Cloud VMware Engine logging-server. + + delete + Delete logging-server from a VMware Engine private cloud. + + describe + Describe a Google Cloud VMware Engine logging-server. + + list + List logging-server in a Google Cloud VMware Engine private cloud. + + update + Update a Google Cloud VMware Engine logging-server. diff --git a/gcloud/vmware/private-clouds/logging-servers/list b/gcloud/vmware/private-clouds/logging-servers/list new file mode 100644 index 000000000..69231f15e --- /dev/null +++ b/gcloud/vmware/private-clouds/logging-servers/list @@ -0,0 +1,99 @@ +NAME + gcloud vmware private-clouds logging-servers list - list logging-server in + a Google Cloud VMware Engine private cloud + +SYNOPSIS + gcloud vmware private-clouds logging-servers list + (--private-cloud=PRIVATE_CLOUD : --location=LOCATION) + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + List logging-server in a VMware Engine private cloud. + +EXAMPLES + To list logger-server in the my-private-cloud private cloud run: + + $ gcloud vmware private-clouds logging-servers list \ + --location=us-west2-a --project=my-project \ + --private-cloud=my-private-cloud + + Or: + + $ gcloud vmware private-clouds logging-servers list \ + --private-cloud=my-private-cloud + + In the second example, the project and location are taken from gcloud + properties core/project and compute/zone. + +REQUIRED FLAGS + Private cloud resource - private_cloud. The arguments in this group can be + used to specify the attributes of this resource. (NOTE) Some attributes + are not given arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument --private-cloud on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + --private-cloud=PRIVATE_CLOUD + ID of the private cloud or fully qualified identifier for the private + cloud. + + To set the private-cloud attribute: + ▸ provide the argument --private-cloud on the command line. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + Location of the private cloud or cluster. + + To set the location attribute: + ▸ provide the argument --private-cloud on the command line with a + fully specified name; + ▸ provide the argument --location on the command line; + ▸ set the property compute/zone. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. diff --git a/gcloud/vmware/private-clouds/logging-servers/update b/gcloud/vmware/private-clouds/logging-servers/update new file mode 100644 index 000000000..708a38a00 --- /dev/null +++ b/gcloud/vmware/private-clouds/logging-servers/update @@ -0,0 +1,100 @@ +NAME + gcloud vmware private-clouds logging-servers update - update a Google Cloud + VMware Engine logging-server + +SYNOPSIS + gcloud vmware private-clouds logging-servers update + (LOGGING_SERVER : --location=LOCATION --private-cloud=PRIVATE_CLOUD) + [--async] [--hostname=HOSTNAME] [--port=PORT] [--protocol=PROTOCOL] + [--source-type=SOURCE_TYPE] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Update a Logging Server. Only source_type, hostname, protocol, port can be + updated. + +EXAMPLES + To update a logging-server called my-logging-server in private cloud + my-private-cloud and zone us-west2-a to change ESXI source_type, + 192.168.20.15 hostname UDP protocol and 514 port, run: + + $ gcloud vmware private-clouds logging-servers update \ + my-logging-server --location=us-west2-a --project=my-project \ + --private-cloud=my-private-cloud --source-type=ESXI \ + --hostname=192.168.20.15 --protocol=UDP --port=514 + + Or: + + $ gcloud vmware private-clouds logging-servers update \ + my-logging-server --private-cloud=my-private-cloud \ + --source-type=ESXI --hostname=192.168.20.15 --protocol=UDP \ + --port=514 + + In the second example, the project and location are taken from gcloud properties core/project and compute/zone. + +POSITIONAL ARGUMENTS + Logging Server resource - logging_server. The arguments in this group can + be used to specify the attributes of this resource. (NOTE) Some attributes + are not given arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument logging_server 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. + + LOGGING_SERVER + ID of the Logging Server or fully qualified identifier for the + Logging Server. + + To set the logging-server attribute: + ▸ provide the argument logging_server on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Location of the private cloud or cluster. + + To set the location attribute: + ▸ provide the argument logging_server on the command line with a + fully specified name; + ▸ provide the argument --location on the command line; + ▸ set the property compute/zone. + + --private-cloud=PRIVATE_CLOUD + VMware Engine private cloud. + + To set the private-cloud attribute: + ▸ provide the argument logging_server on the command line with a + fully specified name; + ▸ provide the argument --private-cloud on the command line. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. The default is True. Enabled by default, use --no-async to + disable. + + --hostname=HOSTNAME + Fully-qualified domain name (FQDN) or IP Address of the logging server. + + --port=PORT + Port number at which the logging server receives logs. + + --protocol=PROTOCOL + Defines possible protocols used to send logs to a logging server. + PROTOCOL must be one of: UDP, TCP. + + --source-type=SOURCE_TYPE + The type of component that produces logs that will be forwarded to this + logging server. SOURCE_TYPE must be one of: VCSA, ESXI. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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/vmware/private-clouds/management-dns-zone-bindings/create b/gcloud/vmware/private-clouds/management-dns-zone-bindings/create new file mode 100644 index 000000000..4a60ec8f8 --- /dev/null +++ b/gcloud/vmware/private-clouds/management-dns-zone-bindings/create @@ -0,0 +1,104 @@ +NAME + gcloud vmware private-clouds management-dns-zone-bindings create - create a + management DNS zone binding + +SYNOPSIS + gcloud vmware private-clouds management-dns-zone-bindings create + (MANAGEMENT_DNS_ZONE_BINDING + : --location=LOCATION --private-cloud=PRIVATE_CLOUD) + (--vmware-engine-network=VMWARE_ENGINE_NETWORK + | --vpc-network=VPC_NETWORK) [--async] [--description=DESCRIPTION] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Create a management DNS zone binding. + +EXAMPLES + To create a management DNS zone binding called my-mgmt-dns-zone-binding + that corresponds to the vmware engine network sample-vmware-engine-network + in private cloud my-private-cloud, in location us-east2-b, run: + + $ gcloud vmware private-clouds management-dns-zone-bindings create \ + my-mgmt-dns-zone-binding --project=my-project \ + --private-cloud=my-private-cloud --location=us-east2-b \ + --vmware-engine-network=sample-vmware-engine-network + + Or: + + $ gcloud vmware private-clouds management-dns-zone-bindings create \ + my-mgmt-dns-zone-binding --private-cloud=my-private-cloud \ + --vmware-engine-network=sample-vmware-engine-network + + In the second example, the project and location are taken from gcloud + properties core/project and compute/zone respectively. + +POSITIONAL ARGUMENTS + Management DNS zone binding resource - management_dns_zone_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 management_dns_zone_binding 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. + + MANAGEMENT_DNS_ZONE_BINDING + ID of the management DNS zone binding or fully qualified identifier + for the management DNS zone binding. + + To set the management-dns-zone-binding attribute: + ▸ provide the argument management_dns_zone_binding on the command + line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Location of the private cloud or cluster. + + To set the location attribute: + ▸ provide the argument management_dns_zone_binding on the command + line with a fully specified name; + ▸ provide the argument --location on the command line; + ▸ set the property compute/zone. + + --private-cloud=PRIVATE_CLOUD + VMware Engine private cloud. + + To set the private-cloud attribute: + ▸ provide the argument management_dns_zone_binding on the command + line with a fully specified name; + ▸ provide the argument --private-cloud on the command line. + +REQUIRED FLAGS + Exactly one of these must be specified: + + --vmware-engine-network=VMWARE_ENGINE_NETWORK + Resource name of VMware Engine network to bind to the management DNS + zone of the private cloud. + + --vpc-network=VPC_NETWORK + Resource name of the Google Cloud VPC network to bind to the + management DNS zone of the private cloud. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. The default is True. Enabled by default, use --no-async to + disable. + + --description=DESCRIPTION + Text describing the binding resource that represents the network + getting bound to the management DNS 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. diff --git a/gcloud/vmware/private-clouds/management-dns-zone-bindings/delete b/gcloud/vmware/private-clouds/management-dns-zone-bindings/delete new file mode 100644 index 000000000..4cc320bbe --- /dev/null +++ b/gcloud/vmware/private-clouds/management-dns-zone-bindings/delete @@ -0,0 +1,84 @@ +NAME + gcloud vmware private-clouds management-dns-zone-bindings delete - delete a + management DNS zone binding + +SYNOPSIS + gcloud vmware private-clouds management-dns-zone-bindings delete + (MANAGEMENT_DNS_ZONE_BINDING + : --location=LOCATION --private-cloud=PRIVATE_CLOUD) [--async] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Delete a management DNS zone binding. + +EXAMPLES + To delete a management DNS zone binding called my-mgmt-dns-zone-binding in + private cloud my-private-cloud, in location us-east2-b, run: + + $ gcloud vmware private-clouds management-dns-zone-bindings delete \ + my-mgmt-dns-zone-binding --project=my-project \ + --private-cloud=my-private-cloud --location=us-east2-b + + Or: + + $ gcloud vmware private-clouds management-dns-zone-bindings delete \ + my-mgmt-dns-zone-binding --private-cloud=my-private-cloud + + In the second example, the project and location are taken from gcloud + properties core/project and compute/zone respectively. + +POSITIONAL ARGUMENTS + Management DNS zone binding resource - management_dns_zone_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 management_dns_zone_binding 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. + + MANAGEMENT_DNS_ZONE_BINDING + ID of the management DNS zone binding or fully qualified identifier + for the management DNS zone binding. + + To set the management-dns-zone-binding attribute: + ▸ provide the argument management_dns_zone_binding on the command + line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Location of the private cloud or cluster. + + To set the location attribute: + ▸ provide the argument management_dns_zone_binding on the command + line with a fully specified name; + ▸ provide the argument --location on the command line; + ▸ set the property compute/zone. + + --private-cloud=PRIVATE_CLOUD + VMware Engine private cloud. + + To set the private-cloud attribute: + ▸ provide the argument management_dns_zone_binding on the command + line with a fully specified name; + ▸ provide the argument --private-cloud on the command line. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. The default is True. Enabled by default, use --no-async to + disable. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. diff --git a/gcloud/vmware/private-clouds/management-dns-zone-bindings/describe b/gcloud/vmware/private-clouds/management-dns-zone-bindings/describe new file mode 100644 index 000000000..ac59697bd --- /dev/null +++ b/gcloud/vmware/private-clouds/management-dns-zone-bindings/describe @@ -0,0 +1,81 @@ +NAME + gcloud vmware private-clouds management-dns-zone-bindings describe - + describe a management DNS zone binding + +SYNOPSIS + gcloud vmware private-clouds management-dns-zone-bindings describe + (MANAGEMENT_DNS_ZONE_BINDING + : --location=LOCATION --private-cloud=PRIVATE_CLOUD) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Describe a management DNS zone binding. + +EXAMPLES + To get a description of a management DNS zone binding called + my-mgmt-dns-zone-binding that corresponds to the vmware engine network + sample-vmware-engine-network in private cloud my-private-cloud, in location + us-east2-b, run: + + $ gcloud vmware private-clouds management-dns-zone-bindings \ + describe my-mgmt-dns-zone-binding --project=my-project \ + --private-cloud=my-private-cloud --location=us-east2-b + + Or: + + $ gcloud vmware private-clouds management-dns-zone-bindings \ + describe my-mgmt-dns-zone-binding \ + --private-cloud=my-private-cloud + + In the second example, the project and location are taken from gcloud + properties core/project and compute/zone respectively. + +POSITIONAL ARGUMENTS + Management DNS zone binding resource - management_dns_zone_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 management_dns_zone_binding 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. + + MANAGEMENT_DNS_ZONE_BINDING + ID of the management DNS zone binding or fully qualified identifier + for the management DNS zone binding. + + To set the management-dns-zone-binding attribute: + ▸ provide the argument management_dns_zone_binding on the command + line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Location of the private cloud or cluster. + + To set the location attribute: + ▸ provide the argument management_dns_zone_binding on the command + line with a fully specified name; + ▸ provide the argument --location on the command line; + ▸ set the property compute/zone. + + --private-cloud=PRIVATE_CLOUD + VMware Engine private cloud. + + To set the private-cloud attribute: + ▸ provide the argument management_dns_zone_binding on the command + line with a fully specified name; + ▸ provide the argument --private-cloud on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. diff --git a/gcloud/vmware/private-clouds/management-dns-zone-bindings/help b/gcloud/vmware/private-clouds/management-dns-zone-bindings/help new file mode 100644 index 000000000..0fbbab541 --- /dev/null +++ b/gcloud/vmware/private-clouds/management-dns-zone-bindings/help @@ -0,0 +1,36 @@ +NAME + gcloud vmware private-clouds management-dns-zone-bindings - manage + Management DNS zone bindings in Google Cloud VMware Engine + +SYNOPSIS + gcloud vmware private-clouds management-dns-zone-bindings COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Manage Management DNS zone bindings in Google Cloud VMware Engine. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + create + Create a management DNS zone binding. + + delete + Delete a management DNS zone binding. + + describe + Describe a management DNS zone binding. + + list + List management DNS zone bindings in a VMware Engine private cloud. + + repair + Repair a management DNS zone binding. + + update + Update a management DNS zone binding. diff --git a/gcloud/vmware/private-clouds/management-dns-zone-bindings/list b/gcloud/vmware/private-clouds/management-dns-zone-bindings/list new file mode 100644 index 000000000..a99d9ba88 --- /dev/null +++ b/gcloud/vmware/private-clouds/management-dns-zone-bindings/list @@ -0,0 +1,92 @@ +NAME + gcloud vmware private-clouds management-dns-zone-bindings list - list + management DNS zone bindings in a VMware Engine private cloud + +SYNOPSIS + gcloud vmware private-clouds management-dns-zone-bindings list + (--private-cloud=PRIVATE_CLOUD : --location=LOCATION) + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + List management DNS zone bindings in a VMware Engine private cloud. + +EXAMPLES + To list management DNS zone bindings in the my-private-cloud private cloud, + run: + + $ gcloud vmware private-clouds management-dns-zone-bindings list \ + --private-cloud=my-private-cloud --project=my-project \ + --location=us-east2-b + +REQUIRED FLAGS + Private cloud resource - private_cloud. The arguments in this group can be + used to specify the attributes of this resource. (NOTE) Some attributes + are not given arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument --private-cloud on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + --private-cloud=PRIVATE_CLOUD + ID of the private cloud or fully qualified identifier for the private + cloud. + + To set the private-cloud attribute: + ▸ provide the argument --private-cloud on the command line. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + Location of the private cloud or cluster. + + To set the location attribute: + ▸ provide the argument --private-cloud on the command line with a + fully specified name; + ▸ provide the argument --location on the command line; + ▸ set the property compute/zone. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. diff --git a/gcloud/vmware/private-clouds/management-dns-zone-bindings/repair b/gcloud/vmware/private-clouds/management-dns-zone-bindings/repair new file mode 100644 index 000000000..d5180db88 --- /dev/null +++ b/gcloud/vmware/private-clouds/management-dns-zone-bindings/repair @@ -0,0 +1,85 @@ +NAME + gcloud vmware private-clouds management-dns-zone-bindings repair - repair a + management DNS zone binding + +SYNOPSIS + gcloud vmware private-clouds management-dns-zone-bindings repair + (MANAGEMENT_DNS_ZONE_BINDING + : --location=LOCATION --private-cloud=PRIVATE_CLOUD) [--async] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Repair a management DNS zone binding. + +EXAMPLES + To repair a management DNS zone binding called my-mgmt-dns-zone-binding in + private cloud my-private-cloud, in project my-project, in location + us-east2-b, run: + + $ gcloud vmware private-clouds management-dns-zone-bindings repair \ + my-mgmt-dns-zone-binding --project=my-project \ + --private-cloud=my-private-cloud --location=us-east2-b + + Or: + + $ gcloud vmware private-clouds management-dns-zone-bindings repair \ + my-mgmt-dns-zone-binding --private-cloud=my-private-cloud + + In the second example, the project and location are taken from gcloud + properties core/project and compute/zone respectively. + +POSITIONAL ARGUMENTS + Management DNS zone binding resource - management_dns_zone_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 management_dns_zone_binding 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. + + MANAGEMENT_DNS_ZONE_BINDING + ID of the management DNS zone binding or fully qualified identifier + for the management DNS zone binding. + + To set the management-dns-zone-binding attribute: + ▸ provide the argument management_dns_zone_binding on the command + line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Location of the private cloud or cluster. + + To set the location attribute: + ▸ provide the argument management_dns_zone_binding on the command + line with a fully specified name; + ▸ provide the argument --location on the command line; + ▸ set the property compute/zone. + + --private-cloud=PRIVATE_CLOUD + VMware Engine private cloud. + + To set the private-cloud attribute: + ▸ provide the argument management_dns_zone_binding on the command + line with a fully specified name; + ▸ provide the argument --private-cloud on the command line. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. The default is True. Enabled by default, use --no-async to + disable. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. diff --git a/gcloud/vmware/private-clouds/management-dns-zone-bindings/update b/gcloud/vmware/private-clouds/management-dns-zone-bindings/update new file mode 100644 index 000000000..082481a7a --- /dev/null +++ b/gcloud/vmware/private-clouds/management-dns-zone-bindings/update @@ -0,0 +1,91 @@ +NAME + gcloud vmware private-clouds management-dns-zone-bindings update - update a + management DNS zone binding + +SYNOPSIS + gcloud vmware private-clouds management-dns-zone-bindings update + (MANAGEMENT_DNS_ZONE_BINDING + : --location=LOCATION --private-cloud=PRIVATE_CLOUD) + --description=DESCRIPTION [--async] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Update a management DNS zone binding. + +EXAMPLES + To update a management DNS zone binding called my-mgmt-dns-zone-binding in + private cloud my-private-cloud and zone us-west2-a with description New + Description, run: + + $ gcloud vmware private-clouds management-dns-zone-bindings update \ + my-mgmt-dns-zone-binding --project=my-project \ + --private-cloud=my-private-cloud --location=us-east2-b \ + --description="New Description" + + Or: + + $ gcloud vmware private-clouds management-dns-zone-bindings update \ + my-mgmt-dns-zone-binding --private-cloud=my-private-cloud \ + --description="New Description" + + In the second example, the project and location are taken from gcloud properties `core/project` and compute/zone. + +POSITIONAL ARGUMENTS + Management DNS zone binding resource - management_dns_zone_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 management_dns_zone_binding 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. + + MANAGEMENT_DNS_ZONE_BINDING + ID of the management DNS zone binding or fully qualified identifier + for the management DNS zone binding. + + To set the management-dns-zone-binding attribute: + ▸ provide the argument management_dns_zone_binding on the command + line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Location of the private cloud or cluster. + + To set the location attribute: + ▸ provide the argument management_dns_zone_binding on the command + line with a fully specified name; + ▸ provide the argument --location on the command line; + ▸ set the property compute/zone. + + --private-cloud=PRIVATE_CLOUD + VMware Engine private cloud. + + To set the private-cloud attribute: + ▸ provide the argument management_dns_zone_binding on the command + line with a fully specified name; + ▸ provide the argument --private-cloud on the command line. + +REQUIRED FLAGS + --description=DESCRIPTION + Text describing the binding resource that represents the network + getting bound to the management DNS zone. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. The default is True. Enabled by default, use --no-async to + disable. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details.