diff --git a/gcloud/_version b/gcloud/_version index 6f7c526e2..88b6b58f1 100644 --- a/gcloud/_version +++ b/gcloud/_version @@ -1,8 +1,8 @@ -Google Cloud SDK 448.0.0 -alpha 2023.09.22 -beta 2023.09.22 +Google Cloud SDK 449.0.0 +alpha 2023.10.02 +beta 2023.10.02 bq 2.0.98 bundled-python3-unix 3.9.16 -core 2023.09.22 +core 2023.10.02 gcloud-crc32c 1.0.0 -gsutil 5.25 +gsutil 5.26 diff --git a/gcloud/ai/index-endpoints/deploy-index b/gcloud/ai/index-endpoints/deploy-index index c19031a6b..9dfd72efa 100644 --- a/gcloud/ai/index-endpoints/deploy-index +++ b/gcloud/ai/index-endpoints/deploy-index @@ -6,20 +6,23 @@ SYNOPSIS gcloud ai index-endpoints deploy-index (INDEX_ENDPOINT : --region=REGION) --deployed-index-id=DEPLOYED_INDEX_ID --display-name=DISPLAY_NAME --index=INDEX [--max-replica-count=MAX_REPLICA_COUNT] - [--min-replica-count=MIN_REPLICA_COUNT] [GCLOUD_WIDE_FLAG ...] + [--min-replica-count=MIN_REPLICA_COUNT] + [--reserved-ip-ranges=[RESERVED_IP_RANGES,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION Deploy an index to a Vertex AI index endpoint. EXAMPLES To deploy index 345 to an index endpoint 456 with 2 min replica count and - 10 max replica count under project example in region us-central1, run: + 10 max replica count under project example in region us-central1, within + reserved ip ranges vertex-ai-ip-ranges-1 and vertex-ai-ip-ranges-2 run: $ gcloud ai index-endpoints deploy-index 456 --project=example \ --region=us-central1 --index=345 \ --deployed-index-id=deployed-index-345 \ --display-name=deployed-index-345 --min-replica-count=2 \ - --max-replica-count=10 + --max-replica-count=10 \ + --reserved-ip-ranges=vertex-ai-ip-ranges-1,vertex-ai-ip-ranges-2 POSITIONAL ARGUMENTS Index endpoint resource - The index endpoint to deploy an index. The @@ -74,6 +77,9 @@ OPTIONAL FLAGS Minimum number of machine replicas the deployed index will be always deployed on. If specified, the value must be equal to or larger than 1. + --reserved-ip-ranges=[RESERVED_IP_RANGES,...] + List of reserved IP ranges deployed index will be deployed to. + 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/ai/index-endpoints/mutate-deployed-index b/gcloud/ai/index-endpoints/mutate-deployed-index index 8df448b71..e69d47197 100644 --- a/gcloud/ai/index-endpoints/mutate-deployed-index +++ b/gcloud/ai/index-endpoints/mutate-deployed-index @@ -7,20 +7,23 @@ SYNOPSIS (INDEX_ENDPOINT : --region=REGION) --deployed-index-id=DEPLOYED_INDEX_ID [--max-replica-count=MAX_REPLICA_COUNT] - [--min-replica-count=MIN_REPLICA_COUNT] [GCLOUD_WIDE_FLAG ...] + [--min-replica-count=MIN_REPLICA_COUNT] + [--reserved-ip-ranges=[RESERVED_IP_RANGES,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION Mutate an existing deployed index from a Vertex AI index endpoint. EXAMPLES - To mutated an deployed index deployed-index-123 from an index endpoint 456 + To mutated a deployed index deployed-index-123 from an index endpoint 456 with 2 min replica count and 10 max replica count under project example in - region us-central1, run: + region us-central1, within vertex-ai-ip-ranges-1 and vertex-ai-ip-ranges-2 + run: $ gcloud ai index-endpoints mutate-deployed-index 456 \ --project=example --region=us-central1 \ --deployed-index-id=deployed-index-123 --min-replica-count=2 \ - --max-replica-count=10 + --max-replica-count=10 \ + --reserved-ip-ranges=vertex-ai-ip-ranges-1,vertex-ai-ip-ranges-2 POSITIONAL ARGUMENTS Index endpoint resource - The index endpoint ID of the index endpoint.. @@ -69,6 +72,9 @@ OPTIONAL FLAGS Minimum number of machine replicas the deployed index will be always deployed on. If specified, the value must be equal to or larger than 1. + --reserved-ip-ranges=[RESERVED_IP_RANGES,...] + List of reserved IP ranges deployed index will be deployed to. + 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/ai/index-endpoints/deploy-index b/gcloud/alpha/ai/index-endpoints/deploy-index index db4e0129e..9357e1650 100644 --- a/gcloud/alpha/ai/index-endpoints/deploy-index +++ b/gcloud/alpha/ai/index-endpoints/deploy-index @@ -7,20 +7,23 @@ SYNOPSIS (INDEX_ENDPOINT : --region=REGION) --deployed-index-id=DEPLOYED_INDEX_ID --display-name=DISPLAY_NAME --index=INDEX [--max-replica-count=MAX_REPLICA_COUNT] - [--min-replica-count=MIN_REPLICA_COUNT] [GCLOUD_WIDE_FLAG ...] + [--min-replica-count=MIN_REPLICA_COUNT] + [--reserved-ip-ranges=[RESERVED_IP_RANGES,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Deploy an index to a Vertex AI index endpoint. EXAMPLES To deploy index 345 to an index endpoint 456 with 2 min replica count and - 10 max replica count under project example in region us-central1, run: + 10 max replica count under project example in region us-central1, within + reserved ip ranges vertex-ai-ip-ranges-1 and vertex-ai-ip-ranges-2 run: $ gcloud alpha ai index-endpoints deploy-index 456 \ --project=example --region=us-central1 --index=345 \ --deployed-index-id=deployed-index-345 \ --display-name=deployed-index-345 --min-replica-count=2 \ - --max-replica-count=10 + --max-replica-count=10 \ + --reserved-ip-ranges=vertex-ai-ip-ranges-1,vertex-ai-ip-ranges-2 POSITIONAL ARGUMENTS Index endpoint resource - The index endpoint to deploy an index. The @@ -75,6 +78,9 @@ OPTIONAL FLAGS Minimum number of machine replicas the deployed index will be always deployed on. If specified, the value must be equal to or larger than 1. + --reserved-ip-ranges=[RESERVED_IP_RANGES,...] + List of reserved IP ranges deployed index will be deployed to. + 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/ai/index-endpoints/mutate-deployed-index b/gcloud/alpha/ai/index-endpoints/mutate-deployed-index index ea406d36d..92e154a65 100644 --- a/gcloud/alpha/ai/index-endpoints/mutate-deployed-index +++ b/gcloud/alpha/ai/index-endpoints/mutate-deployed-index @@ -7,20 +7,23 @@ SYNOPSIS (INDEX_ENDPOINT : --region=REGION) --deployed-index-id=DEPLOYED_INDEX_ID [--max-replica-count=MAX_REPLICA_COUNT] - [--min-replica-count=MIN_REPLICA_COUNT] [GCLOUD_WIDE_FLAG ...] + [--min-replica-count=MIN_REPLICA_COUNT] + [--reserved-ip-ranges=[RESERVED_IP_RANGES,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Mutate an existing deployed index from a Vertex AI index endpoint. EXAMPLES - To mutated an deployed index deployed-index-123 from an index endpoint 456 + To mutated a deployed index deployed-index-123 from an index endpoint 456 with 2 min replica count and 10 max replica count under project example in - region us-central1, run: + region us-central1, within vertex-ai-ip-ranges-1 and vertex-ai-ip-ranges-2 + run: $ gcloud alpha ai index-endpoints mutate-deployed-index 456 \ --project=example --region=us-central1 \ --deployed-index-id=deployed-index-123 --min-replica-count=2 \ - --max-replica-count=10 + --max-replica-count=10 \ + --reserved-ip-ranges=vertex-ai-ip-ranges-1,vertex-ai-ip-ranges-2 POSITIONAL ARGUMENTS Index endpoint resource - The index endpoint ID of the index endpoint.. @@ -69,6 +72,9 @@ OPTIONAL FLAGS Minimum number of machine replicas the deployed index will be always deployed on. If specified, the value must be equal to or larger than 1. + --reserved-ip-ranges=[RESERVED_IP_RANGES,...] + List of reserved IP ranges deployed index will be deployed to. + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/alpha/compute/disks/create b/gcloud/alpha/compute/disks/create index 28f9118db..828cd2220 100644 --- a/gcloud/alpha/compute/disks/create +++ b/gcloud/alpha/compute/disks/create @@ -95,8 +95,8 @@ FLAGS https://cloud.google.com/compute/docs/images/create-delete-deprecate-private-images#guest-os-features. GUEST_OS_FEATURE must be one of: BARE_METAL_LINUX_COMPATIBLE, GVNIC, IDPF, MULTI_IP_SUBNET, SEV_CAPABLE, SEV_LIVE_MIGRATABLE, - SEV_SNP_CAPABLE, TDX_CAPABLE, UEFI_COMPATIBLE, VIRTIO_SCSI_MULTIQUEUE, - WINDOWS. + SEV_LIVE_MIGRATABLE_V2, SEV_SNP_CAPABLE, TDX_CAPABLE, UEFI_COMPATIBLE, + VIRTIO_SCSI_MULTIQUEUE, WINDOWS. --interface=INTERFACE Specifies the disk interface to use for attaching this disk. Valid diff --git a/gcloud/alpha/compute/images/create b/gcloud/alpha/compute/images/create index bfd06b592..e4ae2cc9e 100644 --- a/gcloud/alpha/compute/images/create +++ b/gcloud/alpha/compute/images/create @@ -153,8 +153,8 @@ OPTIONAL FLAGS https://cloud.google.com/compute/docs/images/create-delete-deprecate-private-images#guest-os-features. GUEST_OS_FEATURE must be one of: BARE_METAL_LINUX_COMPATIBLE, GVNIC, IDPF, MULTI_IP_SUBNET, SEV_CAPABLE, SEV_LIVE_MIGRATABLE, - SEV_SNP_CAPABLE, TDX_CAPABLE, UEFI_COMPATIBLE, VIRTIO_SCSI_MULTIQUEUE, - WINDOWS. + SEV_LIVE_MIGRATABLE_V2, SEV_SNP_CAPABLE, TDX_CAPABLE, UEFI_COMPATIBLE, + VIRTIO_SCSI_MULTIQUEUE, WINDOWS. --key-exchange-key-file=[KEK_VALUE,...] Comma-separated list of file paths that point to X.509 certificates in diff --git a/gcloud/alpha/compute/instance-templates/create b/gcloud/alpha/compute/instance-templates/create index 4ecb99c84..86e398dbb 100644 --- a/gcloud/alpha/compute/instance-templates/create +++ b/gcloud/alpha/compute/instance-templates/create @@ -7,6 +7,7 @@ SYNOPSIS [--accelerator=[count=COUNT],[type=TYPE]] [--no-boot-disk-auto-delete] [--boot-disk-device-name=BOOT_DISK_DEVICE_NAME] [--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] @@ -126,6 +127,10 @@ FLAGS of I/O operations per second that the disk can handle. Value must be between 10,000 and 120,000. + --boot-disk-provisioned-throughput=BOOT_DISK_PROVISIONED_THROUGHPUT + Indicates how much throughput to provision for the disk. This sets the + number of throughput mb per second that the disk can handle. + --boot-disk-size=BOOT_DISK_SIZE The size of the boot disk. This option can only be specified if a new boot disk is being created (as opposed to mounting an existing diff --git a/gcloud/alpha/compute/instance-templates/create-with-container b/gcloud/alpha/compute/instance-templates/create-with-container index 4511087ed..bfd56470d 100644 --- a/gcloud/alpha/compute/instance-templates/create-with-container +++ b/gcloud/alpha/compute/instance-templates/create-with-container @@ -8,6 +8,7 @@ SYNOPSIS [--accelerator=[count=COUNT],[type=TYPE]] [--no-boot-disk-auto-delete] [--boot-disk-device-name=BOOT_DISK_DEVICE_NAME] [--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] [--container-arg=CONTAINER_ARG] [--container-command=CONTAINER_COMMAND] @@ -117,6 +118,10 @@ FLAGS of I/O operations per second that the disk can handle. Value must be between 10,000 and 120,000. + --boot-disk-provisioned-throughput=BOOT_DISK_PROVISIONED_THROUGHPUT + Indicates how much throughput to provision for the disk. This sets the + number of throughput mb per second that the disk can handle. + --boot-disk-size=BOOT_DISK_SIZE The size of the boot disk. This option can only be specified if a new boot disk is being created (as opposed to mounting an existing diff --git a/gcloud/alpha/compute/instances/bulk/create b/gcloud/alpha/compute/instances/bulk/create index 99cdfb63b..55d122763 100644 --- a/gcloud/alpha/compute/instances/bulk/create +++ b/gcloud/alpha/compute/instances/bulk/create @@ -10,6 +10,7 @@ SYNOPSIS [--no-boot-disk-auto-delete] [--boot-disk-device-name=BOOT_DISK_DEVICE_NAME] [--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] @@ -166,6 +167,10 @@ OPTIONAL FLAGS of I/O operations per second that the disk can handle. Value must be between 10,000 and 120,000. + --boot-disk-provisioned-throughput=BOOT_DISK_PROVISIONED_THROUGHPUT + Indicates how much throughput to provision for the disk. This sets the + number of throughput mb per second that the disk can handle. + --boot-disk-size=BOOT_DISK_SIZE The size of the boot disk. This option can only be specified if a new boot disk is being created (as opposed to mounting an existing diff --git a/gcloud/alpha/compute/instances/create b/gcloud/alpha/compute/instances/create index 1eee49eec..fc771b53c 100644 --- a/gcloud/alpha/compute/instances/create +++ b/gcloud/alpha/compute/instances/create @@ -8,6 +8,7 @@ SYNOPSIS [--no-boot-disk-auto-delete] [--boot-disk-device-name=BOOT_DISK_DEVICE_NAME] [--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] @@ -181,6 +182,10 @@ FLAGS of I/O operations per second that the disk can handle. Value must be between 10,000 and 120,000. + --boot-disk-provisioned-throughput=BOOT_DISK_PROVISIONED_THROUGHPUT + Indicates how much throughput to provision for the disk. This sets the + number of throughput mb per second that the disk can handle. + --boot-disk-size=BOOT_DISK_SIZE The size of the boot disk. This option can only be specified if a new boot disk is being created (as opposed to mounting an existing diff --git a/gcloud/alpha/compute/instances/create-with-container b/gcloud/alpha/compute/instances/create-with-container index dbf99bd40..67791e770 100644 --- a/gcloud/alpha/compute/instances/create-with-container +++ b/gcloud/alpha/compute/instances/create-with-container @@ -8,6 +8,7 @@ SYNOPSIS [--no-boot-disk-auto-delete] [--boot-disk-device-name=BOOT_DISK_DEVICE_NAME] [--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] @@ -128,6 +129,10 @@ FLAGS of I/O operations per second that the disk can handle. Value must be between 10,000 and 120,000. + --boot-disk-provisioned-throughput=BOOT_DISK_PROVISIONED_THROUGHPUT + Indicates how much throughput to provision for the disk. This sets the + number of throughput mb per second that the disk can handle. + --boot-disk-size=BOOT_DISK_SIZE The size of the boot disk. This option can only be specified if a new boot disk is being created (as opposed to mounting an existing diff --git a/gcloud/alpha/compute/public-delegated-prefixes/create b/gcloud/alpha/compute/public-delegated-prefixes/create index 81e809757..19110f2b2 100644 --- a/gcloud/alpha/compute/public-delegated-prefixes/create +++ b/gcloud/alpha/compute/public-delegated-prefixes/create @@ -3,9 +3,11 @@ NAME Engine public delegated prefix SYNOPSIS - gcloud alpha compute public-delegated-prefixes create NAME - --public-advertised-prefix=PUBLIC_ADVERTISED_PREFIX --range=RANGE - [--description=DESCRIPTION] [--enable-live-migration] + gcloud alpha compute public-delegated-prefixes create NAME --range=RANGE + (--public-advertised-prefix=PUBLIC_ADVERTISED_PREFIX + | --public-delegated-prefix=PUBLIC_DELEGATED_PREFIX) + [--allocatable-prefix-length=ALLOCATABLE_PREFIX_LENGTH] + [--description=DESCRIPTION] [--enable-live-migration] [--mode=MODE] [--global | --region=REGION] [GCLOUD_WIDE_FLAG ...] EXAMPLES @@ -20,21 +22,34 @@ POSITIONAL ARGUMENTS Name of the public delegated prefix to operate on. REQUIRED FLAGS - --public-advertised-prefix=PUBLIC_ADVERTISED_PREFIX - Public advertised prefix that this delegated prefix is created from. - --range=RANGE IPv4 range from this public delegated prefix that should be delegated, in CIDR format. It must be smaller than parent public advertised prefix range. + Exactly one of these must be specified: + + --public-advertised-prefix=PUBLIC_ADVERTISED_PREFIX + Public advertised prefix that this delegated prefix is created from. + + --public-delegated-prefix=PUBLIC_DELEGATED_PREFIX + Regional Public delegated prefix that this delegated prefix is + created from. + OPTIONAL FLAGS + --allocatable-prefix-length=ALLOCATABLE_PREFIX_LENGTH + The allocatable prefix length supported by this PDP. + --description=DESCRIPTION Description of this public delegated prefix. --enable-live-migration Specify if this public delegated prefix is meant to be live migrated. + --mode=MODE + Specifies the mode of this IPv6 PDP. MODE must be one of: + EXTERNAL_IPV6_FORWARDING_RULE_CREATION, DELEGATION. + At most one of these can be specified: --global diff --git a/gcloud/alpha/compute/queued-resources/create b/gcloud/alpha/compute/queued-resources/create index 722562866..a3a838874 100644 --- a/gcloud/alpha/compute/queued-resources/create +++ b/gcloud/alpha/compute/queued-resources/create @@ -11,6 +11,7 @@ SYNOPSIS [--no-boot-disk-auto-delete] [--boot-disk-device-name=BOOT_DISK_DEVICE_NAME] [--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] @@ -150,6 +151,10 @@ OPTIONAL FLAGS of I/O operations per second that the disk can handle. Value must be between 10,000 and 120,000. + --boot-disk-provisioned-throughput=BOOT_DISK_PROVISIONED_THROUGHPUT + Indicates how much throughput to provision for the disk. This sets the + number of throughput mb per second that the disk can handle. + --boot-disk-size=BOOT_DISK_SIZE The size of the boot disk. This option can only be specified if a new boot disk is being created (as opposed to mounting an existing diff --git a/gcloud/alpha/compute/tpus/queued-resources/create b/gcloud/alpha/compute/tpus/queued-resources/create index 481c2484b..8110f93d7 100644 --- a/gcloud/alpha/compute/tpus/queued-resources/create +++ b/gcloud/alpha/compute/tpus/queued-resources/create @@ -8,10 +8,10 @@ SYNOPSIS (--accelerator-type=ACCELERATOR_TYPE | --topology=TOPOLOGY --type=TYPE) (--node-id=NODE_ID | [--node-count=NODE_COUNT : --node-prefix=NODE_PREFIX]) [--async] - [--best-effort] [--data-disk=[mode=MODE],[source=SOURCE]] - [--description=DESCRIPTION] [--guaranteed] [--internal-ips] - [--labels=[KEY=VALUE,...]] [--metadata=[KEY=VALUE,...]] - [--metadata-from-file=[KEY=VALUE,...]] + [--autocheckpoint-enabled] [--best-effort] + [--data-disk=[mode=MODE],[source=SOURCE]] [--description=DESCRIPTION] + [--guaranteed] [--internal-ips] [--labels=[KEY=VALUE,...]] + [--metadata=[KEY=VALUE,...]] [--metadata-from-file=[KEY=VALUE,...]] [--network=NETWORK; default="default"] [--range=RANGE] [--reservation-host-folder=RESERVATION_HOST_FOLDER] [--reservation-host-organization=RESERVATION_HOST_ORGANIZATION] @@ -141,6 +141,10 @@ OPTIONAL FLAGS Return immediately, without waiting for the operation in progress to complete. + --autocheckpoint-enabled + Specifies that the TPU node(s) are created with the Autocheckpoint + feature enabled. + --best-effort If provided, the Node requested here may be scheduled at the 'best effort' tier. diff --git a/gcloud/alpha/compute/tpus/tpu-vm/create b/gcloud/alpha/compute/tpus/tpu-vm/create index c17b97330..115aff3e3 100644 --- a/gcloud/alpha/compute/tpus/tpu-vm/create +++ b/gcloud/alpha/compute/tpus/tpu-vm/create @@ -3,9 +3,9 @@ NAME SYNOPSIS gcloud alpha compute tpus tpu-vm create (TPU : --zone=ZONE) - --version=VERSION [--async] [--boot-disk=[KEY=VALUE,...]] - [--data-disk=[mode=MODE],[source=SOURCE]] [--description=DESCRIPTION] - [--internal-ips] [--labels=[KEY=VALUE,...]] + --version=VERSION [--async] [--autocheckpoint-enabled] + [--boot-disk=[KEY=VALUE,...]] [--data-disk=[mode=MODE],[source=SOURCE]] + [--description=DESCRIPTION] [--internal-ips] [--labels=[KEY=VALUE,...]] [--metadata=[KEY=VALUE,...]] [--metadata-from-file=[KEY=VALUE,...]] [--network=NETWORK; default="default"] [--preemptible] [--range=RANGE] [--reserved] [--scopes=[SCOPES,...]] @@ -82,6 +82,10 @@ OPTIONAL FLAGS Return immediately, without waiting for the operation in progress to complete. + --autocheckpoint-enabled + If specified, the TPU node is created with the Autocheckpoint feature + enabled. + --boot-disk=[KEY=VALUE,...] Specifies if the boot disk should be created in confidential-compute mode. diff --git a/gcloud/alpha/container/clusters/create b/gcloud/alpha/container/clusters/create index 0ba90dcc2..f202d96bd 100644 --- a/gcloud/alpha/container/clusters/create +++ b/gcloud/alpha/container/clusters/create @@ -11,6 +11,7 @@ SYNOPSIS max-shared-clients-per-gpu=MAX_SHARED_CLIENTS_PER_GPU],...]] [--addons=[ADDON,...]] [--allow-route-overlap] [--async] [--autoprovisioning-network-tags=TAGS,[TAGS,...]] + [--autoprovisioning-resource-manager-tags=[KEY=VALUE,...]] [--autoscaling-profile=AUTOSCALING_PROFILE] [--boot-disk-kms-key=BOOT_DISK_KMS_KEY] [--cloud-run-config=[load-balancer-type=EXTERNAL,...]] @@ -61,9 +62,9 @@ SYNOPSIS [--placement-policy=PLACEMENT_POLICY] [--placement-type=PLACEMENT_TYPE] [--preemptible] [--private-endpoint-subnetwork=NAME] [--private-ipv6-google-access-type=PRIVATE_IPV6_GOOGLE_ACCESS_TYPE] - [--release-channel=CHANNEL] [--security-group=SECURITY_GROUP] - [--security-posture=SECURITY_POSTURE] [--services-ipv4-cidr=CIDR] - [--services-secondary-range-name=NAME] + [--release-channel=CHANNEL] [--resource-manager-tags=[KEY=VALUE,...]] + [--security-group=SECURITY_GROUP] [--security-posture=SECURITY_POSTURE] + [--services-ipv4-cidr=CIDR] [--services-secondary-range-name=NAME] [--shielded-integrity-monitoring] [--shielded-secure-boot] [--spot] [--stack-type=STACK_TYPE] [--subnetwork=SUBNETWORK] [--system-config-from-file=SYSTEM_CONFIG_FROM_FILE] @@ -227,6 +228,31 @@ FLAGS https://cloud.google.com/sdk/gcloud/reference/compute/firewall-rules/create for examples. + --autoprovisioning-resource-manager-tags=[KEY=VALUE,...] + Applies the specified comma-separated resource manager tags that has + the GCE_FIREWALL purpose to all nodes in the new Autopilot cluster or + all auto-provisioned nodes in the new Standard cluster. + + Examples: + + $ gcloud alpha container clusters create example-cluster \ + --autoprovisioning-resource-manager-tags=tagKeys/\ + 1234=tagValues/2345 + $ gcloud alpha container clusters create example-cluster \ + --autoprovisioning-resource-manager-tags=my-project/key1=value1 + $ gcloud alpha container clusters create example-cluster \ + --autoprovisioning-resource-manager-tags=12345/key1=value1,\ + 23456/key2=value2 + $ gcloud alpha container clusters create example-cluster \ + --autoprovisioning-resource-manager-tags= + + All nodes in an Autopilot cluster or all auto-provisioned nodes in a + Standard cluster, including nodes that are resized or re-created, will + have the specified tags on the corresponding Instance object in the + Compute Engine API. You can reference these tags in network firewall + policy rules. For instructions, see + https://cloud.google.com/firewall/docs/use-tags-for-firewalls. + --autoscaling-profile=AUTOSCALING_PROFILE Set autoscaling behaviour, choices are 'optimize-utilization' and 'balanced'. Default is 'balanced'. @@ -1057,6 +1083,28 @@ FLAGS Clusters subscribed to 'stable' receive versions that are known to be stable and reliable in production. + --resource-manager-tags=[KEY=VALUE,...] + Applies the specified comma-separated resource manager tags that has + the GCE_FIREWALL purpose to all nodes in the new default node pool(s) + of a new cluster. + + Examples: + + $ gcloud alpha container clusters create example-cluster \ + --resource-manager-tags=tagKeys/1234=tagValues/2345 + $ gcloud alpha container clusters create example-cluster \ + --resource-manager-tags=my-project/key1=value1 + $ gcloud alpha container clusters create example-cluster \ + --resource-manager-tags=12345/key1=value1,23456/key2=value2 + $ gcloud alpha container clusters create example-cluster \ + --resource-manager-tags= + + All nodes, including nodes that are resized or re-created, will have + the specified tags on the corresponding Instance object in the Compute + Engine API. You can reference these tags in network firewall policy + rules. For instructions, see + https://cloud.google.com/firewall/docs/use-tags-for-firewalls. + --security-group=SECURITY_GROUP The name of the RBAC security group for use with Google security groups in Kubernetes RBAC diff --git a/gcloud/alpha/container/clusters/create-auto b/gcloud/alpha/container/clusters/create-auto index dabb47c08..f6a79ebbe 100644 --- a/gcloud/alpha/container/clusters/create-auto +++ b/gcloud/alpha/container/clusters/create-auto @@ -5,6 +5,7 @@ NAME SYNOPSIS gcloud alpha container clusters create-auto NAME [--async] [--autoprovisioning-network-tags=TAGS,[TAGS,...]] + [--autoprovisioning-resource-manager-tags=[KEY=VALUE,...]] [--boot-disk-kms-key=BOOT_DISK_KMS_KEY] [--cluster-ipv4-cidr=CLUSTER_IPV4_CIDR] [--cluster-secondary-range-name=NAME] @@ -71,6 +72,31 @@ FLAGS https://cloud.google.com/sdk/gcloud/reference/compute/firewall-rules/create for examples. + --autoprovisioning-resource-manager-tags=[KEY=VALUE,...] + Applies the specified comma-separated resource manager tags that has + the GCE_FIREWALL purpose to all nodes in the new Autopilot cluster or + all auto-provisioned nodes in the new Standard cluster. + + Examples: + + $ gcloud alpha container clusters create-auto example-cluster \ + --autoprovisioning-resource-manager-tags=tagKeys/\ + 1234=tagValues/2345 + $ gcloud alpha container clusters create-auto example-cluster \ + --autoprovisioning-resource-manager-tags=my-project/key1=value1 + $ gcloud alpha container clusters create-auto example-cluster \ + --autoprovisioning-resource-manager-tags=12345/key1=value1,\ + 23456/key2=value2 + $ gcloud alpha container clusters create-auto example-cluster \ + --autoprovisioning-resource-manager-tags= + + All nodes in an Autopilot cluster or all auto-provisioned nodes in a + Standard cluster, including nodes that are resized or re-created, will + have the specified tags on the corresponding Instance object in the + Compute Engine API. You can reference these tags in network firewall + policy rules. For instructions, see + https://cloud.google.com/firewall/docs/use-tags-for-firewalls. + --boot-disk-kms-key=BOOT_DISK_KMS_KEY The Customer Managed Encryption Key used to encrypt the boot disk attached to each node in the node pool. This should be of the form diff --git a/gcloud/alpha/container/clusters/update b/gcloud/alpha/container/clusters/update index 11430fd61..acdd0a37a 100644 --- a/gcloud/alpha/container/clusters/update +++ b/gcloud/alpha/container/clusters/update @@ -5,6 +5,7 @@ NAME SYNOPSIS gcloud alpha container clusters update NAME (--autoprovisioning-network-tags=[TAGS,...] + | --autoprovisioning-resource-manager-tags=[KEY=VALUE,...] | --autoscaling-profile=AUTOSCALING_PROFILE | --clear-fleet-project | --complete-credential-rotation | --complete-ip-rotation | --database-encryption-key=DATABASE_ENCRYPTION_KEY @@ -128,6 +129,39 @@ REQUIRED FLAGS https://cloud.google.com/sdk/gcloud/reference/compute/firewall-rules/create for examples. + --autoprovisioning-resource-manager-tags=[KEY=VALUE,...] + For an Autopilot cluster, the specified comma-separated resource + manager tags that has the GCP_FIREWALL purpose replace the existing + tags on all nodes in the cluster. + + For a Standard cluster, the specified comma-separated resource + manager tags that has the GCE_FIREWALL purpose are applied to all + nodes in the new newly created auto-provisioned node pools. Existing + auto-provisioned node pools retain the tags that they had before the + update. To update tags on an existing auto-provisioned node pool, use + the node pool level flag '--resource-manager-tags'. + + Examples: + + $ gcloud alpha container clusters update example-cluster \ + --autoprovisioning-resource-manager-tags=tagKeys/\ + 1234=tagValues/2345 + $ gcloud alpha container clusters update example-cluster \ + --autoprovisioning-resource-manager-tags=my-project/key1=value1 + $ gcloud alpha container clusters update example-cluster \ + --autoprovisioning-resource-manager-tags=12345/key1=value1,\ + 23456/key2=value2 + $ gcloud alpha container clusters update example-cluster \ + --autoprovisioning-resource-manager-tags= + + All nodes in an Autopilot cluster or all newly created + auto-provisioned nodes in a Standard cluster, including nodes that + are resized or re-created, will have the specified tags on the + corresponding Instance object in the Compute Engine API. You can + reference these tags in network firewall policy rules. For + instructions, see + https://cloud.google.com/firewall/docs/use-tags-for-firewalls. + --autoscaling-profile=AUTOSCALING_PROFILE Set autoscaling behaviour, choices are 'optimize-utilization' and 'balanced'. Default is 'balanced'. diff --git a/gcloud/alpha/container/node-pools/create b/gcloud/alpha/container/node-pools/create index 149e86b43..25925cdbc 100644 --- a/gcloud/alpha/container/node-pools/create +++ b/gcloud/alpha/container/node-pools/create @@ -37,8 +37,9 @@ SYNOPSIS [--node-taints=[NODE_TAINT,...]] [--node-version=NODE_VERSION] [--num-nodes=NUM_NODES; default=3] [--placement-policy=PLACEMENT_POLICY] [--placement-type=PLACEMENT_TYPE] - [--preemptible] [--sandbox=[type=TYPE]] - [--shielded-integrity-monitoring] [--shielded-secure-boot] + [--preemptible] [--resource-manager-tags=[KEY=VALUE,...]] + [--sandbox=[type=TYPE]] [--shielded-integrity-monitoring] + [--shielded-secure-boot] [--sole-tenant-node-affinity-file=SOLE_TENANT_NODE_AFFINITY_FILE] [--spot] [--standard-rollout-policy=[batch-node-count=BATCH_NODE_COUNT, @@ -532,6 +533,27 @@ FLAGS https://cloud.google.com/kubernetes-engine/docs/preemptible-vm for more information on how to use Preemptible VMs with Kubernetes Engine. + --resource-manager-tags=[KEY=VALUE,...] + Applies the specified comma-separated resource manager tags that has + the GCE_FIREWALL purpose to all nodes in the new node pool. + + Examples: + + $ gcloud alpha container node-pools create example-node-pool \ + --resource-manager-tags=tagKeys/1234=tagValues/2345 + $ gcloud alpha container node-pools create example-node-pool \ + --resource-manager-tags=my-project/key1=value1 + $ gcloud alpha container node-pools create example-node-pool \ + --resource-manager-tags=12345/key1=value1,23456/key2=value2 + $ gcloud alpha container node-pools create example-node-pool \ + --resource-manager-tags= + + All nodes, including nodes that are resized or re-created, will have + the specified tags on the corresponding Instance object in the Compute + Engine API. You can reference these tags in network firewall policy + rules. For instructions, see + https://cloud.google.com/firewall/docs/use-tags-for-firewalls. + --sandbox=[type=TYPE] Enables the requested sandbox on all nodes in the node pool. diff --git a/gcloud/alpha/container/node-pools/update b/gcloud/alpha/container/node-pools/update index 6753a767d..31b8c3d02 100644 --- a/gcloud/alpha/container/node-pools/update +++ b/gcloud/alpha/container/node-pools/update @@ -10,6 +10,7 @@ SYNOPSIS | --network-performance-configs=[PROPERTY=VALUE,...] | --node-labels=[NODE_LABEL,...] | --node-locations=ZONE,[ZONE,...] | --node-taints=[NODE_TAINT,...] + | --resource-manager-tags=[KEY=VALUE,...] | --system-config-from-file=SYSTEM_CONFIG_FROM_FILE | --tags=[TAG,...] | --windows-os-version=WINDOWS_OS_VERSION | --workload-metadata=WORKLOAD_METADATA | --enable-blue-green-upgrade @@ -145,6 +146,29 @@ REQUIRED FLAGS To read more about node-taints, see https://cloud.google.com/kubernetes-engine/docs/node-taints. + --resource-manager-tags=[KEY=VALUE,...] + Replaces all the user specified resource manager tags on all nodes in + an existing standard or auto-provisioned node pool in a Standard + cluster with the given comma-separated resource manager tags that has + the GCE_FIREWALL purpose. + + Examples: + + $ gcloud alpha container node-pools update example-node-pool \ + --resource-manager-tags=tagKeys/1234=tagValues/2345 + $ gcloud alpha container node-pools update example-node-pool \ + --resource-manager-tags=my-project/key1=value1 + $ gcloud alpha container node-pools update example-node-pool \ + --resource-manager-tags=12345/key1=value1,23456/key2=value2 + $ gcloud alpha container node-pools update example-node-pool \ + --resource-manager-tags= + + All nodes, including nodes that are resized or re-created, will have + the specified tags on the corresponding Instance object in the + Compute Engine API. You can reference these tags in network firewall + policy rules. For instructions, see + https://cloud.google.com/firewall/docs/use-tags-for-firewalls. + --system-config-from-file=SYSTEM_CONFIG_FROM_FILE Path of the YAML/JSON file that contains the node configuration, including Linux kernel parameters (sysctls) and kubelet configs. diff --git a/gcloud/alpha/container/vmware/clusters/create b/gcloud/alpha/container/vmware/clusters/create index 44934ecbc..ca48138bb 100644 --- a/gcloud/alpha/container/vmware/clusters/create +++ b/gcloud/alpha/container/vmware/clusters/create @@ -177,7 +177,11 @@ REQUIRED FLAGS Use quote around the flag value to escape semicolon in the terminal. - Manual load balancer configuration + Manual load balancer configuration. + + With manual load balancing mode, DHCP is not supported. Specify static + IP addresses for cluster nodes instead. For more details, see + https://cloud.google.com/anthos/clusters/docs/on-prem/latest/how-to/manual-load-balance#setting_aside_node_ip_addresses. --control-plane-node-port=CONTROL_PLANE_NODE_PORT NodePort for control plane service. @@ -257,6 +261,10 @@ REQUIRED FLAGS --enable-dhcp Enable DHCP IP allocation for VMware user clusters. + While using DHCP, manual load balancing mode is not supported. + For more details, see + https://cloud.google.com/anthos/clusters/docs/on-prem/latest/how-to/manual-load-balance#setting_aside_node_ip_addresses. + Static IP configuration group At most one of these can be specified: diff --git a/gcloud/alpha/edge-cloud/container/clusters/get-credentials b/gcloud/alpha/edge-cloud/container/clusters/get-credentials index 434cfacd0..978def813 100644 --- a/gcloud/alpha/edge-cloud/container/clusters/get-credentials +++ b/gcloud/alpha/edge-cloud/container/clusters/get-credentials @@ -6,7 +6,7 @@ SYNOPSIS gcloud alpha edge-cloud container clusters get-credentials (CLUSTER : --location=LOCATION) [--auth-provider-cmd-path=AUTH_PROVIDER_CMD_PATH] - [GCLOUD_WIDE_FLAG ...] + [--offline-credential] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Fetch credentials for a running Edge Container cluster. This @@ -63,6 +63,10 @@ FLAGS Path to the gcloud executable for the auth provider field in kubeconfig. + --offline-credential + Once specified, an offline credential will be generated for the + cluster. + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/alpha/edge-cloud/container/get-server-config b/gcloud/alpha/edge-cloud/container/get-server-config index 9ef376873..591a94379 100644 --- a/gcloud/alpha/edge-cloud/container/get-server-config +++ b/gcloud/alpha/edge-cloud/container/get-server-config @@ -52,5 +52,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 edge-cloud container get-server-config diff --git a/gcloud/alpha/firestore/databases/delete b/gcloud/alpha/firestore/databases/delete index 40576eb33..be5453209 100644 --- a/gcloud/alpha/firestore/databases/delete +++ b/gcloud/alpha/firestore/databases/delete @@ -19,11 +19,6 @@ EXAMPLES $ gcloud alpha firestore databases delete --database=test --etag=etag - To delete a Firestore database test and allow missing. - - $ gcloud alpha firestore databases delete --database=test \ - --allow-missing - REQUIRED FLAGS --database=DATABASE The database to operate on. diff --git a/gcloud/alpha/functions/add-invoker-policy-binding b/gcloud/alpha/functions/add-invoker-policy-binding index 973d84aff..c4639e023 100644 --- a/gcloud/alpha/functions/add-invoker-policy-binding +++ b/gcloud/alpha/functions/add-invoker-policy-binding @@ -4,16 +4,17 @@ NAME SYNOPSIS gcloud alpha functions add-invoker-policy-binding (NAME : --region=REGION) - --member=PRINCIPAL [GCLOUD_WIDE_FLAG ...] + --member=PRINCIPAL [--gen2] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Adds the Cloud Run Invoker binding to the IAM policy of a Google - Cloud Function's underlying Cloud Run service. + (ALPHA) Adds an invoker role IAM policy binding that allows the specified + member to invoke the specified function. - This command applies to Cloud Functions (2nd gen) only. Cloud Functions - (2nd gen) currently requires the Cloud Run Invoke permission on the - underlying Cloud Run service to be able to call functions. This command - grants the given member permission to invoke the given 2nd gen function. + For Cloud Functions (1st gen), this adds the Cloud Functions Invoker + binding to the IAM policy of the specified function. + + For Cloud Functions (2nd gen), this adds the Cloud Run Invoker binding to + the IAM policy of the specified function's underlying Cloud Run service. EXAMPLES To add the invoker role policy binding for FUNCTION-1 for member MEMBER-1 @@ -70,6 +71,15 @@ REQUIRED FLAGS ◆ allAuthenticatedUsers - Special identifier that represents anyone who is authenticated with a Google account or a service account. +OPTIONAL FLAGS + --gen2 + If enabled, this command will use Cloud Functions (Second generation). + If disabled with --no-gen2, Cloud Functions (First generation) will be + used. If not specified, the value of this flag will be taken from the + functions/gen2 configuration property. If the functions/gen2 + configuration property is not set, defaults to looking up the given + function and using its generation. + 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/functions/remove-invoker-policy-binding b/gcloud/alpha/functions/remove-invoker-policy-binding index ec718d544..cac4a8fb0 100644 --- a/gcloud/alpha/functions/remove-invoker-policy-binding +++ b/gcloud/alpha/functions/remove-invoker-policy-binding @@ -4,16 +4,19 @@ NAME SYNOPSIS gcloud alpha functions remove-invoker-policy-binding - (NAME : --region=REGION) --member=PRINCIPAL [GCLOUD_WIDE_FLAG ...] + (NAME : --region=REGION) --member=PRINCIPAL [--gen2] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Removes the Cloud Run Invoker binding from the IAM policy of a - Google Cloud Function's underlying Cloud Run service. + (ALPHA) Removes the invoker role IAM policy binding that allows the + specified member to invoke the specified function. - This command applies to Cloud Functions (2nd gen) only. Cloud Functions - (2nd gen) currently requires the Cloud Run Invoke permission on the - underlying Cloud Run service to be able to call functions. This command - removes the given member permission to invoke the given 2nd gen function. + For Cloud Functions (1st gen), this removes the Cloud Functions Invoker + binding from the IAM policy of the specified function. + + For Cloud Functions (2nd gen), this removes the Cloud Run Invoker binding + from the IAM policy of the specified function's underlying Cloud Run + service. EXAMPLES To remove the invoker role policy binding for FUNCTION-1 for member @@ -74,6 +77,15 @@ REQUIRED FLAGS ◆ allAuthenticatedUsers - Special identifier that represents anyone who is authenticated with a Google account or a service account. +OPTIONAL FLAGS + --gen2 + If enabled, this command will use Cloud Functions (Second generation). + If disabled with --no-gen2, Cloud Functions (First generation) will be + used. If not specified, the value of this flag will be taken from the + functions/gen2 configuration property. If the functions/gen2 + configuration property is not set, defaults to looking up the given + function and using its generation. + 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/redis/clusters/create b/gcloud/alpha/redis/clusters/create index 0ed28591d..1225bf616 100644 --- a/gcloud/alpha/redis/clusters/create +++ b/gcloud/alpha/redis/clusters/create @@ -128,7 +128,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 redis clusters create $ gcloud beta redis clusters create diff --git a/gcloud/alpha/redis/clusters/delete b/gcloud/alpha/redis/clusters/delete index c985e6a66..1db6b25a9 100644 --- a/gcloud/alpha/redis/clusters/delete +++ b/gcloud/alpha/redis/clusters/delete @@ -74,7 +74,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud redis clusters delete $ gcloud beta redis clusters delete diff --git a/gcloud/alpha/redis/clusters/describe b/gcloud/alpha/redis/clusters/describe index 4d2c4638c..5eb3b362a 100644 --- a/gcloud/alpha/redis/clusters/describe +++ b/gcloud/alpha/redis/clusters/describe @@ -71,7 +71,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud redis clusters describe $ gcloud beta redis clusters describe diff --git a/gcloud/alpha/redis/clusters/get-cluster-certificate-authority b/gcloud/alpha/redis/clusters/get-cluster-certificate-authority index dce902fe5..f666146f3 100644 --- a/gcloud/alpha/redis/clusters/get-cluster-certificate-authority +++ b/gcloud/alpha/redis/clusters/get-cluster-certificate-authority @@ -72,7 +72,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud redis clusters get-cluster-certificate-authority $ gcloud beta redis clusters get-cluster-certificate-authority diff --git a/gcloud/alpha/redis/clusters/help b/gcloud/alpha/redis/clusters/help index 46ac2ad6e..2c59a1c04 100644 --- a/gcloud/alpha/redis/clusters/help +++ b/gcloud/alpha/redis/clusters/help @@ -39,7 +39,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 redis clusters $ gcloud beta redis clusters diff --git a/gcloud/alpha/redis/clusters/list b/gcloud/alpha/redis/clusters/list index b43fe3540..857c8ea97 100644 --- a/gcloud/alpha/redis/clusters/list +++ b/gcloud/alpha/redis/clusters/list @@ -84,7 +84,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 redis clusters list $ gcloud beta redis clusters list diff --git a/gcloud/alpha/redis/clusters/update b/gcloud/alpha/redis/clusters/update index f7b200020..5742dd1ee 100644 --- a/gcloud/alpha/redis/clusters/update +++ b/gcloud/alpha/redis/clusters/update @@ -82,7 +82,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 redis clusters update $ gcloud beta redis clusters update diff --git a/gcloud/alpha/run/deploy b/gcloud/alpha/run/deploy index 951be1f68..a582854eb 100644 --- a/gcloud/alpha/run/deploy +++ b/gcloud/alpha/run/deploy @@ -15,7 +15,7 @@ SYNOPSIS --update-config-maps=[KEY=VALUE,...]] [--[no-]allow-unauthenticated --breakglass=JUSTIFICATION --clear-vpc-connector --[no-]cpu-boost --[no-]cpu-throttling - --description=DESCRIPTION + --[no-]default-url --description=DESCRIPTION --execution-environment=EXECUTION_ENVIRONMENT --revision-suffix=REVISION_SUFFIX --[no-]session-affinity --vpc-connector=VPC_CONNECTOR --vpc-egress=VPC_EGRESS @@ -291,6 +291,10 @@ FLAGS serving requests. Use --cpu-throttling to enable and --no-cpu-throttling to disable. + --[no-]default-url + enables the default url for a run service. Use --default-url to + enable and --no-default-url to disable. + --description=DESCRIPTION Provides an optional, human-readable description of the service. diff --git a/gcloud/alpha/run/services/update b/gcloud/alpha/run/services/update index ae82496c6..7b5626513 100644 --- a/gcloud/alpha/run/services/update +++ b/gcloud/alpha/run/services/update @@ -11,7 +11,7 @@ SYNOPSIS [--service-account=SERVICE_ACCOUNT] [--tag=TAG] [--timeout=TIMEOUT] [--no-traffic] [--breakglass=JUSTIFICATION --clear-vpc-connector --[no-]cpu-boost - --[no-]cpu-throttling --description=DESCRIPTION + --[no-]cpu-throttling --[no-]default-url --description=DESCRIPTION --execution-environment=EXECUTION_ENVIRONMENT --revision-suffix=REVISION_SUFFIX --[no-]session-affinity --vpc-connector=VPC_CONNECTOR --vpc-egress=VPC_EGRESS @@ -197,6 +197,10 @@ FLAGS serving requests. Use --cpu-throttling to enable and --no-cpu-throttling to disable. + --[no-]default-url + enables the default url for a run service. Use --default-url to + enable and --no-default-url to disable. + --description=DESCRIPTION Provides an optional, human-readable description of the service. diff --git a/gcloud/alpha/scc/help b/gcloud/alpha/scc/help index 481bcb5e7..49cea150f 100644 --- a/gcloud/alpha/scc/help +++ b/gcloud/alpha/scc/help @@ -34,6 +34,18 @@ GROUPS operations (ALPHA) Manage Cloud SCC (Security Command Center) operations. + posture-deployments + (ALPHA) Manage Cloud Security Command Center (SCC) posture deployments. + + posture-templates + (ALPHA) Manage Cloud Security Command Center (SCC) posture templates. + + postures + (ALPHA) Manage Cloud Security Command Center (SCC) postures. + + securityposture-operations + (ALPHA) Manage Cloud Security Command Center (SCC) operations. + settings (ALPHA) Manage Cloud SCC (Security Command Center) settings. diff --git a/gcloud/alpha/scc/posture-deployments/create b/gcloud/alpha/scc/posture-deployments/create new file mode 100644 index 000000000..3af1d2dcf --- /dev/null +++ b/gcloud/alpha/scc/posture-deployments/create @@ -0,0 +1,67 @@ +NAME + gcloud alpha scc posture-deployments create - create a Cloud Security + Command Center posture deployment + +SYNOPSIS + gcloud alpha scc posture-deployments create POSTURE_DEPLOYMENT_PARENT + POSTURE_DEPLOYMENT_ID --posture-name=POSTURE_NAME + --posture-revision-id=POSTURE_REVISION_ID + --target-resource=TARGET_RESOURCE [--description=DESCRIPTION] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Create a Cloud Security Command Center (SCC) posture deployment. + First argument is the parent of the posture-deployment to be created. + Second argument is the name of the posture-deployment to be created. It is + followed by details of the posture to be deployed and the target_resource + to be deployed on. + + LRO operation ID is returned as the response of the command. + +POSITIONAL ARGUMENTS + POSTURE_DEPLOYMENT_PARENT + Name of the organization of the workload where posture-deployment is to + be created. Format: organizations//locations/ + + POSTURE_DEPLOYMENT_ID + Name of the posture-deployment to be created. It has to be unique for + an organization. + +REQUIRED FLAGS + --posture-name=POSTURE_NAME + Posture that needs to be deployed. Format: + organizations//locations/global/postures/ + + --posture-revision-id=POSTURE_REVISION_ID + Posture revision that needs to be deployed. + + --target-resource=TARGET_RESOURCE + Name of the workload on which posture deployment is to be created. It + could be an organization, folder or a project. Possible formats: | + organizations/ | folders/ | + projects/ The above mentioned IDs need to have numeric + format. + +OPTIONAL FLAGS + --description=DESCRIPTION + User provided description of the posture-deployment. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the securityposture/v1alpha 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. + diff --git a/gcloud/alpha/scc/posture-deployments/delete b/gcloud/alpha/scc/posture-deployments/delete new file mode 100644 index 000000000..98dd9437a --- /dev/null +++ b/gcloud/alpha/scc/posture-deployments/delete @@ -0,0 +1,61 @@ +NAME + gcloud alpha scc posture-deployments delete - delete a Cloud Security + Command Center posture deployment + +SYNOPSIS + gcloud alpha scc posture-deployments delete POSTURE_DEPLOYMENT_NAME + [--etag=ETAG] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Delete a Cloud Security Command Center (SCC) posture deployment. + +EXAMPLES + Delete the posture deployment named + organizations/123/locations/global/postureDeployments/posture-deployment-foo + (i.e. a posture deployment in organization 123, location global, with id + posture-deployment-foo): + + $ gcloud alpha scc posture-deployments delete \ + organizations/123/locations/global/postureDeployments/\ + posture-deployment-foo + + Delete the posture deployment named + organizations/123/locations/global/postureDeployments/posture-deployment-foo + (i.e. a posture deployment in organization 123, location global, with id + posture-deployment-foo) for the ETAG + ABcdO1Rf5clu7Yhlkwgelo7Vl4tiqd7Sy5iP5SdkSVU + + $ gcloud alpha scc posture-deployments delete \ + organizations/123/locations/global/postureDeployments/\ + posture-deployment-foo \ + --etag=ABcdO1Rf5clu7Yhlkwgelo7Vl4tiqd7Sy5iI5SdkSVU + +POSITIONAL ARGUMENTS + POSTURE_DEPLOYMENT_NAME + Relative resource name of the posture deployment, like + organizations//locations//postureDeployments/. + +FLAGS + --etag=ETAG + Etag is an optional flag. If the provided Etag doesn't match the server + generated Etag, the delete operation won't proceed. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the securityposture/v1alpha 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. + diff --git a/gcloud/alpha/scc/posture-deployments/describe b/gcloud/alpha/scc/posture-deployments/describe new file mode 100644 index 000000000..9fd16b68e --- /dev/null +++ b/gcloud/alpha/scc/posture-deployments/describe @@ -0,0 +1,44 @@ +NAME + gcloud alpha scc posture-deployments describe - describe a Cloud Security + Command Center posture deployment + +SYNOPSIS + gcloud alpha scc posture-deployments describe POSTURE_DEPLOYMENT_NAME + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Describe a Cloud Security Command Center (SCC) posture deployment. + +EXAMPLES + Describe a posture-deployment present on an organization: organizations/123/locations/global/postureDeployments/posture-deployment-foo-1 + (i.e. a posture-deployment + in organization 123, location global, with id posture-deployment-foo-1): + + $ gcloud alpha scc posture-deployments describe \ + organizations/123/locations/global/postureDeployments/\ + posture-deployment-foo-1 + +POSITIONAL ARGUMENTS + POSTURE_DEPLOYMENT_NAME + Relative resource name of the posture-deployment, like + organizations//locations//postureDeployments/. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the securityposture/v1alpha 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. + diff --git a/gcloud/alpha/scc/posture-deployments/help b/gcloud/alpha/scc/posture-deployments/help new file mode 100644 index 000000000..96f0d01d3 --- /dev/null +++ b/gcloud/alpha/scc/posture-deployments/help @@ -0,0 +1,44 @@ +NAME + gcloud alpha scc posture-deployments - manage Cloud Security Command Center + posture deployments + +SYNOPSIS + gcloud alpha scc posture-deployments COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Manage Cloud Security Command Center (SCC) posture deployments. + +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 Cloud Security Command Center (SCC) posture + deployment. + + delete + (ALPHA) Delete a Cloud Security Command Center (SCC) posture + deployment. + + describe + (ALPHA) Describe a Cloud Security Command Center (SCC) posture + deployment. + + list + (ALPHA) List the details of Cloud Security Command Center (SCC) posture + deployments. + + update + (ALPHA) Update the given Cloud Security Command Center (SCC) posture + deployment. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/scc/posture-deployments/list b/gcloud/alpha/scc/posture-deployments/list new file mode 100644 index 000000000..0f6e33451 --- /dev/null +++ b/gcloud/alpha/scc/posture-deployments/list @@ -0,0 +1,71 @@ +NAME + gcloud alpha scc posture-deployments list - list the details of Cloud + Security Command Center posture deployments + +SYNOPSIS + gcloud alpha scc posture-deployments list PARENT [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) List the details of the Cloud Security Command Center (SCC) posture + deployments for the specified organization. + +EXAMPLES + To list Cloud Security Command Center posture deployments for organization + 123, run: + + $ gcloud alpha scc posture-deployments list \ + organizations/123/locations/global + +POSITIONAL ARGUMENTS + PARENT + Organization for listing the Cloud Security Command Center posture + deployments available at the organization level. Formatted as + organizations//locations/. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the securityposture/v1alpha 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. + diff --git a/gcloud/alpha/scc/posture-deployments/update b/gcloud/alpha/scc/posture-deployments/update new file mode 100644 index 000000000..48339d890 --- /dev/null +++ b/gcloud/alpha/scc/posture-deployments/update @@ -0,0 +1,78 @@ +NAME + gcloud alpha scc posture-deployments update - update the given Cloud + Security Command Center posture deployment + +SYNOPSIS + gcloud alpha scc posture-deployments update POSTURE_DEPLOYMENT_NAME + [--description=DESCRIPTION] [--etag=ETAG] [--update-mask=UPDATE_MASK] + [--posture-id=POSTURE_ID --posture-revision-id=POSTURE_REVISION_ID] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Update a Cloud Security Command Center (SCC) posture deployment. + + Fields specified in update-mask flag are updated. Updatable fields are + description and posture_name with posture_revision-id. The target_resource + for a posture deployment cannot be updated. The posture deployment to be + updated should be in ACTIVE State. If posture details of posture deployment + need to be updated, then the desired posture needs to be in ACTIVE state. + LRO operation ID is returned as the response of the command. + +EXAMPLES + Update the description of the posture deployment named + foo-posture-deployment in the organization + organizations/123/locations/global: $ gcloud alpha scc posture-deployments update \ + organizations/123/locations/global/postureDeployments/\ + foo-posture-deployment --update-mask=description \ + --description="updated-description" + + Update posture deployment named foo-posture-deployment with the posture + named foo-posture and revision_id abcdefgh in the organization + organizations/123/locations/global: $ gcloud alpha scc posture-deployments update \ + organizations/123/locations/global/postureDeployments/\ + foo-posture-deployment \ + --update-mask=posture_id,posture_revision-id \ + --posture-id=foo-posture --posture-revision-id=abcdefgh + +POSITIONAL ARGUMENTS + POSTURE_DEPLOYMENT_NAME + Relative resource name of the posture-deployment, like + organizations//locations//postureDeployments/. + +FLAGS + --description=DESCRIPTION + Updated description of posture deployment. + + --etag=ETAG + Etag is an optional flag. If the provided Etag doesn't match the server + generated Etag, the update operation won't proceed. + + --update-mask=UPDATE_MASK + Comma-separated string containing list of fields to be updated. + + --posture-id=POSTURE_ID + Relative name of the posture to be updated, like + organizations//locations//postures/. + + --posture-revision-id=POSTURE_REVISION_ID + Revision ID of the posture to be updated. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the securityposture/v1alpha 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. + diff --git a/gcloud/alpha/scc/posture-templates/describe b/gcloud/alpha/scc/posture-templates/describe new file mode 100644 index 000000000..a2414fc53 --- /dev/null +++ b/gcloud/alpha/scc/posture-templates/describe @@ -0,0 +1,59 @@ +NAME + gcloud alpha scc posture-templates describe - describe a Cloud Security + Command Center posture template + +SYNOPSIS + gcloud alpha scc posture-templates describe POSTURE_TEMPLATE_NAME + [--revision-id=REVISION_ID] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Describe a Cloud Security Command Center (SCC) posture template. + + By default, the latest created revision of the posture template is + described. Users must provide revision ID to describe a specific revision. + +EXAMPLES + Describe a posture template named + organizations/123/locations/global/postureTemplates/secure_by_default (i.e. + a posture in organization 123, location global, with id secure_by_default): + + $ gcloud alpha scc posture-templates describe \ + organizations/123/locations/global/postureTemplates/\ + secure_by_default + + Describe a specific revision v1.0.0 of posture template named + organizations/123/locations/global/postureTemplates/secure_by_default: + + $ gcloud alpha scc posture-templates describe \ + organizations/123/locations/global/postureTemplates/\ + secure_by_default --revision-id=v1.0.0 + +POSITIONAL ARGUMENTS + POSTURE_TEMPLATE_NAME + Relative resource name of the posture template, like + organizations//locations//postureTemplates/. + +FLAGS + --revision-id=REVISION_ID + ID of the specific posture template revision to describe. If not + specified, latest revision is described. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the securityposture/v1alpha 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. + diff --git a/gcloud/alpha/scc/posture-templates/help b/gcloud/alpha/scc/posture-templates/help new file mode 100644 index 000000000..19b45ac1f --- /dev/null +++ b/gcloud/alpha/scc/posture-templates/help @@ -0,0 +1,32 @@ +NAME + gcloud alpha scc posture-templates - manage Cloud Security Command Center + posture templates + +SYNOPSIS + gcloud alpha scc posture-templates COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Manage Cloud Security Command Center (SCC) posture templates. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + describe + (ALPHA) Describe a Cloud Security Command Center (SCC) posture + template. + + list + (ALPHA) List the details of Cloud Security Command Center (SCC) posture + templates. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/scc/posture-templates/list b/gcloud/alpha/scc/posture-templates/list new file mode 100644 index 000000000..d5bbec789 --- /dev/null +++ b/gcloud/alpha/scc/posture-templates/list @@ -0,0 +1,71 @@ +NAME + gcloud alpha scc posture-templates list - list the details of Cloud + Security Command Center posture templates + +SYNOPSIS + gcloud alpha scc posture-templates list PARENT [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) List the details of the Cloud Security Command Center (SCC) posture + templates for the specified organization. + +EXAMPLES + To list Cloud Security Command Center posture templates for organization + 123, run: + + $ gcloud alpha scc posture-templates list \ + organizations/123/locations/global + +POSITIONAL ARGUMENTS + PARENT + Organization for listing the Cloud Security Command Center posture + templates available at the organization level. Formatted as + organizations//locations/. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the securityposture/v1alpha 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. + diff --git a/gcloud/alpha/scc/postures/create b/gcloud/alpha/scc/postures/create new file mode 100644 index 000000000..2dc096b2e --- /dev/null +++ b/gcloud/alpha/scc/postures/create @@ -0,0 +1,54 @@ +NAME + gcloud alpha scc postures create - create a Cloud Security Command Center + posture + +SYNOPSIS + gcloud alpha scc postures create POSTURE_PARENT POSTURE_ID + --posture-from-file=POSTURE_FROM_FILE [--async] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Create a Cloud Security Command Center (SCC) posture. First + argument is the parent of the posture to be created. Second argument is the + name of the posture to be created. The posture details are provided in YAML + file. The file path is mentioned in posture-from-file flag. + + Created posture is returned as the response of the command. LRO operation + ID is printed as the standard output. + +POSITIONAL ARGUMENTS + POSTURE_PARENT + Organization where posture is to be created. Format: + organizations//locations/ + + POSTURE_ID + Name of the posture to be created. It has to be unique for an + organization. + +REQUIRED FLAGS + --posture-from-file=POSTURE_FROM_FILE + YAML file containing the body of the posture to be created. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the securityposture/v1alpha 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. + diff --git a/gcloud/alpha/scc/postures/delete b/gcloud/alpha/scc/postures/delete new file mode 100644 index 000000000..a9b06c37d --- /dev/null +++ b/gcloud/alpha/scc/postures/delete @@ -0,0 +1,65 @@ +NAME + gcloud alpha scc postures delete - delete a Cloud Security Command Center + posture + +SYNOPSIS + gcloud alpha scc postures delete POSTURE_NAME [--async] [--etag=ETAG] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Delete a Cloud Security Command Center (SCC) posture. + + Posture with all it's revisions is deleted. Deletion won't be allowed in + case any of the versions of the posture is deployed on a workload. ETAG can + be provided as an optional flag. + +EXAMPLES + Delete the posture named + organizations/123/locations/global/postures/posture-foo-1 (i.e. a posture + in organization 123, location global, with id posture-foo-1): + + $ gcloud alpha scc postures delete \ + organizations/123/locations/global/postures/posture-foo-1 + + Delete the posture named + organizations/123/locations/global/postures/posture-foo-1 (i.e. a posture + in organization 123, location global, with id posture-foo-1) for the ETAG + ABcdO1Rf5clu7Yhlkwgelo7Vl4tiqd7Sy5iP5SdkSVU + + $ gcloud alpha scc postures delete \ + organizations/123/locations/global/postures/posture-foo-1 \ + --etag=ABcdO1Rf5clu7Yhlkwgelo7Vl4tiqd7Sy5iI5SdkSVU + +POSITIONAL ARGUMENTS + POSTURE_NAME + Relative resource name of the posture, like + organizations//locations//postures/. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --etag=ETAG + Etag is an optional flag. If the provided Etag doesn't match the server + generated Etag, the delete operation won't proceed. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the securityposture/v1alpha 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. + diff --git a/gcloud/alpha/scc/postures/describe b/gcloud/alpha/scc/postures/describe new file mode 100644 index 000000000..055cbc1f8 --- /dev/null +++ b/gcloud/alpha/scc/postures/describe @@ -0,0 +1,58 @@ +NAME + gcloud alpha scc postures describe - describe a Cloud Security Command + Center posture + +SYNOPSIS + gcloud alpha scc postures describe POSTURE_NAME [--revision-id=REVISION_ID] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Describe a Cloud Security Command Center (SCC) posture. + + By default, the latest created revision of the posture is described. Users + must provide revision ID to describe a specific revision. + +EXAMPLES + Describe the latest revision of a posture named + organizations/123/locations/global/postures/posture-foo-1 (i.e. a posture + in organization 123, location global, with id posture-foo-1): + + $ gcloud alpha scc postures describe \ + organizations/123/locations/global/postures/posture-foo-1 + + Describe a specific revision abcdefg of posture named + organizations/123/locations/global/postures/posture-foo-1: + + $ gcloud alpha scc postures describe \ + organizations/123/locations/global/postures/posture-foo-1 \ + --revision-id=abcdefg + +POSITIONAL ARGUMENTS + POSTURE_NAME + Relative resource name of the posture, like + organizations//locations//postures/. + +FLAGS + --revision-id=REVISION_ID + ID of the specific posture revision to describe. If not specified, + latest revision is described. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the securityposture/v1alpha 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. + diff --git a/gcloud/alpha/scc/postures/extract b/gcloud/alpha/scc/postures/extract new file mode 100644 index 000000000..fe5aa82f1 --- /dev/null +++ b/gcloud/alpha/scc/postures/extract @@ -0,0 +1,57 @@ +NAME + gcloud alpha scc postures extract - extract a Cloud Security Command Center + posture from a workload + +SYNOPSIS + gcloud alpha scc postures extract POSTURE_PARENT POSTURE_ID + --workload=WORKLOAD [--async] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Extract a Cloud Security Command Center (SCC) posture from a + workload. First argument is the parent of the posture to be created. Second + argument is the name of the posture to be created. The workload from where + the organization policies need to be extracted is provided via 'workload' + flag. + + Extracted posture is returned as the response of the command. LRO operation + ID is printed as the standard output. + +POSITIONAL ARGUMENTS + POSTURE_PARENT + Organization where posture is to be created. Format: + organizations//locations/ + + POSTURE_ID + Name of the posture to be created. It has to be unique for an + organization. + +REQUIRED FLAGS + --workload=WORKLOAD + Workload from where policies has to be extracted into a posture. It can + be in one of the following formats: projects/projectNumber, + folders/folderNumber, organizations/organizationNumber. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the securityposture/v1alpha 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. + diff --git a/gcloud/alpha/scc/postures/help b/gcloud/alpha/scc/postures/help new file mode 100644 index 000000000..22aa40eb6 --- /dev/null +++ b/gcloud/alpha/scc/postures/help @@ -0,0 +1,47 @@ +NAME + gcloud alpha scc postures - manage Cloud Security Command Center postures + +SYNOPSIS + gcloud alpha scc postures COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Manage Cloud Security Command Center (SCC) postures. + +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 Cloud Security Command Center (SCC) posture. + + delete + (ALPHA) Delete a Cloud Security Command Center (SCC) posture. + + describe + (ALPHA) Describe a Cloud Security Command Center (SCC) posture. + + extract + (ALPHA) Extract a Cloud Security Command Center (SCC) posture from a + workload. + + list + (ALPHA) Lists all the Cloud Security Command Center (SCC) postures for + an organization. + + list-revisions + (ALPHA) List the revisions of a Cloud Security Command Center (SCC) + posture. + + update + (ALPHA) Update the given Cloud Security Command Center (SCC) posture. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/scc/postures/list b/gcloud/alpha/scc/postures/list new file mode 100644 index 000000000..266bbc99a --- /dev/null +++ b/gcloud/alpha/scc/postures/list @@ -0,0 +1,75 @@ +NAME + gcloud alpha scc postures list - lists all the Cloud Security Command + Center postures for an organization + +SYNOPSIS + gcloud alpha scc postures list PARENT [--filter=EXPRESSION] [--limit=LIMIT] + [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Lists all Cloud Security Command Center (SCC) postures for an + organization. + + By default, postures created in global location are returned. + +EXAMPLES + List all postures in organization 123. If location is omitted, this returns + postures from location 'global'. For a posture with multiple revisions, + only the latest revision of the posture is returned in the output. + + $ gcloud alpha scc postures list organizations/123 + + List all postures in organization 123, location global + + $ gcloud alpha scc postures list organizations/123/locations/global + +POSITIONAL ARGUMENTS + PARENT + Resource name of the parent, like organizations/ or + organizations//locations/. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the securityposture/v1alpha 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. + diff --git a/gcloud/alpha/scc/postures/list-revisions b/gcloud/alpha/scc/postures/list-revisions new file mode 100644 index 000000000..04e72a8d0 --- /dev/null +++ b/gcloud/alpha/scc/postures/list-revisions @@ -0,0 +1,71 @@ +NAME + gcloud alpha scc postures list-revisions - list the revisions of a Cloud + Security Command Center posture + +SYNOPSIS + gcloud alpha scc postures list-revisions POSTURE_NAME [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) List the revisions of a Cloud Security Command Center (SCC) + posture. + +EXAMPLES + To list Cloud Security Command Center posture revisions for posture + organizations/123/locations/global/postures/posture123 , run: + + $ gcloud alpha scc postures list-revisions \ + organizations/123/locations/global/postures/posture123 + +POSITIONAL ARGUMENTS + POSTURE_NAME + Posture name of the Cloud Security Command Center posture for listing + the revisions. Formatted as + organizations//locations//postures/ + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the securityposture/v1alpha 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. + diff --git a/gcloud/alpha/scc/postures/update b/gcloud/alpha/scc/postures/update new file mode 100644 index 000000000..9b399851a --- /dev/null +++ b/gcloud/alpha/scc/postures/update @@ -0,0 +1,142 @@ +NAME + gcloud alpha scc postures update - update the given Cloud Security Command + Center posture + +SYNOPSIS + gcloud alpha scc postures update + (POSTURE : --location=LOCATION --organization=ORGANIZATION) + --posture-from-file=POSTURE_FROM_FILE --revision-id=REVISION_ID + [--async] [--update-mask=UPDATE_MASK] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Update a Cloud Security Command Center (SCC) posture. + + Fields specified in update-mask flag are updated. Updatable fields are + state, description and policy_sets. State of the posture can't be updated + along with update of other fields. An empty or "" as field mask will result + in update of policy_sets and description. In case of the update of + policy_sets, the value mentioned in the update posture request overwrites + the exisiting value of policy_sets. + + Valid state transitions are: a) ACTIVE to DRAFT b) ACTIVE to DEPRECATED c) + DRAFT to ACTIVE d) DEPRECATED to ACTIVE + + The update operation will result in the update of the revision-id specified + in the request, unless the posture revision is currently deployed on a + workload. A new revision is created for an already deployed posture + revision. + +EXAMPLES + Update the revision-id abcdefgh of the posture named foo-posture in the + organization organizations/123/locations/global: Change State to ACTIVE. $ gcloud alpha scc postures update \ + organizations/123/locations/global/postures/foo-posture \ + --posture-from-file=update_posture.yaml --revision-id=abcdefgh \ + update_mask=state + + Contents of update_posture.yaml are | + name: organizations/123/locations/global/postures/foo-posture + state: ACTIVE + + Update the revision-id abcdefgh of the posture named foo-posture in the + organization organizations/123/locations/global: Change description and + policy_sets to the values mentioned in update_posture.yaml $ gcloud alpha scc postures update \ + organizations/123/locations/global/postures/foo-posture \ + --posture-from-file=update_posture.yaml --revision-id=abcdefgh \ + update_mask=description,policy_sets + + Contents of update_posture.yaml are | + name: organizations/123/locations/global/postures/foo-posture + description: updated description + policy_sets: + - policy_set_id: newPolicySet1 + policies: + - policy_id: newPolicy + constraint: + org_policy_canned_constraint: + canned_constraint_id: storage.uniformBucketLevelAccess + policy_rules: + enforce: false + - policy_set_id: PolicySet2 + policies: + - policy_id: Policy3 + constraint: + org_policy_custom_constraint: + custom_constraint: + name: organizations/9454078371/customConstraints/custom.newConstraint + resource_types: container.$$UNIVERSE_DOMAIN$$/NodePool + method_types: UPDATE + condition: resource.management.autoUpgrade == false + action_type: ALLOW + policy_rules: + enforce: true + +POSITIONAL ARGUMENTS + Posture resource - Arguments and flags that specify the Posture instance + to update. The arguments in this group can be used to specify the + attributes of this resource. + + This must be specified. + + POSTURE + ID of the posture or fully qualified identifier for the posture. + + To set the posture attribute: + ▸ provide the argument posture on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The location Id. + + To set the location attribute: + ▸ provide the argument posture on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + + --organization=ORGANIZATION + The organization Id. + + To set the organization attribute: + ▸ provide the argument posture on the command line with a fully + specified name; + ▸ provide the argument --organization on the command line. + +REQUIRED FLAGS + --posture-from-file=POSTURE_FROM_FILE + Path of the file containing the details of the field to be updated. + Contents include the name of the posture to be updated and value of the + fields to be updated. + + --revision-id=REVISION_ID + Revision ID of the posture to be updated. The same revision ID will be + updated in case the posture revision is not deployed on any workload. A + new revision will be created for a deployed posture. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --update-mask=UPDATE_MASK + Comma separated string containing list of fields to be updated. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the securityposture/v1alpha 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. + diff --git a/gcloud/alpha/scc/securityposture-operations/describe b/gcloud/alpha/scc/securityposture-operations/describe new file mode 100644 index 000000000..9d9d3c55f --- /dev/null +++ b/gcloud/alpha/scc/securityposture-operations/describe @@ -0,0 +1,44 @@ +NAME + gcloud alpha scc securityposture-operations describe - describe a SCC + Security Posture's long running scan operation + +SYNOPSIS + gcloud alpha scc securityposture-operations describe OPERATION_NAME + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Describe a SCC Security Posture's long running scan operation. + +EXAMPLES + Return long running scan operation status for operation id + (operation-1694515698847-605272e4bcd7c-f93dade6-067467ae) for parent + organizations/123/locations/global + + $ gcloud alpha scc securityposture-operations describe \ + organizations/123/locations/global/operations/\ + operation-1694515698847-605272e4bcd7c-f93dade6-067467ae + +POSITIONAL ARGUMENTS + OPERATION_NAME + Relative resource name of the operation, of the format: + organizations//locations//operations/. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the securityposture/v1alpha 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. + diff --git a/gcloud/alpha/scc/securityposture-operations/help b/gcloud/alpha/scc/securityposture-operations/help new file mode 100644 index 000000000..efcdc1156 --- /dev/null +++ b/gcloud/alpha/scc/securityposture-operations/help @@ -0,0 +1,27 @@ +NAME + gcloud alpha scc securityposture-operations - manage Cloud Security Command + Center operations + +SYNOPSIS + gcloud alpha scc securityposture-operations COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Manage Cloud Security Command Center (SCC) operations. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + describe + (ALPHA) Describe a SCC Security Posture's long running scan operation. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/services/api-keys/update b/gcloud/alpha/services/api-keys/update index b54e48b4d..6904ef4fb 100644 --- a/gcloud/alpha/services/api-keys/update +++ b/gcloud/alpha/services/api-keys/update @@ -66,14 +66,12 @@ EXAMPLES The content of 'my-flags.yaml' is as following: - --api-target: - service: - - "foo.service.com" + service: "foo.service.com" - --api-target: - service: - - "bar.service.com" + service: "bar.service.com" methods: - - "foomethod" - - "barmethod" + - "foomethod" + - "barmethod" POSITIONAL ARGUMENTS Key resource - The name of the key to update. The arguments in this group diff --git a/gcloud/alpha/storage/buckets/create b/gcloud/alpha/storage/buckets/create index a92b7e106..413493c72 100644 --- a/gcloud/alpha/storage/buckets/create +++ b/gcloud/alpha/storage/buckets/create @@ -8,12 +8,13 @@ SYNOPSIS -k DEFAULT_ENCRYPTION_KEY] [--default-storage-class=DEFAULT_STORAGE_CLASS, -c DEFAULT_STORAGE_CLASS, -s DEFAULT_STORAGE_CLASS] - [--[no-]enable-autoclass] [--location=LOCATION, -l LOCATION] + [--location=LOCATION, -l LOCATION] [--[no-]pap, --[no-]public-access-prevention] [--placement=REGION,REGION] [--recovery-point-objective=SETTING, --rpo=SETTING] [--retention-period=RETENTION_PERIOD] - [--[no-]uniform-bucket-level-access, -b] [GCLOUD_WIDE_FLAG ...] + [--[no-]uniform-bucket-level-access, -b] [--[no-]enable-autoclass] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Create new buckets. @@ -54,11 +55,6 @@ FLAGS If not specified, the default storage class used by Cloud Storage is "Standard". - --[no-]enable-autoclass - The Autoclass feature automatically selects the best storage class for - objects based on access patterns. Use --enable-autoclass to enable and - --no-enable-autoclass to disable. - --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 @@ -103,6 +99,12 @@ FLAGS --uniform-bucket-level-access to enable and --no-uniform-bucket-level-access to disable. +AUTOCLASS FLAGS + --[no-]enable-autoclass + The Autoclass feature automatically selects the best storage class for + objects based on access patterns. Use --enable-autoclass to enable and + --no-enable-autoclass to disable. + 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/buckets/update b/gcloud/alpha/storage/buckets/update index c9185516e..1a7ff8491 100644 --- a/gcloud/alpha/storage/buckets/update +++ b/gcloud/alpha/storage/buckets/update @@ -4,8 +4,7 @@ NAME SYNOPSIS gcloud alpha storage buckets update URL [URL ...] [--additional-headers=HEADER=VALUE] [--continue-on-error, -c] - [--[no-]default-event-based-hold] [--[no-]enable-autoclass] - [--lock-retention-period] + [--[no-]default-event-based-hold] [--lock-retention-period] [--recovery-point-objective=SETTING, --rpo=SETTING] [--[no-]requester-pays] [--[no-]uniform-bucket-level-access] [--[no-]versioning] @@ -30,7 +29,8 @@ SYNOPSIS [--clear-retention-period | --retention-period=RETENTION_PERIOD] [--clear-web-error-page | --web-error-page=WEB_ERROR_PAGE] [--clear-web-main-page-suffix - | --web-main-page-suffix=WEB_MAIN_PAGE_SUFFIX] [GCLOUD_WIDE_FLAG ...] + | --web-main-page-suffix=WEB_MAIN_PAGE_SUFFIX] + [--[no-]enable-autoclass] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Update a bucket. @@ -71,11 +71,6 @@ FLAGS retroactively). Use --default-event-based-hold to enable and --no-default-event-based-hold to disable. - --[no-]enable-autoclass - The Autoclass feature automatically selects the best storage class for - objects based on access patterns. Use --enable-autoclass to enable and - --no-enable-autoclass to disable. - --lock-retention-period Locks an unlocked retention policy on the buckets. Caution: A locked retention policy cannot be removed from a bucket or reduced in @@ -292,6 +287,12 @@ FLAGS domain serves the specified "main" page instead of performing the usual bucket listing. +AUTOCLASS FLAGS + --[no-]enable-autoclass + The Autoclass feature automatically selects the best storage class for + objects based on access patterns. Use --enable-autoclass to enable and + --no-enable-autoclass to disable. + 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/workstations/configs/create b/gcloud/alpha/workstations/configs/create index 928294d17..49c849d46 100644 --- a/gcloud/alpha/workstations/configs/create +++ b/gcloud/alpha/workstations/configs/create @@ -21,8 +21,10 @@ SYNOPSIS [--pd-reclaim-policy=PD_RECLAIM_POLICY; default="delete"] [--pool-size=POOL_SIZE] [--replica-zones=[REPLICA_ZONES,...]] [--running-timeout=RUNNING_TIMEOUT; default=7200] - [--service-account=SERVICE_ACCOUNT] [--shielded-integrity-monitoring] - [--shielded-secure-boot] [--shielded-vtpm] + [--service-account=SERVICE_ACCOUNT] + [--service-account-scopes=[SERVICE_ACCOUNT_SCOPES,...]] + [--shielded-integrity-monitoring] [--shielded-secure-boot] + [--shielded-vtpm] [--accelerator-count=ACCELERATOR_COUNT : --accelerator-type=ACCELERATOR_TYPE] [--container-custom-image=CONTAINER_CUSTOM_IMAGE @@ -212,6 +214,12 @@ FLAGS to pull the specified container image. If not set, VMs will run without a service account, in which case the image must be publicly accessible. + --service-account-scopes=[SERVICE_ACCOUNT_SCOPES,...] + Scopes to grant to the service_account. Various scopes are + automatically added based on feature usage. When specified, users of + workstations under this configuration must have + iam.serviceAccounts.actAs on the service account. + --shielded-integrity-monitoring Default value is false. If set, instances will have integrity monitoring enabled. diff --git a/gcloud/alpha/workstations/configs/update b/gcloud/alpha/workstations/configs/update index ca8931266..8b126598c 100644 --- a/gcloud/alpha/workstations/configs/update +++ b/gcloud/alpha/workstations/configs/update @@ -16,6 +16,7 @@ SYNOPSIS [--labels=[LABELS,...]] [--machine-type=MACHINE_TYPE] [--network-tags=[NETWORK_TAGS,...]] [--pool-size=POOL_SIZE] [--running-timeout=RUNNING_TIMEOUT] [--service-account=SERVICE_ACCOUNT] + [--service-account-scopes=[SERVICE_ACCOUNT_SCOPES,...]] [--shielded-integrity-monitoring] [--shielded-secure-boot] [--shielded-vtpm] [--accelerator-count=ACCELERATOR_COUNT @@ -172,6 +173,12 @@ FLAGS to pull the specified container image. If not set, VMs will run without a service account, in which case the image must be publicly accessible. + --service-account-scopes=[SERVICE_ACCOUNT_SCOPES,...] + Scopes to grant to the service_account. Various scopes are + automatically added based on feature usage. When specified, users of + workstations under this configuration must have + iam.serviceAccounts.actAs on the service account. + --shielded-integrity-monitoring Default value is false. If set, instances will have integrity monitoring enabled. diff --git a/gcloud/beta/ai/index-endpoints/deploy-index b/gcloud/beta/ai/index-endpoints/deploy-index index 2324dcf88..30e026ff1 100644 --- a/gcloud/beta/ai/index-endpoints/deploy-index +++ b/gcloud/beta/ai/index-endpoints/deploy-index @@ -7,20 +7,23 @@ SYNOPSIS (INDEX_ENDPOINT : --region=REGION) --deployed-index-id=DEPLOYED_INDEX_ID --display-name=DISPLAY_NAME --index=INDEX [--max-replica-count=MAX_REPLICA_COUNT] - [--min-replica-count=MIN_REPLICA_COUNT] [GCLOUD_WIDE_FLAG ...] + [--min-replica-count=MIN_REPLICA_COUNT] + [--reserved-ip-ranges=[RESERVED_IP_RANGES,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Deploy an index to a Vertex AI index endpoint. EXAMPLES To deploy index 345 to an index endpoint 456 with 2 min replica count and - 10 max replica count under project example in region us-central1, run: + 10 max replica count under project example in region us-central1, within + reserved ip ranges vertex-ai-ip-ranges-1 and vertex-ai-ip-ranges-2 run: $ gcloud beta ai index-endpoints deploy-index 456 \ --project=example --region=us-central1 --index=345 \ --deployed-index-id=deployed-index-345 \ --display-name=deployed-index-345 --min-replica-count=2 \ - --max-replica-count=10 + --max-replica-count=10 \ + --reserved-ip-ranges=vertex-ai-ip-ranges-1,vertex-ai-ip-ranges-2 POSITIONAL ARGUMENTS Index endpoint resource - The index endpoint to deploy an index. The @@ -75,6 +78,9 @@ OPTIONAL FLAGS Minimum number of machine replicas the deployed index will be always deployed on. If specified, the value must be equal to or larger than 1. + --reserved-ip-ranges=[RESERVED_IP_RANGES,...] + List of reserved IP ranges deployed index will be deployed to. + 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/ai/index-endpoints/mutate-deployed-index b/gcloud/beta/ai/index-endpoints/mutate-deployed-index index 8b7afb30b..88b39e267 100644 --- a/gcloud/beta/ai/index-endpoints/mutate-deployed-index +++ b/gcloud/beta/ai/index-endpoints/mutate-deployed-index @@ -7,20 +7,23 @@ SYNOPSIS (INDEX_ENDPOINT : --region=REGION) --deployed-index-id=DEPLOYED_INDEX_ID [--max-replica-count=MAX_REPLICA_COUNT] - [--min-replica-count=MIN_REPLICA_COUNT] [GCLOUD_WIDE_FLAG ...] + [--min-replica-count=MIN_REPLICA_COUNT] + [--reserved-ip-ranges=[RESERVED_IP_RANGES,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Mutate an existing deployed index from a Vertex AI index endpoint. EXAMPLES - To mutated an deployed index deployed-index-123 from an index endpoint 456 + To mutated a deployed index deployed-index-123 from an index endpoint 456 with 2 min replica count and 10 max replica count under project example in - region us-central1, run: + region us-central1, within vertex-ai-ip-ranges-1 and vertex-ai-ip-ranges-2 + run: $ gcloud beta ai index-endpoints mutate-deployed-index 456 \ --project=example --region=us-central1 \ --deployed-index-id=deployed-index-123 --min-replica-count=2 \ - --max-replica-count=10 + --max-replica-count=10 \ + --reserved-ip-ranges=vertex-ai-ip-ranges-1,vertex-ai-ip-ranges-2 POSITIONAL ARGUMENTS Index endpoint resource - The index endpoint ID of the index endpoint.. @@ -69,6 +72,9 @@ OPTIONAL FLAGS Minimum number of machine replicas the deployed index will be always deployed on. If specified, the value must be equal to or larger than 1. + --reserved-ip-ranges=[RESERVED_IP_RANGES,...] + List of reserved IP ranges deployed index will be deployed to. + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/beta/compute/disks/create b/gcloud/beta/compute/disks/create index b0988ff48..6e276f362 100644 --- a/gcloud/beta/compute/disks/create +++ b/gcloud/beta/compute/disks/create @@ -92,8 +92,8 @@ FLAGS their boot disks. See the descriptions of supported features at: https://cloud.google.com/compute/docs/images/create-delete-deprecate-private-images#guest-os-features. GUEST_OS_FEATURE must be one of: GVNIC, MULTI_IP_SUBNET, SEV_CAPABLE, - SEV_LIVE_MIGRATABLE, SEV_SNP_CAPABLE, UEFI_COMPATIBLE, - VIRTIO_SCSI_MULTIQUEUE, WINDOWS. + SEV_LIVE_MIGRATABLE, SEV_LIVE_MIGRATABLE_V2, SEV_SNP_CAPABLE, + UEFI_COMPATIBLE, VIRTIO_SCSI_MULTIQUEUE, WINDOWS. --interface=INTERFACE Specifies the disk interface to use for attaching this disk. Valid diff --git a/gcloud/beta/compute/images/create b/gcloud/beta/compute/images/create index d41f38aa8..1fe44613a 100644 --- a/gcloud/beta/compute/images/create +++ b/gcloud/beta/compute/images/create @@ -152,8 +152,8 @@ OPTIONAL FLAGS their boot disks. See the descriptions of supported features at: https://cloud.google.com/compute/docs/images/create-delete-deprecate-private-images#guest-os-features. GUEST_OS_FEATURE must be one of: GVNIC, MULTI_IP_SUBNET, SEV_CAPABLE, - SEV_LIVE_MIGRATABLE, SEV_SNP_CAPABLE, UEFI_COMPATIBLE, - VIRTIO_SCSI_MULTIQUEUE, WINDOWS. + SEV_LIVE_MIGRATABLE, SEV_LIVE_MIGRATABLE_V2, SEV_SNP_CAPABLE, + UEFI_COMPATIBLE, VIRTIO_SCSI_MULTIQUEUE, WINDOWS. --key-exchange-key-file=[KEK_VALUE,...] Comma-separated list of file paths that point to X.509 certificates in diff --git a/gcloud/beta/compute/instance-templates/create b/gcloud/beta/compute/instance-templates/create index d597a4bba..af6f2cada 100644 --- a/gcloud/beta/compute/instance-templates/create +++ b/gcloud/beta/compute/instance-templates/create @@ -7,6 +7,7 @@ SYNOPSIS [--accelerator=[count=COUNT],[type=TYPE]] [--no-boot-disk-auto-delete] [--boot-disk-device-name=BOOT_DISK_DEVICE_NAME] [--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] [--configure-disk=[PROPERTY=VALUE,...]] @@ -119,6 +120,10 @@ FLAGS of I/O operations per second that the disk can handle. Value must be between 10,000 and 120,000. + --boot-disk-provisioned-throughput=BOOT_DISK_PROVISIONED_THROUGHPUT + Indicates how much throughput to provision for the disk. This sets the + number of throughput mb per second that the disk can handle. + --boot-disk-size=BOOT_DISK_SIZE The size of the boot disk. This option can only be specified if a new boot disk is being created (as opposed to mounting an existing diff --git a/gcloud/beta/compute/instance-templates/create-with-container b/gcloud/beta/compute/instance-templates/create-with-container index 89b4be50c..3de480eb7 100644 --- a/gcloud/beta/compute/instance-templates/create-with-container +++ b/gcloud/beta/compute/instance-templates/create-with-container @@ -8,6 +8,7 @@ SYNOPSIS [--accelerator=[count=COUNT],[type=TYPE]] [--no-boot-disk-auto-delete] [--boot-disk-device-name=BOOT_DISK_DEVICE_NAME] [--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] [--container-arg=CONTAINER_ARG] [--container-command=CONTAINER_COMMAND] @@ -109,6 +110,10 @@ FLAGS of I/O operations per second that the disk can handle. Value must be between 10,000 and 120,000. + --boot-disk-provisioned-throughput=BOOT_DISK_PROVISIONED_THROUGHPUT + Indicates how much throughput to provision for the disk. This sets the + number of throughput mb per second that the disk can handle. + --boot-disk-size=BOOT_DISK_SIZE The size of the boot disk. This option can only be specified if a new boot disk is being created (as opposed to mounting an existing diff --git a/gcloud/beta/compute/instances/bulk/create b/gcloud/beta/compute/instances/bulk/create index 36b3b7d69..c5bd1571e 100644 --- a/gcloud/beta/compute/instances/bulk/create +++ b/gcloud/beta/compute/instances/bulk/create @@ -10,6 +10,7 @@ SYNOPSIS [--no-boot-disk-auto-delete] [--boot-disk-device-name=BOOT_DISK_DEVICE_NAME] [--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] [--count=COUNT] [--create-disk=[PROPERTY=VALUE,...]] [--description=DESCRIPTION] @@ -162,6 +163,10 @@ OPTIONAL FLAGS of I/O operations per second that the disk can handle. Value must be between 10,000 and 120,000. + --boot-disk-provisioned-throughput=BOOT_DISK_PROVISIONED_THROUGHPUT + Indicates how much throughput to provision for the disk. This sets the + number of throughput mb per second that the disk can handle. + --boot-disk-size=BOOT_DISK_SIZE The size of the boot disk. This option can only be specified if a new boot disk is being created (as opposed to mounting an existing diff --git a/gcloud/beta/compute/instances/create b/gcloud/beta/compute/instances/create index 10278cb15..28a2621c2 100644 --- a/gcloud/beta/compute/instances/create +++ b/gcloud/beta/compute/instances/create @@ -8,6 +8,7 @@ SYNOPSIS [--no-boot-disk-auto-delete] [--boot-disk-device-name=BOOT_DISK_DEVICE_NAME] [--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] [--create-disk=[PROPERTY=VALUE,...]] [--csek-key-file=FILE] @@ -163,6 +164,10 @@ FLAGS of I/O operations per second that the disk can handle. Value must be between 10,000 and 120,000. + --boot-disk-provisioned-throughput=BOOT_DISK_PROVISIONED_THROUGHPUT + Indicates how much throughput to provision for the disk. This sets the + number of throughput mb per second that the disk can handle. + --boot-disk-size=BOOT_DISK_SIZE The size of the boot disk. This option can only be specified if a new boot disk is being created (as opposed to mounting an existing diff --git a/gcloud/beta/compute/instances/create-with-container b/gcloud/beta/compute/instances/create-with-container index 6137f1481..29bd0015d 100644 --- a/gcloud/beta/compute/instances/create-with-container +++ b/gcloud/beta/compute/instances/create-with-container @@ -8,6 +8,7 @@ SYNOPSIS [--no-boot-disk-auto-delete] [--boot-disk-device-name=BOOT_DISK_DEVICE_NAME] [--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] [--container-arg=CONTAINER_ARG] [--container-command=CONTAINER_COMMAND] @@ -119,6 +120,10 @@ FLAGS of I/O operations per second that the disk can handle. Value must be between 10,000 and 120,000. + --boot-disk-provisioned-throughput=BOOT_DISK_PROVISIONED_THROUGHPUT + Indicates how much throughput to provision for the disk. This sets the + number of throughput mb per second that the disk can handle. + --boot-disk-size=BOOT_DISK_SIZE The size of the boot disk. This option can only be specified if a new boot disk is being created (as opposed to mounting an existing diff --git a/gcloud/beta/compute/public-delegated-prefixes/create b/gcloud/beta/compute/public-delegated-prefixes/create index 8fa295bf4..1d8e7474f 100644 --- a/gcloud/beta/compute/public-delegated-prefixes/create +++ b/gcloud/beta/compute/public-delegated-prefixes/create @@ -3,8 +3,9 @@ NAME Engine public delegated prefix SYNOPSIS - gcloud beta compute public-delegated-prefixes create NAME - --public-advertised-prefix=PUBLIC_ADVERTISED_PREFIX --range=RANGE + gcloud beta compute public-delegated-prefixes create NAME --range=RANGE + (--public-advertised-prefix=PUBLIC_ADVERTISED_PREFIX + | --public-delegated-prefix=PUBLIC_DELEGATED_PREFIX) [--description=DESCRIPTION] [--enable-live-migration] [--global | --region=REGION] [GCLOUD_WIDE_FLAG ...] @@ -20,14 +21,20 @@ POSITIONAL ARGUMENTS Name of the public delegated prefix to operate on. REQUIRED FLAGS - --public-advertised-prefix=PUBLIC_ADVERTISED_PREFIX - Public advertised prefix that this delegated prefix is created from. - --range=RANGE IPv4 range from this public delegated prefix that should be delegated, in CIDR format. It must be smaller than parent public advertised prefix range. + Exactly one of these must be specified: + + --public-advertised-prefix=PUBLIC_ADVERTISED_PREFIX + Public advertised prefix that this delegated prefix is created from. + + --public-delegated-prefix=PUBLIC_DELEGATED_PREFIX + Regional Public delegated prefix that this delegated prefix is + created from. + OPTIONAL FLAGS --description=DESCRIPTION Description of this public delegated prefix. diff --git a/gcloud/beta/container/clusters/create b/gcloud/beta/container/clusters/create index 80cb6bc4a..ffa6bf688 100644 --- a/gcloud/beta/container/clusters/create +++ b/gcloud/beta/container/clusters/create @@ -11,6 +11,7 @@ SYNOPSIS max-shared-clients-per-gpu=MAX_SHARED_CLIENTS_PER_GPU],...]] [--addons=[ADDON,...]] [--allow-route-overlap] [--async] [--autoprovisioning-network-tags=TAGS,[TAGS,...]] + [--autoprovisioning-resource-manager-tags=[KEY=VALUE,...]] [--autoscaling-profile=AUTOSCALING_PROFILE] [--boot-disk-kms-key=BOOT_DISK_KMS_KEY] [--cloud-run-config=[load-balancer-type=EXTERNAL,...]] @@ -60,9 +61,9 @@ SYNOPSIS [--placement-policy=PLACEMENT_POLICY] [--placement-type=PLACEMENT_TYPE] [--preemptible] [--private-endpoint-subnetwork=NAME] [--private-ipv6-google-access-type=PRIVATE_IPV6_GOOGLE_ACCESS_TYPE] - [--release-channel=CHANNEL] [--security-group=SECURITY_GROUP] - [--security-posture=SECURITY_POSTURE] [--services-ipv4-cidr=CIDR] - [--services-secondary-range-name=NAME] + [--release-channel=CHANNEL] [--resource-manager-tags=[KEY=VALUE,...]] + [--security-group=SECURITY_GROUP] [--security-posture=SECURITY_POSTURE] + [--services-ipv4-cidr=CIDR] [--services-secondary-range-name=NAME] [--shielded-integrity-monitoring] [--shielded-secure-boot] [--spot] [--stack-type=STACK_TYPE] [--subnetwork=SUBNETWORK] [--system-config-from-file=SYSTEM_CONFIG_FROM_FILE] @@ -223,6 +224,31 @@ FLAGS https://cloud.google.com/sdk/gcloud/reference/compute/firewall-rules/create for examples. + --autoprovisioning-resource-manager-tags=[KEY=VALUE,...] + Applies the specified comma-separated resource manager tags that has + the GCE_FIREWALL purpose to all nodes in the new Autopilot cluster or + all auto-provisioned nodes in the new Standard cluster. + + Examples: + + $ gcloud beta container clusters create example-cluster \ + --autoprovisioning-resource-manager-tags=tagKeys/\ + 1234=tagValues/2345 + $ gcloud beta container clusters create example-cluster \ + --autoprovisioning-resource-manager-tags=my-project/key1=value1 + $ gcloud beta container clusters create example-cluster \ + --autoprovisioning-resource-manager-tags=12345/key1=value1,\ + 23456/key2=value2 + $ gcloud beta container clusters create example-cluster \ + --autoprovisioning-resource-manager-tags= + + All nodes in an Autopilot cluster or all auto-provisioned nodes in a + Standard cluster, including nodes that are resized or re-created, will + have the specified tags on the corresponding Instance object in the + Compute Engine API. You can reference these tags in network firewall + policy rules. For instructions, see + https://cloud.google.com/firewall/docs/use-tags-for-firewalls. + --autoscaling-profile=AUTOSCALING_PROFILE Set autoscaling behaviour, choices are 'optimize-utilization' and 'balanced'. Default is 'balanced'. @@ -1024,6 +1050,28 @@ FLAGS Clusters subscribed to 'stable' receive versions that are known to be stable and reliable in production. + --resource-manager-tags=[KEY=VALUE,...] + Applies the specified comma-separated resource manager tags that has + the GCE_FIREWALL purpose to all nodes in the new default node pool(s) + of a new cluster. + + Examples: + + $ gcloud beta container clusters create example-cluster \ + --resource-manager-tags=tagKeys/1234=tagValues/2345 + $ gcloud beta container clusters create example-cluster \ + --resource-manager-tags=my-project/key1=value1 + $ gcloud beta container clusters create example-cluster \ + --resource-manager-tags=12345/key1=value1,23456/key2=value2 + $ gcloud beta container clusters create example-cluster \ + --resource-manager-tags= + + All nodes, including nodes that are resized or re-created, will have + the specified tags on the corresponding Instance object in the Compute + Engine API. You can reference these tags in network firewall policy + rules. For instructions, see + https://cloud.google.com/firewall/docs/use-tags-for-firewalls. + --security-group=SECURITY_GROUP The name of the RBAC security group for use with Google security groups in Kubernetes RBAC diff --git a/gcloud/beta/container/clusters/create-auto b/gcloud/beta/container/clusters/create-auto index 1eb4e4aa1..fb7c302c7 100644 --- a/gcloud/beta/container/clusters/create-auto +++ b/gcloud/beta/container/clusters/create-auto @@ -5,6 +5,7 @@ NAME SYNOPSIS gcloud beta container clusters create-auto NAME [--async] [--autoprovisioning-network-tags=TAGS,[TAGS,...]] + [--autoprovisioning-resource-manager-tags=[KEY=VALUE,...]] [--boot-disk-kms-key=BOOT_DISK_KMS_KEY] [--cluster-ipv4-cidr=CLUSTER_IPV4_CIDR] [--cluster-secondary-range-name=NAME] @@ -71,6 +72,31 @@ FLAGS https://cloud.google.com/sdk/gcloud/reference/compute/firewall-rules/create for examples. + --autoprovisioning-resource-manager-tags=[KEY=VALUE,...] + Applies the specified comma-separated resource manager tags that has + the GCE_FIREWALL purpose to all nodes in the new Autopilot cluster or + all auto-provisioned nodes in the new Standard cluster. + + Examples: + + $ gcloud beta container clusters create-auto example-cluster \ + --autoprovisioning-resource-manager-tags=tagKeys/\ + 1234=tagValues/2345 + $ gcloud beta container clusters create-auto example-cluster \ + --autoprovisioning-resource-manager-tags=my-project/key1=value1 + $ gcloud beta container clusters create-auto example-cluster \ + --autoprovisioning-resource-manager-tags=12345/key1=value1,\ + 23456/key2=value2 + $ gcloud beta container clusters create-auto example-cluster \ + --autoprovisioning-resource-manager-tags= + + All nodes in an Autopilot cluster or all auto-provisioned nodes in a + Standard cluster, including nodes that are resized or re-created, will + have the specified tags on the corresponding Instance object in the + Compute Engine API. You can reference these tags in network firewall + policy rules. For instructions, see + https://cloud.google.com/firewall/docs/use-tags-for-firewalls. + --boot-disk-kms-key=BOOT_DISK_KMS_KEY The Customer Managed Encryption Key used to encrypt the boot disk attached to each node in the node pool. This should be of the form diff --git a/gcloud/beta/container/clusters/update b/gcloud/beta/container/clusters/update index c4b7445f3..5797ccf07 100644 --- a/gcloud/beta/container/clusters/update +++ b/gcloud/beta/container/clusters/update @@ -5,6 +5,7 @@ NAME SYNOPSIS gcloud beta container clusters update NAME (--autoprovisioning-network-tags=[TAGS,...] + | --autoprovisioning-resource-manager-tags=[KEY=VALUE,...] | --autoscaling-profile=AUTOSCALING_PROFILE | --clear-fleet-project | --complete-credential-rotation | --complete-ip-rotation | --database-encryption-key=DATABASE_ENCRYPTION_KEY @@ -127,6 +128,39 @@ REQUIRED FLAGS https://cloud.google.com/sdk/gcloud/reference/compute/firewall-rules/create for examples. + --autoprovisioning-resource-manager-tags=[KEY=VALUE,...] + For an Autopilot cluster, the specified comma-separated resource + manager tags that has the GCP_FIREWALL purpose replace the existing + tags on all nodes in the cluster. + + For a Standard cluster, the specified comma-separated resource + manager tags that has the GCE_FIREWALL purpose are applied to all + nodes in the new newly created auto-provisioned node pools. Existing + auto-provisioned node pools retain the tags that they had before the + update. To update tags on an existing auto-provisioned node pool, use + the node pool level flag '--resource-manager-tags'. + + Examples: + + $ gcloud beta container clusters update example-cluster \ + --autoprovisioning-resource-manager-tags=tagKeys/\ + 1234=tagValues/2345 + $ gcloud beta container clusters update example-cluster \ + --autoprovisioning-resource-manager-tags=my-project/key1=value1 + $ gcloud beta container clusters update example-cluster \ + --autoprovisioning-resource-manager-tags=12345/key1=value1,\ + 23456/key2=value2 + $ gcloud beta container clusters update example-cluster \ + --autoprovisioning-resource-manager-tags= + + All nodes in an Autopilot cluster or all newly created + auto-provisioned nodes in a Standard cluster, including nodes that + are resized or re-created, will have the specified tags on the + corresponding Instance object in the Compute Engine API. You can + reference these tags in network firewall policy rules. For + instructions, see + https://cloud.google.com/firewall/docs/use-tags-for-firewalls. + --autoscaling-profile=AUTOSCALING_PROFILE Set autoscaling behaviour, choices are 'optimize-utilization' and 'balanced'. Default is 'balanced'. diff --git a/gcloud/beta/container/node-pools/create b/gcloud/beta/container/node-pools/create index 90b469bb2..bc2cb654b 100644 --- a/gcloud/beta/container/node-pools/create +++ b/gcloud/beta/container/node-pools/create @@ -36,8 +36,9 @@ SYNOPSIS [--node-taints=[NODE_TAINT,...]] [--node-version=NODE_VERSION] [--num-nodes=NUM_NODES; default=3] [--placement-policy=PLACEMENT_POLICY] [--placement-type=PLACEMENT_TYPE] - [--preemptible] [--sandbox=[type=TYPE]] - [--shielded-integrity-monitoring] [--shielded-secure-boot] + [--preemptible] [--resource-manager-tags=[KEY=VALUE,...]] + [--sandbox=[type=TYPE]] [--shielded-integrity-monitoring] + [--shielded-secure-boot] [--sole-tenant-node-affinity-file=SOLE_TENANT_NODE_AFFINITY_FILE] [--spot] [--standard-rollout-policy=[batch-node-count=BATCH_NODE_COUNT, @@ -516,6 +517,27 @@ FLAGS https://cloud.google.com/kubernetes-engine/docs/preemptible-vm for more information on how to use Preemptible VMs with Kubernetes Engine. + --resource-manager-tags=[KEY=VALUE,...] + Applies the specified comma-separated resource manager tags that has + the GCE_FIREWALL purpose to all nodes in the new node pool. + + Examples: + + $ gcloud beta container node-pools create example-node-pool \ + --resource-manager-tags=tagKeys/1234=tagValues/2345 + $ gcloud beta container node-pools create example-node-pool \ + --resource-manager-tags=my-project/key1=value1 + $ gcloud beta container node-pools create example-node-pool \ + --resource-manager-tags=12345/key1=value1,23456/key2=value2 + $ gcloud beta container node-pools create example-node-pool \ + --resource-manager-tags= + + All nodes, including nodes that are resized or re-created, will have + the specified tags on the corresponding Instance object in the Compute + Engine API. You can reference these tags in network firewall policy + rules. For instructions, see + https://cloud.google.com/firewall/docs/use-tags-for-firewalls. + --sandbox=[type=TYPE] Enables the requested sandbox on all nodes in the node pool. diff --git a/gcloud/beta/container/node-pools/update b/gcloud/beta/container/node-pools/update index abef3c0da..aaa36b371 100644 --- a/gcloud/beta/container/node-pools/update +++ b/gcloud/beta/container/node-pools/update @@ -10,6 +10,7 @@ SYNOPSIS | --network-performance-configs=[PROPERTY=VALUE,...] | --node-labels=[NODE_LABEL,...] | --node-locations=ZONE,[ZONE,...] | --node-taints=[NODE_TAINT,...] + | --resource-manager-tags=[KEY=VALUE,...] | --system-config-from-file=SYSTEM_CONFIG_FROM_FILE | --tags=[TAG,...] | --windows-os-version=WINDOWS_OS_VERSION | --workload-metadata=WORKLOAD_METADATA | --enable-blue-green-upgrade @@ -145,6 +146,29 @@ REQUIRED FLAGS To read more about node-taints, see https://cloud.google.com/kubernetes-engine/docs/node-taints. + --resource-manager-tags=[KEY=VALUE,...] + Replaces all the user specified resource manager tags on all nodes in + an existing standard or auto-provisioned node pool in a Standard + cluster with the given comma-separated resource manager tags that has + the GCE_FIREWALL purpose. + + Examples: + + $ gcloud beta container node-pools update example-node-pool \ + --resource-manager-tags=tagKeys/1234=tagValues/2345 + $ gcloud beta container node-pools update example-node-pool \ + --resource-manager-tags=my-project/key1=value1 + $ gcloud beta container node-pools update example-node-pool \ + --resource-manager-tags=12345/key1=value1,23456/key2=value2 + $ gcloud beta container node-pools update example-node-pool \ + --resource-manager-tags= + + All nodes, including nodes that are resized or re-created, will have + the specified tags on the corresponding Instance object in the + Compute Engine API. You can reference these tags in network firewall + policy rules. For instructions, see + https://cloud.google.com/firewall/docs/use-tags-for-firewalls. + --system-config-from-file=SYSTEM_CONFIG_FROM_FILE Path of the YAML/JSON file that contains the node configuration, including Linux kernel parameters (sysctls) and kubelet configs. diff --git a/gcloud/beta/container/vmware/clusters/create b/gcloud/beta/container/vmware/clusters/create index b475954a0..743b782ce 100644 --- a/gcloud/beta/container/vmware/clusters/create +++ b/gcloud/beta/container/vmware/clusters/create @@ -176,7 +176,11 @@ REQUIRED FLAGS Use quote around the flag value to escape semicolon in the terminal. - Manual load balancer configuration + Manual load balancer configuration. + + With manual load balancing mode, DHCP is not supported. Specify static + IP addresses for cluster nodes instead. For more details, see + https://cloud.google.com/anthos/clusters/docs/on-prem/latest/how-to/manual-load-balance#setting_aside_node_ip_addresses. --control-plane-node-port=CONTROL_PLANE_NODE_PORT NodePort for control plane service. @@ -256,6 +260,10 @@ REQUIRED FLAGS --enable-dhcp Enable DHCP IP allocation for VMware user clusters. + While using DHCP, manual load balancing mode is not supported. + For more details, see + https://cloud.google.com/anthos/clusters/docs/on-prem/latest/how-to/manual-load-balance#setting_aside_node_ip_addresses. + Static IP configuration group At most one of these can be specified: diff --git a/gcloud/beta/functions/add-invoker-policy-binding b/gcloud/beta/functions/add-invoker-policy-binding index ae6fbfc2f..77f4ae5a3 100644 --- a/gcloud/beta/functions/add-invoker-policy-binding +++ b/gcloud/beta/functions/add-invoker-policy-binding @@ -4,16 +4,17 @@ NAME SYNOPSIS gcloud beta functions add-invoker-policy-binding (NAME : --region=REGION) - --member=PRINCIPAL [GCLOUD_WIDE_FLAG ...] + --member=PRINCIPAL [--gen2] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Adds the Cloud Run Invoker binding to the IAM policy of a Google - Cloud Function's underlying Cloud Run service. + (BETA) Adds an invoker role IAM policy binding that allows the specified + member to invoke the specified function. - This command applies to Cloud Functions (2nd gen) only. Cloud Functions - (2nd gen) currently requires the Cloud Run Invoke permission on the - underlying Cloud Run service to be able to call functions. This command - grants the given member permission to invoke the given 2nd gen function. + For Cloud Functions (1st gen), this adds the Cloud Functions Invoker + binding to the IAM policy of the specified function. + + For Cloud Functions (2nd gen), this adds the Cloud Run Invoker binding to + the IAM policy of the specified function's underlying Cloud Run service. EXAMPLES To add the invoker role policy binding for FUNCTION-1 for member MEMBER-1 @@ -70,6 +71,15 @@ REQUIRED FLAGS ◆ allAuthenticatedUsers - Special identifier that represents anyone who is authenticated with a Google account or a service account. +OPTIONAL FLAGS + --gen2 + If enabled, this command will use Cloud Functions (Second generation). + If disabled with --no-gen2, Cloud Functions (First generation) will be + used. If not specified, the value of this flag will be taken from the + functions/gen2 configuration property. If the functions/gen2 + configuration property is not set, defaults to looking up the given + function and using its generation. + 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/functions/remove-invoker-policy-binding b/gcloud/beta/functions/remove-invoker-policy-binding index 2267ad5b7..79f83d876 100644 --- a/gcloud/beta/functions/remove-invoker-policy-binding +++ b/gcloud/beta/functions/remove-invoker-policy-binding @@ -4,16 +4,19 @@ NAME SYNOPSIS gcloud beta functions remove-invoker-policy-binding - (NAME : --region=REGION) --member=PRINCIPAL [GCLOUD_WIDE_FLAG ...] + (NAME : --region=REGION) --member=PRINCIPAL [--gen2] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Removes the Cloud Run Invoker binding from the IAM policy of a - Google Cloud Function's underlying Cloud Run service. + (BETA) Removes the invoker role IAM policy binding that allows the + specified member to invoke the specified function. - This command applies to Cloud Functions (2nd gen) only. Cloud Functions - (2nd gen) currently requires the Cloud Run Invoke permission on the - underlying Cloud Run service to be able to call functions. This command - removes the given member permission to invoke the given 2nd gen function. + For Cloud Functions (1st gen), this removes the Cloud Functions Invoker + binding from the IAM policy of the specified function. + + For Cloud Functions (2nd gen), this removes the Cloud Run Invoker binding + from the IAM policy of the specified function's underlying Cloud Run + service. EXAMPLES To remove the invoker role policy binding for FUNCTION-1 for member @@ -74,6 +77,15 @@ REQUIRED FLAGS ◆ allAuthenticatedUsers - Special identifier that represents anyone who is authenticated with a Google account or a service account. +OPTIONAL FLAGS + --gen2 + If enabled, this command will use Cloud Functions (Second generation). + If disabled with --no-gen2, Cloud Functions (First generation) will be + used. If not specified, the value of this flag will be taken from the + functions/gen2 configuration property. If the functions/gen2 + configuration property is not set, defaults to looking up the given + function and using its generation. + 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/redis/clusters/create b/gcloud/beta/redis/clusters/create index 494a0e79d..33c869685 100644 --- a/gcloud/beta/redis/clusters/create +++ b/gcloud/beta/redis/clusters/create @@ -125,8 +125,10 @@ API REFERENCE API can be found at: https://cloud.google.com/memorystore/docs/redis/ NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud redis clusters create $ gcloud alpha redis clusters create diff --git a/gcloud/beta/redis/clusters/delete b/gcloud/beta/redis/clusters/delete index 2f8533c13..ee02514cf 100644 --- a/gcloud/beta/redis/clusters/delete +++ b/gcloud/beta/redis/clusters/delete @@ -71,8 +71,10 @@ API REFERENCE API can be found at: https://cloud.google.com/memorystore/docs/redis/ NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud redis clusters delete $ gcloud alpha redis clusters delete diff --git a/gcloud/beta/redis/clusters/describe b/gcloud/beta/redis/clusters/describe index 46bdfee87..242a2ab70 100644 --- a/gcloud/beta/redis/clusters/describe +++ b/gcloud/beta/redis/clusters/describe @@ -68,8 +68,10 @@ API REFERENCE API can be found at: https://cloud.google.com/memorystore/docs/redis/ NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud redis clusters describe $ gcloud alpha redis clusters describe diff --git a/gcloud/beta/redis/clusters/get-cluster-certificate-authority b/gcloud/beta/redis/clusters/get-cluster-certificate-authority index 10f9dd09e..7ec77f430 100644 --- a/gcloud/beta/redis/clusters/get-cluster-certificate-authority +++ b/gcloud/beta/redis/clusters/get-cluster-certificate-authority @@ -69,8 +69,10 @@ API REFERENCE API can be found at: https://cloud.google.com/memorystore/docs/redis/ NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud redis clusters get-cluster-certificate-authority $ gcloud alpha redis clusters get-cluster-certificate-authority diff --git a/gcloud/beta/redis/clusters/help b/gcloud/beta/redis/clusters/help index bd82166b9..575bef057 100644 --- a/gcloud/beta/redis/clusters/help +++ b/gcloud/beta/redis/clusters/help @@ -35,8 +35,10 @@ COMMANDS (BETA) Update Memorystore Cluster for Redis instance. 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 redis clusters $ gcloud alpha redis clusters diff --git a/gcloud/beta/redis/clusters/list b/gcloud/beta/redis/clusters/list index 953ec3084..cc5b68e00 100644 --- a/gcloud/beta/redis/clusters/list +++ b/gcloud/beta/redis/clusters/list @@ -81,8 +81,10 @@ API REFERENCE API can be found at: https://cloud.google.com/memorystore/docs/redis/ NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud redis clusters list $ gcloud alpha redis clusters list diff --git a/gcloud/beta/redis/clusters/update b/gcloud/beta/redis/clusters/update index 89e2e3885..3340c8634 100644 --- a/gcloud/beta/redis/clusters/update +++ b/gcloud/beta/redis/clusters/update @@ -79,8 +79,10 @@ API REFERENCE API can be found at: https://cloud.google.com/memorystore/docs/redis/ NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud redis clusters update $ gcloud alpha redis clusters update diff --git a/gcloud/beta/services/api-keys/update b/gcloud/beta/services/api-keys/update index 8c76d5b06..7f0e55335 100644 --- a/gcloud/beta/services/api-keys/update +++ b/gcloud/beta/services/api-keys/update @@ -66,14 +66,12 @@ EXAMPLES The content of 'my-flags.yaml' is as following: - --api-target: - service: - - "foo.service.com" + service: "foo.service.com" - --api-target: - service: - - "bar.service.com" + service: "bar.service.com" methods: - - "foomethod" - - "barmethod" + - "foomethod" + - "barmethod" POSITIONAL ARGUMENTS Key resource - The name of the key to update. The arguments in this group diff --git a/gcloud/beta/workstations/configs/create b/gcloud/beta/workstations/configs/create index 446afefff..3dbaff358 100644 --- a/gcloud/beta/workstations/configs/create +++ b/gcloud/beta/workstations/configs/create @@ -21,8 +21,10 @@ SYNOPSIS [--pd-reclaim-policy=PD_RECLAIM_POLICY; default="delete"] [--pool-size=POOL_SIZE] [--replica-zones=[REPLICA_ZONES,...]] [--running-timeout=RUNNING_TIMEOUT; default=7200] - [--service-account=SERVICE_ACCOUNT] [--shielded-integrity-monitoring] - [--shielded-secure-boot] [--shielded-vtpm] + [--service-account=SERVICE_ACCOUNT] + [--service-account-scopes=[SERVICE_ACCOUNT_SCOPES,...]] + [--shielded-integrity-monitoring] [--shielded-secure-boot] + [--shielded-vtpm] [--accelerator-count=ACCELERATOR_COUNT : --accelerator-type=ACCELERATOR_TYPE] [--container-custom-image=CONTAINER_CUSTOM_IMAGE @@ -212,6 +214,12 @@ FLAGS to pull the specified container image. If not set, VMs will run without a service account, in which case the image must be publicly accessible. + --service-account-scopes=[SERVICE_ACCOUNT_SCOPES,...] + Scopes to grant to the service_account. Various scopes are + automatically added based on feature usage. When specified, users of + workstations under this configuration must have + iam.serviceAccounts.actAs on the service account. + --shielded-integrity-monitoring Default value is false. If set, instances will have integrity monitoring enabled. diff --git a/gcloud/beta/workstations/configs/update b/gcloud/beta/workstations/configs/update index e1653fdfb..7653e62cd 100644 --- a/gcloud/beta/workstations/configs/update +++ b/gcloud/beta/workstations/configs/update @@ -16,6 +16,7 @@ SYNOPSIS [--labels=[LABELS,...]] [--machine-type=MACHINE_TYPE] [--network-tags=[NETWORK_TAGS,...]] [--pool-size=POOL_SIZE] [--running-timeout=RUNNING_TIMEOUT] [--service-account=SERVICE_ACCOUNT] + [--service-account-scopes=[SERVICE_ACCOUNT_SCOPES,...]] [--shielded-integrity-monitoring] [--shielded-secure-boot] [--shielded-vtpm] [--accelerator-count=ACCELERATOR_COUNT @@ -172,6 +173,12 @@ FLAGS to pull the specified container image. If not set, VMs will run without a service account, in which case the image must be publicly accessible. + --service-account-scopes=[SERVICE_ACCOUNT_SCOPES,...] + Scopes to grant to the service_account. Various scopes are + automatically added based on feature usage. When specified, users of + workstations under this configuration must have + iam.serviceAccounts.actAs on the service account. + --shielded-integrity-monitoring Default value is false. If set, instances will have integrity monitoring enabled. diff --git a/gcloud/compute/disks/create b/gcloud/compute/disks/create index 31b102139..644f7b40d 100644 --- a/gcloud/compute/disks/create +++ b/gcloud/compute/disks/create @@ -78,8 +78,8 @@ FLAGS their boot disks. See the descriptions of supported features at: https://cloud.google.com/compute/docs/images/create-delete-deprecate-private-images#guest-os-features. GUEST_OS_FEATURE must be one of: GVNIC, MULTI_IP_SUBNET, SEV_CAPABLE, - SEV_LIVE_MIGRATABLE, SEV_SNP_CAPABLE, UEFI_COMPATIBLE, - VIRTIO_SCSI_MULTIQUEUE, WINDOWS. + SEV_LIVE_MIGRATABLE, SEV_LIVE_MIGRATABLE_V2, SEV_SNP_CAPABLE, + UEFI_COMPATIBLE, VIRTIO_SCSI_MULTIQUEUE, WINDOWS. --labels=[KEY=VALUE,...] List of label KEY=VALUE pairs to add. diff --git a/gcloud/compute/images/create b/gcloud/compute/images/create index a41b45d46..ceb86600f 100644 --- a/gcloud/compute/images/create +++ b/gcloud/compute/images/create @@ -144,8 +144,8 @@ OPTIONAL FLAGS their boot disks. See the descriptions of supported features at: https://cloud.google.com/compute/docs/images/create-delete-deprecate-private-images#guest-os-features. GUEST_OS_FEATURE must be one of: GVNIC, MULTI_IP_SUBNET, SEV_CAPABLE, - SEV_LIVE_MIGRATABLE, SEV_SNP_CAPABLE, UEFI_COMPATIBLE, - VIRTIO_SCSI_MULTIQUEUE, WINDOWS. + SEV_LIVE_MIGRATABLE, SEV_LIVE_MIGRATABLE_V2, SEV_SNP_CAPABLE, + UEFI_COMPATIBLE, VIRTIO_SCSI_MULTIQUEUE, WINDOWS. --key-exchange-key-file=[KEK_VALUE,...] Comma-separated list of file paths that point to X.509 certificates in diff --git a/gcloud/compute/instance-templates/create b/gcloud/compute/instance-templates/create index 6a22742f4..69abf4783 100644 --- a/gcloud/compute/instance-templates/create +++ b/gcloud/compute/instance-templates/create @@ -7,6 +7,7 @@ SYNOPSIS [--accelerator=[count=COUNT],[type=TYPE]] [--no-boot-disk-auto-delete] [--boot-disk-device-name=BOOT_DISK_DEVICE_NAME] [--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] [--configure-disk=[PROPERTY=VALUE,...]] @@ -107,6 +108,10 @@ FLAGS of I/O operations per second that the disk can handle. Value must be between 10,000 and 120,000. + --boot-disk-provisioned-throughput=BOOT_DISK_PROVISIONED_THROUGHPUT + Indicates how much throughput to provision for the disk. This sets the + number of throughput mb per second that the disk can handle. + --boot-disk-size=BOOT_DISK_SIZE The size of the boot disk. This option can only be specified if a new boot disk is being created (as opposed to mounting an existing diff --git a/gcloud/compute/instance-templates/create-with-container b/gcloud/compute/instance-templates/create-with-container index 7914509e0..bc64ace61 100644 --- a/gcloud/compute/instance-templates/create-with-container +++ b/gcloud/compute/instance-templates/create-with-container @@ -7,6 +7,7 @@ SYNOPSIS [--no-boot-disk-auto-delete] [--boot-disk-device-name=BOOT_DISK_DEVICE_NAME] [--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] [--container-arg=CONTAINER_ARG] [--container-command=CONTAINER_COMMAND] @@ -94,6 +95,10 @@ FLAGS of I/O operations per second that the disk can handle. Value must be between 10,000 and 120,000. + --boot-disk-provisioned-throughput=BOOT_DISK_PROVISIONED_THROUGHPUT + Indicates how much throughput to provision for the disk. This sets the + number of throughput mb per second that the disk can handle. + --boot-disk-size=BOOT_DISK_SIZE The size of the boot disk. This option can only be specified if a new boot disk is being created (as opposed to mounting an existing diff --git a/gcloud/compute/instances/bulk/create b/gcloud/compute/instances/bulk/create index 28fda2b90..ab9e0149e 100644 --- a/gcloud/compute/instances/bulk/create +++ b/gcloud/compute/instances/bulk/create @@ -10,6 +10,7 @@ SYNOPSIS [--no-boot-disk-auto-delete] [--boot-disk-device-name=BOOT_DISK_DEVICE_NAME] [--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] [--count=COUNT] [--create-disk=[PROPERTY=VALUE,...]] [--description=DESCRIPTION] @@ -157,6 +158,10 @@ OPTIONAL FLAGS of I/O operations per second that the disk can handle. Value must be between 10,000 and 120,000. + --boot-disk-provisioned-throughput=BOOT_DISK_PROVISIONED_THROUGHPUT + Indicates how much throughput to provision for the disk. This sets the + number of throughput mb per second that the disk can handle. + --boot-disk-size=BOOT_DISK_SIZE The size of the boot disk. This option can only be specified if a new boot disk is being created (as opposed to mounting an existing diff --git a/gcloud/compute/instances/create b/gcloud/compute/instances/create index 629f722f0..71fa007df 100644 --- a/gcloud/compute/instances/create +++ b/gcloud/compute/instances/create @@ -8,6 +8,7 @@ SYNOPSIS [--no-boot-disk-auto-delete] [--boot-disk-device-name=BOOT_DISK_DEVICE_NAME] [--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] [--create-disk=[PROPERTY=VALUE,...]] [--csek-key-file=FILE] @@ -160,6 +161,10 @@ FLAGS of I/O operations per second that the disk can handle. Value must be between 10,000 and 120,000. + --boot-disk-provisioned-throughput=BOOT_DISK_PROVISIONED_THROUGHPUT + Indicates how much throughput to provision for the disk. This sets the + number of throughput mb per second that the disk can handle. + --boot-disk-size=BOOT_DISK_SIZE The size of the boot disk. This option can only be specified if a new boot disk is being created (as opposed to mounting an existing diff --git a/gcloud/compute/instances/create-with-container b/gcloud/compute/instances/create-with-container index 0390f00ad..1b2a042f5 100644 --- a/gcloud/compute/instances/create-with-container +++ b/gcloud/compute/instances/create-with-container @@ -8,6 +8,7 @@ SYNOPSIS [--no-boot-disk-auto-delete] [--boot-disk-device-name=BOOT_DISK_DEVICE_NAME] [--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] [--container-arg=CONTAINER_ARG] [--container-command=CONTAINER_COMMAND] @@ -117,6 +118,10 @@ FLAGS of I/O operations per second that the disk can handle. Value must be between 10,000 and 120,000. + --boot-disk-provisioned-throughput=BOOT_DISK_PROVISIONED_THROUGHPUT + Indicates how much throughput to provision for the disk. This sets the + number of throughput mb per second that the disk can handle. + --boot-disk-size=BOOT_DISK_SIZE The size of the boot disk. This option can only be specified if a new boot disk is being created (as opposed to mounting an existing diff --git a/gcloud/compute/public-delegated-prefixes/create b/gcloud/compute/public-delegated-prefixes/create index b0732b533..cf0311107 100644 --- a/gcloud/compute/public-delegated-prefixes/create +++ b/gcloud/compute/public-delegated-prefixes/create @@ -3,8 +3,9 @@ NAME public delegated prefix SYNOPSIS - gcloud compute public-delegated-prefixes create NAME - --public-advertised-prefix=PUBLIC_ADVERTISED_PREFIX --range=RANGE + gcloud compute public-delegated-prefixes create NAME --range=RANGE + (--public-advertised-prefix=PUBLIC_ADVERTISED_PREFIX + | --public-delegated-prefix=PUBLIC_DELEGATED_PREFIX) [--description=DESCRIPTION] [--enable-live-migration] [--global | --region=REGION] [GCLOUD_WIDE_FLAG ...] @@ -20,14 +21,20 @@ POSITIONAL ARGUMENTS Name of the public delegated prefix to operate on. REQUIRED FLAGS - --public-advertised-prefix=PUBLIC_ADVERTISED_PREFIX - Public advertised prefix that this delegated prefix is created from. - --range=RANGE IPv4 range from this public delegated prefix that should be delegated, in CIDR format. It must be smaller than parent public advertised prefix range. + Exactly one of these must be specified: + + --public-advertised-prefix=PUBLIC_ADVERTISED_PREFIX + Public advertised prefix that this delegated prefix is created from. + + --public-delegated-prefix=PUBLIC_DELEGATED_PREFIX + Regional Public delegated prefix that this delegated prefix is + created from. + OPTIONAL FLAGS --description=DESCRIPTION Description of this public delegated prefix. diff --git a/gcloud/compute/tpus/tpu-vm/update b/gcloud/compute/tpus/tpu-vm/update index 17c8ae0ce..6d935dee1 100644 --- a/gcloud/compute/tpus/tpu-vm/update +++ b/gcloud/compute/tpus/tpu-vm/update @@ -3,7 +3,7 @@ NAME SYNOPSIS gcloud compute tpus tpu-vm update (TPU : --zone=ZONE) [--async] - [--description=DESCRIPTION] [GCLOUD_WIDE_FLAG ...] + [--description=DESCRIPTION] [--internal-ips] [GCLOUD_WIDE_FLAG ...] DESCRIPTION Update a Cloud TPU VM node. @@ -57,6 +57,11 @@ FLAGS --description=DESCRIPTION Text description of the TPU. + --internal-ips + Indicate that the IP addresses for the node should be internal. The + default is that external IP addresses will be associated with the TPU + workers. + 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/clusters/create b/gcloud/container/clusters/create index 118e8e1bc..ba8eedae3 100644 --- a/gcloud/container/clusters/create +++ b/gcloud/container/clusters/create @@ -24,7 +24,7 @@ SYNOPSIS [--disk-type=DISK_TYPE] [--enable-autorepair] [--no-enable-autoupgrade] [--enable-cloud-logging] [--enable-cloud-monitoring] [--enable-cloud-run-alpha] [--enable-confidential-nodes] - [--enable-cost-allocation] [--enable-dataplane-v2] + [--enable-cost-allocation] [--enable-dataplane-v2] [--enable-fleet] [--enable-google-cloud-access] [--enable-gvnic] [--enable-identity-service] [--enable-image-streaming] [--enable-intra-node-visibility] [--enable-ip-alias] @@ -35,10 +35,10 @@ SYNOPSIS [--enable-multi-networking] [--enable-network-policy] [--enable-service-externalips] [--enable-shielded-nodes] [--enable-stackdriver-kubernetes] [--enable-vertical-pod-autoscaling] - [--gateway-api=GATEWAY_API] [--image-type=IMAGE_TYPE] - [--ipv6-access-type=IPV6_ACCESS_TYPE] [--issue-client-certificate] - [--labels=[KEY=VALUE,...]] [--logging=[COMPONENT,...]] - [--logging-variant=LOGGING_VARIANT] + [--fleet-project=PROJECT_ID_OR_NUMBER] [--gateway-api=GATEWAY_API] + [--image-type=IMAGE_TYPE] [--ipv6-access-type=IPV6_ACCESS_TYPE] + [--issue-client-certificate] [--labels=[KEY=VALUE,...]] + [--logging=[COMPONENT,...]] [--logging-variant=LOGGING_VARIANT] [--machine-type=MACHINE_TYPE, -m MACHINE_TYPE] [--max-nodes-per-pool=MAX_NODES_PER_POOL] [--max-pods-per-node=MAX_PODS_PER_NODE] @@ -460,6 +460,12 @@ FLAGS Enables the new eBPF dataplane for GKE clusters that is required for network security, scalability and visibility features. + --enable-fleet + Set cluster project as the fleet host project. This will register the + cluster to the same project. To register the cluster to a fleet in a + different project, please use --fleet-project=FLEET_HOST_PROJECT. + Example: $ gcloud container clusters create --enable-fleet + --enable-google-cloud-access When you enable Google Cloud Access, any public IP addresses owned by Google Cloud can reach the public control plane endpoint of your @@ -564,6 +570,13 @@ FLAGS --enable-vertical-pod-autoscaling Enable vertical pod autoscaling for a cluster. + --fleet-project=PROJECT_ID_OR_NUMBER + Sets fleet host project for the cluster. If specified, the current + cluster will be registered as a fleet membership under the fleet host + project. + + Example: $ gcloud container clusters create --fleet-project=my-project + --gateway-api=GATEWAY_API Enables GKE Gateway controller in this cluster. The value of the flag specifies which Open Source Gateway API release channel will be used to diff --git a/gcloud/container/clusters/create-auto b/gcloud/container/clusters/create-auto index 432279fba..f1b485f30 100644 --- a/gcloud/container/clusters/create-auto +++ b/gcloud/container/clusters/create-auto @@ -13,14 +13,16 @@ SYNOPSIS [--create-subnetwork=[KEY=VALUE,...]] [--database-encryption-key=DATABASE_ENCRYPTION_KEY] [--dataplane-v2-observability-mode=DATAPLANE_V2_OBSERVABILITY_MODE] - [--enable-backup-restore] [--enable-google-cloud-access] + [--enable-backup-restore] [--enable-fleet] + [--enable-google-cloud-access] [--enable-kubernetes-unstable-apis=API,[API,...]] - [--enable-master-global-access] [--logging=[COMPONENT,...]] - [--monitoring=[COMPONENT,...]] [--network=NETWORK] - [--private-endpoint-subnetwork=NAME] [--release-channel=CHANNEL] - [--security-group=SECURITY_GROUP] [--security-posture=SECURITY_POSTURE] - [--services-ipv4-cidr=CIDR] [--services-secondary-range-name=NAME] - [--subnetwork=SUBNETWORK] [--workload-policies=WORKLOAD_POLICIES] + [--enable-master-global-access] [--fleet-project=PROJECT_ID_OR_NUMBER] + [--logging=[COMPONENT,...]] [--monitoring=[COMPONENT,...]] + [--network=NETWORK] [--private-endpoint-subnetwork=NAME] + [--release-channel=CHANNEL] [--security-group=SECURITY_GROUP] + [--security-posture=SECURITY_POSTURE] [--services-ipv4-cidr=CIDR] + [--services-secondary-range-name=NAME] [--subnetwork=SUBNETWORK] + [--workload-policies=WORKLOAD_POLICIES] [--workload-vulnerability-scanning=WORKLOAD_VULNERABILITY_SCANNING] [--enable-master-authorized-networks --master-authorized-networks=NETWORK,[NETWORK,...]] @@ -195,6 +197,12 @@ FLAGS To learn more, see the Backup for GKE overview: https://cloud.google.com/kubernetes-engine/docs/add-on/backup-for-gke/concepts/backup-for-gke. + --enable-fleet + Set cluster project as the fleet host project. This will register the + cluster to the same project. To register the cluster to a fleet in a + different project, please use --fleet-project=FLEET_HOST_PROJECT. + Example: $ gcloud container clusters create-auto --enable-fleet + --enable-google-cloud-access When you enable Google Cloud Access, any public IP addresses owned by Google Cloud can reach the public control plane endpoint of your @@ -210,6 +218,14 @@ FLAGS endpoint from any Google Cloud region or on-premises environment regardless of the private cluster's region. + --fleet-project=PROJECT_ID_OR_NUMBER + Sets fleet host project for the cluster. If specified, the current + cluster will be registered as a fleet membership under the fleet host + project. + + Example: $ gcloud container clusters create-auto + --fleet-project=my-project + --logging=[COMPONENT,...] Set the components that have logging enabled. Valid component values are: SYSTEM, WORKLOAD, API_SERVER, CONTROLLER_MANAGER, SCHEDULER, NONE diff --git a/gcloud/container/clusters/update b/gcloud/container/clusters/update index 996d770b9..5cd910d1f 100644 --- a/gcloud/container/clusters/update +++ b/gcloud/container/clusters/update @@ -5,22 +5,23 @@ NAME SYNOPSIS gcloud container clusters update NAME (--autoprovisioning-network-tags=[TAGS,...] - | --autoscaling-profile=AUTOSCALING_PROFILE + | --autoscaling-profile=AUTOSCALING_PROFILE | --clear-fleet-project | --complete-credential-rotation | --complete-ip-rotation | --database-encryption-key=DATABASE_ENCRYPTION_KEY | --disable-database-encryption | --disable-default-snat | --disable-workload-identity | --enable-autoscaling - | --enable-cost-allocation | --enable-google-cloud-access - | --enable-identity-service | --enable-image-streaming - | --enable-intra-node-visibility + | --enable-cost-allocation | --enable-fleet + | --enable-google-cloud-access | --enable-identity-service + | --enable-image-streaming | --enable-intra-node-visibility | --enable-kubernetes-unstable-apis=API,[API,...] | --enable-l4-ilb-subsetting | --enable-legacy-authorization | --enable-master-authorized-networks | --enable-master-global-access | --enable-network-policy | --enable-private-endpoint | --enable-service-externalips | --enable-shielded-nodes | --enable-stackdriver-kubernetes | --enable-vertical-pod-autoscaling - | --gateway-api=GATEWAY_API | --generate-password - | --logging-variant=LOGGING_VARIANT | --maintenance-window=START_TIME + | --fleet-project=PROJECT_ID_OR_NUMBER | --gateway-api=GATEWAY_API + | --generate-password | --logging-variant=LOGGING_VARIANT + | --maintenance-window=START_TIME | --network-performance-configs=[PROPERTY1=VALUE1,...] | --node-locations=ZONE,[ZONE,...] | --notification-config=[pubsub=ENABLED|DISABLED, @@ -124,6 +125,10 @@ REQUIRED FLAGS Set autoscaling behaviour, choices are 'optimize-utilization' and 'balanced'. Default is 'balanced'. + --clear-fleet-project + Remove the cluster from current fleet host project. Example: $ gcloud + container clusters update --clear-fleet-project + --complete-credential-rotation Complete the IP and credential rotation for this cluster. For example: @@ -207,6 +212,12 @@ REQUIRED FLAGS Use --no-enable-cost-allocation to disable this feature. + --enable-fleet + Set cluster project as the fleet host project. This will register the + cluster to the same project. To register the cluster to a fleet in a + different project, please use --fleet-project=FLEET_HOST_PROJECT. + Example: $ gcloud container clusters update --enable-fleet + --enable-google-cloud-access When you enable Google Cloud Access, any public IP addresses owned by Google Cloud can reach the public control plane endpoint of your @@ -303,6 +314,14 @@ REQUIRED FLAGS --enable-vertical-pod-autoscaling Enable vertical pod autoscaling for a cluster. + --fleet-project=PROJECT_ID_OR_NUMBER + Sets fleet host project for the cluster. If specified, the current + cluster will be registered as a fleet membership under the fleet host + project. + + Example: $ gcloud container clusters update + --fleet-project=my-project + --gateway-api=GATEWAY_API Enables GKE Gateway controller in this cluster. The value of the flag specifies which Open Source Gateway API release channel will be used diff --git a/gcloud/container/vmware/clusters/create b/gcloud/container/vmware/clusters/create index 7ab64bb12..1a298a7ed 100644 --- a/gcloud/container/vmware/clusters/create +++ b/gcloud/container/vmware/clusters/create @@ -176,7 +176,11 @@ REQUIRED FLAGS Use quote around the flag value to escape semicolon in the terminal. - Manual load balancer configuration + Manual load balancer configuration. + + With manual load balancing mode, DHCP is not supported. Specify static + IP addresses for cluster nodes instead. For more details, see + https://cloud.google.com/anthos/clusters/docs/on-prem/latest/how-to/manual-load-balance#setting_aside_node_ip_addresses. --control-plane-node-port=CONTROL_PLANE_NODE_PORT NodePort for control plane service. @@ -256,6 +260,10 @@ REQUIRED FLAGS --enable-dhcp Enable DHCP IP allocation for VMware user clusters. + While using DHCP, manual load balancing mode is not supported. + For more details, see + https://cloud.google.com/anthos/clusters/docs/on-prem/latest/how-to/manual-load-balance#setting_aside_node_ip_addresses. + Static IP configuration group At most one of these can be specified: diff --git a/gcloud/edge-cloud/container/get-server-config b/gcloud/edge-cloud/container/get-server-config new file mode 100644 index 000000000..7fdc05f41 --- /dev/null +++ b/gcloud/edge-cloud/container/get-server-config @@ -0,0 +1,55 @@ +NAME + gcloud edge-cloud container get-server-config - get server config + +SYNOPSIS + gcloud edge-cloud container get-server-config [--location=LOCATION] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + gcloud edge-cloud container get-server-config gets the server configuration + for an Edge Container location. This configuration includes the default + cluster version, the supported cluster versions and version configuration + for each release channel. + +EXAMPLES + To get server config in region us-central1, run: + + $ gcloud edge-cloud container get-server-config \ + --location=us-central1 + +FLAGS + Location resource - The location of the server configuration. This + represents a Cloud resource. (NOTE) Some attributes are not given + arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument --location on the command line with a fully + specified name; + ◆ set the property edge_container/location 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 the property edge_container/location. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the edgecontainer/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/edge-cloud + +NOTES + This variant is also available: + + $ gcloud alpha edge-cloud container get-server-config + diff --git a/gcloud/edge-cloud/container/help b/gcloud/edge-cloud/container/help index ab90f6af4..04ee11b98 100644 --- a/gcloud/edge-cloud/container/help +++ b/gcloud/edge-cloud/container/help @@ -2,7 +2,7 @@ NAME gcloud edge-cloud container - manage Edge Container resources SYNOPSIS - gcloud edge-cloud container GROUP [GCLOUD_WIDE_FLAG ...] + gcloud edge-cloud container GROUP | COMMAND [GCLOUD_WIDE_FLAG ...] DESCRIPTION Manage Edge Container resources. @@ -34,6 +34,12 @@ GROUPS zones Inspect Edge Container zones. +COMMANDS + COMMAND is one of the following: + + get-server-config + Get server config. + NOTES This variant is also available: diff --git a/gcloud/functions/add-invoker-policy-binding b/gcloud/functions/add-invoker-policy-binding index 41c91836e..ba33777c1 100644 --- a/gcloud/functions/add-invoker-policy-binding +++ b/gcloud/functions/add-invoker-policy-binding @@ -4,16 +4,17 @@ NAME SYNOPSIS gcloud functions add-invoker-policy-binding (NAME : --region=REGION) - --member=PRINCIPAL [GCLOUD_WIDE_FLAG ...] + --member=PRINCIPAL [--gen2] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - Adds the Cloud Run Invoker binding to the IAM policy of a Google Cloud - Function's underlying Cloud Run service. + Adds an invoker role IAM policy binding that allows the specified member to + invoke the specified function. - This command applies to Cloud Functions (2nd gen) only. Cloud Functions - (2nd gen) currently requires the Cloud Run Invoke permission on the - underlying Cloud Run service to be able to call functions. This command - grants the given member permission to invoke the given 2nd gen function. + For Cloud Functions (1st gen), this adds the Cloud Functions Invoker + binding to the IAM policy of the specified function. + + For Cloud Functions (2nd gen), this adds the Cloud Run Invoker binding to + the IAM policy of the specified function's underlying Cloud Run service. EXAMPLES To add the invoker role policy binding for FUNCTION-1 for member MEMBER-1 @@ -70,6 +71,15 @@ REQUIRED FLAGS ◆ allAuthenticatedUsers - Special identifier that represents anyone who is authenticated with a Google account or a service account. +OPTIONAL FLAGS + --gen2 + If enabled, this command will use Cloud Functions (Second generation). + If disabled with --no-gen2, Cloud Functions (First generation) will be + used. If not specified, the value of this flag will be taken from the + functions/gen2 configuration property. If the functions/gen2 + configuration property is not set, defaults to looking up the given + function and using its generation. + 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/functions/remove-invoker-policy-binding b/gcloud/functions/remove-invoker-policy-binding index 3e4b5e7dc..1a26ac8bc 100644 --- a/gcloud/functions/remove-invoker-policy-binding +++ b/gcloud/functions/remove-invoker-policy-binding @@ -4,16 +4,18 @@ NAME SYNOPSIS gcloud functions remove-invoker-policy-binding (NAME : --region=REGION) - --member=PRINCIPAL [GCLOUD_WIDE_FLAG ...] + --member=PRINCIPAL [--gen2] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - Removes the Cloud Run Invoker binding from the IAM policy of a Google Cloud - Function's underlying Cloud Run service. + Removes the invoker role IAM policy binding that allows the specified + member to invoke the specified function. - This command applies to Cloud Functions (2nd gen) only. Cloud Functions - (2nd gen) currently requires the Cloud Run Invoke permission on the - underlying Cloud Run service to be able to call functions. This command - removes the given member permission to invoke the given 2nd gen function. + For Cloud Functions (1st gen), this removes the Cloud Functions Invoker + binding from the IAM policy of the specified function. + + For Cloud Functions (2nd gen), this removes the Cloud Run Invoker binding + from the IAM policy of the specified function's underlying Cloud Run + service. EXAMPLES To remove the invoker role policy binding for FUNCTION-1 for member @@ -74,6 +76,15 @@ REQUIRED FLAGS ◆ allAuthenticatedUsers - Special identifier that represents anyone who is authenticated with a Google account or a service account. +OPTIONAL FLAGS + --gen2 + If enabled, this command will use Cloud Functions (Second generation). + If disabled with --no-gen2, Cloud Functions (First generation) will be + used. If not specified, the value of this flag will be taken from the + functions/gen2 configuration property. If the functions/gen2 + configuration property is not set, defaults to looking up the given + function and using its generation. + 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/redis/clusters/create b/gcloud/redis/clusters/create new file mode 100644 index 000000000..70fec7075 --- /dev/null +++ b/gcloud/redis/clusters/create @@ -0,0 +1,133 @@ +NAME + gcloud redis clusters create - create a new Memorystore for Redis Cluster + instance + +SYNOPSIS + gcloud redis clusters create (CLUSTER : --region=REGION) --network=NETWORK + --shard-count=SHARD_COUNT [--async] [--auth-mode=AUTH_MODE] + [--replica-count=REPLICA_COUNT] + [--transit-encryption-mode=TRANSIT_ENCRYPTION_MODE] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Create a new Memorystore for Redis Cluster instance, and uses Private + Service Connect service connectivity automation to automate connectivity + for instances. + + This command can fail for the following reasons: + ▪ A cluster with the same name already exists. + ▪ The active account does not have permission to create clusters. + ▪ Some required APIs not enabled yet. + ▪ No connection policy defined yet on the network and in the region a + cluster will be created. + ▪ Miss the steps for creating and configuring a service account (to + grant permissions) in both host project and service project, if a + shared VPC network is used. + + Refer to + https://cloud.google.com/memorystore/docs/cluster/networking#prerequisites_required_before_creating_a_cluster + for prerequisites. + +EXAMPLES + To create a cluster with name my-redis-cluster in region us-central1 with 3 + shards and with a discovery endpoint created on network "default", run: + + $ gcloud redis clusters create my-redis-cluster \ + --region=us-central1 --shard-count=3 \ + --network=projects/NETWORK_PROJECT_ID/global/networks/default + +POSITIONAL ARGUMENTS + Cluster resource - Arguments and flags that specify the cluster you want + to create. Your cluster ID must be 1 to 63 characters and use only + lowercase letters, numbers, or hyphens. It must start with a lowercase + letter and end with a lowercase letter or number. The arguments in this + group can be used to specify the attributes of this resource. (NOTE) Some + attributes are not given arguments in this group but can be set in other + ways. + + To set the project attribute: + ◆ provide the argument cluster on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + CLUSTER + ID of the cluster or fully qualified identifier for the cluster. + + To set the cluster attribute: + ▸ provide the argument cluster on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The name of the Redis region of the cluster. Overrides the default + redis/region property value for this command invocation. + + To set the region attribute: + ▸ provide the argument cluster on the command line with a fully + specified name; + ▸ provide the argument --region on the command line; + ▸ set the property redis/region. + +REQUIRED FLAGS + --network=NETWORK + The network used to create your instance. It must use the format: + projects/NETWORK_PROJECT_ID/global/networks/NETWORK_ID. The network ID + used here must match the network ID used by the service connection + policy. Otherwise, the create operation fails + + --shard-count=SHARD_COUNT + The shard count of the cluster. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --auth-mode=AUTH_MODE + Available authorization mode of a Redis cluster. AUTH_MODE must be one + of: + + disabled + Authorization is disabled for the cluster. + + iam-auth + IAM basic authorization is enabled for the cluster. + + --replica-count=REPLICA_COUNT + The replica count of each shard. + + --transit-encryption-mode=TRANSIT_ENCRYPTION_MODE + Transit encryption mode used for the Redis cluster. If not provided, + encryption is disabled for the cluster. TRANSIT_ENCRYPTION_MODE must be + one of: + + disabled + In-transit encryption is disabled for the cluster. + + server-authentication + The cluster uses server managed encryption for in-transit + encryption. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the redis/v1 API. The full documentation for this API can + be found at: https://cloud.google.com/memorystore/docs/redis/ + +NOTES + These variants are also available: + + $ gcloud alpha redis clusters create + + $ gcloud beta redis clusters create + diff --git a/gcloud/redis/clusters/delete b/gcloud/redis/clusters/delete new file mode 100644 index 000000000..b31eee9b8 --- /dev/null +++ b/gcloud/redis/clusters/delete @@ -0,0 +1,79 @@ +NAME + gcloud redis clusters delete - delete a Memorystore for Redis Cluster + instance + +SYNOPSIS + gcloud redis clusters delete (CLUSTER : --region=REGION) [--async] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Delete a Memorystore for Redis Cluster instance. + + This command can fail for the following reasons: + ▪ The cluster specified does not exist. + ▪ The active account does not have permission to access the given + cluster. + +EXAMPLES + To delete a cluster with the name my-redis-cluster in your default region, + run: + + $ gcloud redis clusters delete my-redis-cluster + +POSITIONAL ARGUMENTS + Cluster resource - Arguments and flags that specify the cluster you want + to delete. The arguments in this group can be used to specify the + attributes of this resource. (NOTE) Some attributes are not given + arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument cluster on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + CLUSTER + ID of the cluster or fully qualified identifier for the cluster. + + To set the cluster attribute: + ▸ provide the argument cluster on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The name of the Redis region of the cluster. Overrides the default + redis/region property value for this command invocation. + + To set the region attribute: + ▸ provide the argument cluster on the command line with a fully + specified name; + ▸ provide the argument --region on the command line; + ▸ set the property redis/region. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the redis/v1 API. The full documentation for this API can + be found at: https://cloud.google.com/memorystore/docs/redis/ + +NOTES + These variants are also available: + + $ gcloud alpha redis clusters delete + + $ gcloud beta redis clusters delete + diff --git a/gcloud/redis/clusters/describe b/gcloud/redis/clusters/describe new file mode 100644 index 000000000..6679c48aa --- /dev/null +++ b/gcloud/redis/clusters/describe @@ -0,0 +1,76 @@ +NAME + gcloud redis clusters describe - show metadata for a Memorystore for Redis + Cluster instance + +SYNOPSIS + gcloud redis clusters describe (CLUSTER : --region=REGION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Show metadata for a Memorystore for Redis Cluster instance. + + Displays all metadata associated with a cluster given a valid cluster name. + + This command can fail for the following reasons: + ▪ The cluster specified does not exist. + ▪ The active account does not have permission to access the given + cluster. + +EXAMPLES + To display the metadata for a cluster with the name my-redis-cluster in the + default region, run: + + $ gcloud redis clusters describe my-redis-cluster + +POSITIONAL ARGUMENTS + Cluster resource - Arguments and flags that specify the cluster you want + to describe. The arguments in this group can be used to specify the + attributes of this resource. (NOTE) Some attributes are not given + arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument cluster on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + CLUSTER + ID of the cluster or fully qualified identifier for the cluster. + + To set the cluster attribute: + ▸ provide the argument cluster on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The name of the Redis region of the cluster. Overrides the default + redis/region property value for this command invocation. + + To set the region attribute: + ▸ provide the argument cluster on the command line with a fully + specified name; + ▸ provide the argument --region on the command line; + ▸ set the property redis/region. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the redis/v1 API. The full documentation for this API can + be found at: https://cloud.google.com/memorystore/docs/redis/ + +NOTES + These variants are also available: + + $ gcloud alpha redis clusters describe + + $ gcloud beta redis clusters describe + diff --git a/gcloud/redis/clusters/get-cluster-certificate-authority b/gcloud/redis/clusters/get-cluster-certificate-authority new file mode 100644 index 000000000..d67e4a9c5 --- /dev/null +++ b/gcloud/redis/clusters/get-cluster-certificate-authority @@ -0,0 +1,77 @@ +NAME + gcloud redis clusters get-cluster-certificate-authority - get the + certificate authority information for a Memorystore for Redis Cluster + instance + +SYNOPSIS + gcloud redis clusters get-cluster-certificate-authority + (CLUSTER : --region=REGION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Get the certificate authority information for a Memorystore for Redis + Cluster instance. + + This command can fail for the following reasons: + ▪ The cluster specified does not exist. + ▪ The active account does not have permission to access the given + cluster. + +EXAMPLES + To get the metadata for a cluster with the name my-redie-cluster in the + default region, run: + + $ gcloud redis clusters get-cluster-certificate-authority \ + my-redis-cluster + +POSITIONAL ARGUMENTS + Cluster resource - Arguments and flags that specify the 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; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + CLUSTER + ID of the cluster or fully qualified identifier for the cluster. + + To set the cluster attribute: + ▸ provide the argument cluster on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The name of the Redis region of the cluster. Overrides the default + redis/region property value for this command invocation. + + To set the region attribute: + ▸ provide the argument cluster on the command line with a fully + specified name; + ▸ provide the argument --region on the command line; + ▸ set the property redis/region. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the redis/v1 API. The full documentation for this API can + be found at: https://cloud.google.com/memorystore/docs/redis/ + +NOTES + These variants are also available: + + $ gcloud alpha redis clusters get-cluster-certificate-authority + + $ gcloud beta redis clusters get-cluster-certificate-authority + diff --git a/gcloud/redis/clusters/help b/gcloud/redis/clusters/help new file mode 100644 index 000000000..e22ec655a --- /dev/null +++ b/gcloud/redis/clusters/help @@ -0,0 +1,43 @@ +NAME + gcloud redis clusters - manage Memorystore for Redis Cluster instances + +SYNOPSIS + gcloud redis clusters COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Manage Memorystore for Redis Cluster instances. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + create + Create a new Memorystore for Redis Cluster instance. + + delete + Delete a Memorystore for Redis Cluster instance. + + describe + Show metadata for a Memorystore for Redis Cluster instance. + + get-cluster-certificate-authority + Get the certificate authority information for a Memorystore for Redis + Cluster instance. + + list + List Memorystore for Redis Cluster instances. + + update + Update Memorystore Cluster for Redis instance. + +NOTES + These variants are also available: + + $ gcloud alpha redis clusters + + $ gcloud beta redis clusters + diff --git a/gcloud/redis/clusters/list b/gcloud/redis/clusters/list new file mode 100644 index 000000000..fdb02d4c3 --- /dev/null +++ b/gcloud/redis/clusters/list @@ -0,0 +1,88 @@ +NAME + gcloud redis clusters list - list Memorystore for Redis Cluster instances + +SYNOPSIS + gcloud redis clusters list [--region=REGION] [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + List all clusters under the specified project and region. + + To specify the maximum number of clusters to list, use the --limit flag. + +EXAMPLES + To list up to five clusters, run: + + $ gcloud redis clusters list --limit=5 + +FLAGS + Region resource - The region of the clusters to display. This represents a + Cloud resource. (NOTE) Some attributes are not given arguments in this + group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument --region on the command line with a fully + specified name; + ◆ set the property redis/region with a fully specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + --region=REGION + ID of the region or fully qualified identifier for the region. + + To set the region attribute: + ▸ provide the argument --region on the command line; + ▸ set the property redis/region. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the redis/v1 API. The full documentation for this API can + be found at: https://cloud.google.com/memorystore/docs/redis/ + +NOTES + These variants are also available: + + $ gcloud alpha redis clusters list + + $ gcloud beta redis clusters list + diff --git a/gcloud/redis/clusters/update b/gcloud/redis/clusters/update new file mode 100644 index 000000000..79a3dfbbf --- /dev/null +++ b/gcloud/redis/clusters/update @@ -0,0 +1,86 @@ +NAME + gcloud redis clusters update - update Memorystore Cluster for Redis + instance + +SYNOPSIS + gcloud redis clusters update (CLUSTER : --region=REGION) [--async] + [--replica-count=REPLICA_COUNT] [--shard-count=SHARD_COUNT] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Update the metadata and/or configuration parameters of a Redis cluster. + + This command can fail for the following reasons: + ▪ The cluster specified does not exist. + ▪ The active account does not have permission to update the given + cluster. + +EXAMPLES + To update a Redis cluster with 5 shard and 2 replica, run: + + $ gcloud redis clusters update my-redis-cluster --shard-count=5 \ + --replica-count=2 + +POSITIONAL ARGUMENTS + Cluster resource - Arguments and flags that specify the Memorystore Redis + cluster you want to update. The arguments in this group can be used to + specify the attributes of this resource. (NOTE) Some attributes are not + given arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument cluster on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + CLUSTER + ID of the cluster or fully qualified identifier for the cluster. + + To set the cluster attribute: + ▸ provide the argument cluster on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The name of the Redis region of the cluster. Overrides the default + redis/region property value for this command invocation. + + To set the region attribute: + ▸ provide the argument cluster on the command line with a fully + specified name; + ▸ provide the argument --region on the command line; + ▸ set the property redis/region. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --replica-count=REPLICA_COUNT + The replica count of each shard. + + --shard-count=SHARD_COUNT + The shard count of the cluster. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the redis/v1 API. The full documentation for this API can + be found at: https://cloud.google.com/memorystore/docs/redis/ + +NOTES + These variants are also available: + + $ gcloud alpha redis clusters update + + $ gcloud beta redis clusters update + diff --git a/gcloud/redis/help b/gcloud/redis/help index 223bcb0b8..4e4b86d5e 100644 --- a/gcloud/redis/help +++ b/gcloud/redis/help @@ -15,6 +15,9 @@ GCLOUD WIDE FLAGS GROUPS GROUP is one of the following: + clusters + Manage Memorystore for Redis Cluster instances. + instances Manage Cloud Memorystore Redis instances. diff --git a/gcloud/storage/buckets/create b/gcloud/storage/buckets/create index cc66db8dc..8b3f1d152 100644 --- a/gcloud/storage/buckets/create +++ b/gcloud/storage/buckets/create @@ -8,12 +8,13 @@ SYNOPSIS -k DEFAULT_ENCRYPTION_KEY] [--default-storage-class=DEFAULT_STORAGE_CLASS, -c DEFAULT_STORAGE_CLASS, -s DEFAULT_STORAGE_CLASS] - [--[no-]enable-autoclass] [--location=LOCATION, -l LOCATION] + [--location=LOCATION, -l LOCATION] [--[no-]pap, --[no-]public-access-prevention] [--placement=REGION,REGION] [--recovery-point-objective=SETTING, --rpo=SETTING] [--retention-period=RETENTION_PERIOD] - [--[no-]uniform-bucket-level-access, -b] [GCLOUD_WIDE_FLAG ...] + [--[no-]uniform-bucket-level-access, -b] [--[no-]enable-autoclass] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION Create new buckets. @@ -53,11 +54,6 @@ FLAGS If not specified, the default storage class used by Cloud Storage is "Standard". - --[no-]enable-autoclass - The Autoclass feature automatically selects the best storage class for - objects based on access patterns. Use --enable-autoclass to enable and - --no-enable-autoclass to disable. - --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 @@ -102,6 +98,12 @@ FLAGS --uniform-bucket-level-access to enable and --no-uniform-bucket-level-access to disable. +AUTOCLASS FLAGS + --[no-]enable-autoclass + The Autoclass feature automatically selects the best storage class for + objects based on access patterns. Use --enable-autoclass to enable and + --no-enable-autoclass to disable. + 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/buckets/update b/gcloud/storage/buckets/update index 6581b8a88..0851e169c 100644 --- a/gcloud/storage/buckets/update +++ b/gcloud/storage/buckets/update @@ -4,8 +4,7 @@ NAME SYNOPSIS gcloud storage buckets update URL [URL ...] [--additional-headers=HEADER=VALUE] [--continue-on-error, -c] - [--[no-]default-event-based-hold] [--[no-]enable-autoclass] - [--lock-retention-period] + [--[no-]default-event-based-hold] [--lock-retention-period] [--recovery-point-objective=SETTING, --rpo=SETTING] [--[no-]requester-pays] [--[no-]uniform-bucket-level-access] [--[no-]versioning] @@ -30,7 +29,8 @@ SYNOPSIS [--clear-retention-period | --retention-period=RETENTION_PERIOD] [--clear-web-error-page | --web-error-page=WEB_ERROR_PAGE] [--clear-web-main-page-suffix - | --web-main-page-suffix=WEB_MAIN_PAGE_SUFFIX] [GCLOUD_WIDE_FLAG ...] + | --web-main-page-suffix=WEB_MAIN_PAGE_SUFFIX] + [--[no-]enable-autoclass] [GCLOUD_WIDE_FLAG ...] DESCRIPTION Update the settings for a bucket. @@ -77,11 +77,6 @@ FLAGS retroactively). Use --default-event-based-hold to enable and --no-default-event-based-hold to disable. - --[no-]enable-autoclass - The Autoclass feature automatically selects the best storage class for - objects based on access patterns. Use --enable-autoclass to enable and - --no-enable-autoclass to disable. - --lock-retention-period Locks an unlocked retention policy on the buckets. Caution: A locked retention policy cannot be removed from a bucket or reduced in @@ -298,6 +293,12 @@ FLAGS domain serves the specified "main" page instead of performing the usual bucket listing. +AUTOCLASS FLAGS + --[no-]enable-autoclass + The Autoclass feature automatically selects the best storage class for + objects based on access patterns. Use --enable-autoclass to enable and + --no-enable-autoclass to disable. + 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/workstations/configs/create b/gcloud/workstations/configs/create index 9874567a8..e989fd6db 100644 --- a/gcloud/workstations/configs/create +++ b/gcloud/workstations/configs/create @@ -20,8 +20,10 @@ SYNOPSIS [--pd-reclaim-policy=PD_RECLAIM_POLICY; default="delete"] [--pool-size=POOL_SIZE] [--replica-zones=[REPLICA_ZONES,...]] [--running-timeout=RUNNING_TIMEOUT; default=7200] - [--service-account=SERVICE_ACCOUNT] [--shielded-integrity-monitoring] - [--shielded-secure-boot] [--shielded-vtpm] + [--service-account=SERVICE_ACCOUNT] + [--service-account-scopes=[SERVICE_ACCOUNT_SCOPES,...]] + [--shielded-integrity-monitoring] [--shielded-secure-boot] + [--shielded-vtpm] [--container-custom-image=CONTAINER_CUSTOM_IMAGE | --container-predefined-image=CONTAINER_PREDEFINED_IMAGE; default="codeoss"] @@ -208,6 +210,12 @@ FLAGS to pull the specified container image. If not set, VMs will run without a service account, in which case the image must be publicly accessible. + --service-account-scopes=[SERVICE_ACCOUNT_SCOPES,...] + Scopes to grant to the service_account. Various scopes are + automatically added based on feature usage. When specified, users of + workstations under this configuration must have + iam.serviceAccounts.actAs on the service account. + --shielded-integrity-monitoring Default value is false. If set, instances will have integrity monitoring enabled. diff --git a/gcloud/workstations/configs/update b/gcloud/workstations/configs/update index a88918fe2..91c309d97 100644 --- a/gcloud/workstations/configs/update +++ b/gcloud/workstations/configs/update @@ -15,6 +15,7 @@ SYNOPSIS [--labels=[LABELS,...]] [--machine-type=MACHINE_TYPE] [--network-tags=[NETWORK_TAGS,...]] [--pool-size=POOL_SIZE] [--running-timeout=RUNNING_TIMEOUT] [--service-account=SERVICE_ACCOUNT] + [--service-account-scopes=[SERVICE_ACCOUNT_SCOPES,...]] [--shielded-integrity-monitoring] [--shielded-secure-boot] [--shielded-vtpm] [--container-custom-image=CONTAINER_CUSTOM_IMAGE @@ -168,6 +169,12 @@ FLAGS to pull the specified container image. If not set, VMs will run without a service account, in which case the image must be publicly accessible. + --service-account-scopes=[SERVICE_ACCOUNT_SCOPES,...] + Scopes to grant to the service_account. Various scopes are + automatically added based on feature usage. When specified, users of + workstations under this configuration must have + iam.serviceAccounts.actAs on the service account. + --shielded-integrity-monitoring Default value is false. If set, instances will have integrity monitoring enabled.