diff --git a/gcloud/_version b/gcloud/_version index c93b9ed15..f5614d895 100644 --- a/gcloud/_version +++ b/gcloud/_version @@ -1,8 +1,8 @@ -Google Cloud SDK 550.0.0 -alpha 2025.12.12 -beta 2025.12.12 -bq 2.1.26 +Google Cloud SDK 552.0.0 +alpha 2026.01.09 +beta 2026.01.09 +bq 2.1.27 bundled-python3-unix 3.13.10 -core 2025.12.12 +core 2026.01.09 gcloud-crc32c 1.0.0 gsutil 5.35 diff --git a/gcloud/alpha/backup-dr/resource-backup-config/help b/gcloud/alpha/backup-dr/resource-backup-config/help index 056f6d3dd..2521b1f09 100644 --- a/gcloud/alpha/backup-dr/resource-backup-config/help +++ b/gcloud/alpha/backup-dr/resource-backup-config/help @@ -26,5 +26,7 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. This variant is also available: + + $ gcloud backup-dr resource-backup-config diff --git a/gcloud/alpha/backup-dr/resource-backup-config/list b/gcloud/alpha/backup-dr/resource-backup-config/list index 3f9d5973a..2fb835d81 100644 --- a/gcloud/alpha/backup-dr/resource-backup-config/list +++ b/gcloud/alpha/backup-dr/resource-backup-config/list @@ -138,5 +138,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 backup-dr resource-backup-config list diff --git a/gcloud/alpha/cluster-director/clusters/create b/gcloud/alpha/cluster-director/clusters/create index 32652d71f..cec703340 100644 --- a/gcloud/alpha/cluster-director/clusters/create +++ b/gcloud/alpha/cluster-director/clusters/create @@ -14,8 +14,8 @@ SYNOPSIS [enableOSLogin=ENABLEOSLOGIN],[enablePublicIPs=ENABLEPUBLICIPS], [labels=LABELS], [machineType=MACHINETYPE],[startupScript=STARTUPSCRIPT],[zone=ZONE] - --slurm-node-sets=[computeId=COMPUTEID],[id=ID],[labels=LABELS], - [maxDynamicNodeCount=MAXDYNAMICNODECOUNT], + --slurm-node-sets=[bootDisk=BOOTDISK],[computeId=COMPUTEID],[id=ID], + [labels=LABELS],[maxDynamicNodeCount=MAXDYNAMICNODECOUNT], [startupScript=STARTUPSCRIPT],[staticNodeCount=STATICNODECOUNT] --slurm-partitions=[exclusive=EXCLUSIVE], [id=ID],[nodesetIds=NODESETIDS] @@ -998,7 +998,7 @@ REQUIRED FLAGS This flag argument must be specified if any of the other arguments in this group are specified. - --slurm-node-sets=[computeId=COMPUTEID],[id=ID],[labels=LABELS],[maxDynamicNodeCount=MAXDYNAMICNODECOUNT],[startupScript=STARTUPSCRIPT],[staticNodeCount=STATICNODECOUNT] + --slurm-node-sets=[bootDisk=BOOTDISK],[computeId=COMPUTEID],[id=ID],[labels=LABELS],[maxDynamicNodeCount=MAXDYNAMICNODECOUNT],[startupScript=STARTUPSCRIPT],[staticNodeCount=STATICNODECOUNT] Parameters to define slurm cluster nodeset config. For e.g. --slurm-node-sets @@ -1017,6 +1017,18 @@ REQUIRED FLAGS Required, sets slurm_node_sets value. + bootDisk + Sets bootDisk value. + + image + Sets image value. + + sizeGb + Required, sets sizeGb value. + + type + Required, sets type value. + computeId Required, sets computeId value. @@ -1043,11 +1055,11 @@ REQUIRED FLAGS Shorthand Example: - --slurm-node-sets=computeId=string,id=string,labels={string=string},maxDynamicNodeCount=int,startupScript=string,staticNodeCount=int --slurm-node-sets=computeId=string,id=string,labels={string=string},maxDynamicNodeCount=int,startupScript=string,staticNodeCount=int + --slurm-node-sets=bootDisk={image=string,sizeGb=int,type=string},computeId=string,id=string,labels={string=string},maxDynamicNodeCount=int,startupScript=string,staticNodeCount=int --slurm-node-sets=bootDisk={image=string,sizeGb=int,type=string},computeId=string,id=string,labels={string=string},maxDynamicNodeCount=int,startupScript=string,staticNodeCount=int JSON Example: - --slurm-node-sets='[{"computeId": "string", "id": "string", "labels": {"string": "string"}, "maxDynamicNodeCount": int, "startupScript": "string", "staticNodeCount": int}]' + --slurm-node-sets='[{"bootDisk": {"image": "string", "sizeGb": int, "type": "string"}, "computeId": "string", "id": "string", "labels": {"string": "string"}, "maxDynamicNodeCount": int, "startupScript": "string", "staticNodeCount": int}]' File Example: diff --git a/gcloud/alpha/cluster-director/clusters/update b/gcloud/alpha/cluster-director/clusters/update index a2d7faf95..d44c33347 100644 --- a/gcloud/alpha/cluster-director/clusters/update +++ b/gcloud/alpha/cluster-director/clusters/update @@ -21,8 +21,8 @@ SYNOPSIS [machineType=MACHINETYPE],[zone=ZONE] --add-reserved-instances=[id=ID], [machineType=MACHINETYPE],[reservation=RESERVATION] - --add-slurm-node-sets=[computeId=COMPUTEID],[id=ID],[labels=LABELS], - [maxDynamicNodeCount=MAXDYNAMICNODECOUNT], + --add-slurm-node-sets=[bootDisk=BOOTDISK],[computeId=COMPUTEID], + [id=ID],[labels=LABELS],[maxDynamicNodeCount=MAXDYNAMICNODECOUNT], [startupScript=STARTUPSCRIPT],[staticNodeCount=STATICNODECOUNT] --add-slurm-partitions=[exclusive=EXCLUSIVE], [id=ID],[nodesetIds=NODESETIDS] @@ -42,7 +42,7 @@ SYNOPSIS --slurm-default-partition=SLURM_DEFAULT_PARTITION --update-slurm-login-node=[bootDisk=BOOTDISK], [count=COUNT],[startupScript=STARTUPSCRIPT] - --update-slurm-node-sets=[id=ID], + --update-slurm-node-sets=[bootDisk=BOOTDISK],[id=ID], [maxDynamicNodeCount=MAXDYNAMICNODECOUNT], [staticNodeCount=STATICNODECOUNT] --update-slurm-partitions=[exclusive=EXCLUSIVE], @@ -452,7 +452,7 @@ REQUIRED FLAGS --add-reserved-instances=path_to_file.(yaml|json) - --add-slurm-node-sets=[computeId=COMPUTEID],[id=ID],[labels=LABELS],[maxDynamicNodeCount=MAXDYNAMICNODECOUNT],[startupScript=STARTUPSCRIPT],[staticNodeCount=STATICNODECOUNT] + --add-slurm-node-sets=[bootDisk=BOOTDISK],[computeId=COMPUTEID],[id=ID],[labels=LABELS],[maxDynamicNodeCount=MAXDYNAMICNODECOUNT],[startupScript=STARTUPSCRIPT],[staticNodeCount=STATICNODECOUNT] Parameters to define slurm cluster nodeset config. For e.g. --add-slurm-node-sets @@ -471,6 +471,18 @@ REQUIRED FLAGS Sets add_slurm_node_sets value. + bootDisk + Sets bootDisk value. + + image + Sets image value. + + sizeGb + Required, sets sizeGb value. + + type + Required, sets type value. + computeId Required, sets computeId value. @@ -497,11 +509,11 @@ REQUIRED FLAGS Shorthand Example: - --add-slurm-node-sets=computeId=string,id=string,labels={string=string},maxDynamicNodeCount=int,startupScript=string,staticNodeCount=int --add-slurm-node-sets=computeId=string,id=string,labels={string=string},maxDynamicNodeCount=int,startupScript=string,staticNodeCount=int + --add-slurm-node-sets=bootDisk={image=string,sizeGb=int,type=string},computeId=string,id=string,labels={string=string},maxDynamicNodeCount=int,startupScript=string,staticNodeCount=int --add-slurm-node-sets=bootDisk={image=string,sizeGb=int,type=string},computeId=string,id=string,labels={string=string},maxDynamicNodeCount=int,startupScript=string,staticNodeCount=int JSON Example: - --add-slurm-node-sets='[{"computeId": "string", "id": "string", "labels": {"string": "string"}, "maxDynamicNodeCount": int, "startupScript": "string", "staticNodeCount": int}]' + --add-slurm-node-sets='[{"bootDisk": {"image": "string", "sizeGb": int, "type": "string"}, "computeId": "string", "id": "string", "labels": {"string": "string"}, "maxDynamicNodeCount": int, "startupScript": "string", "staticNodeCount": int}]' File Example: @@ -672,7 +684,7 @@ REQUIRED FLAGS --update-slurm-login-node=path_to_file.(yaml|json) - --update-slurm-node-sets=[id=ID],[maxDynamicNodeCount=MAXDYNAMICNODECOUNT],[staticNodeCount=STATICNODECOUNT] + --update-slurm-node-sets=[bootDisk=BOOTDISK],[id=ID],[maxDynamicNodeCount=MAXDYNAMICNODECOUNT],[staticNodeCount=STATICNODECOUNT] Parameters to define and update slurm cluster nodeset config. For e.g. --update-slurm-node-sets @@ -680,6 +692,18 @@ REQUIRED FLAGS Sets update_slurm_node_sets value. + bootDisk + Sets bootDisk value. + + image + Sets image value. + + sizeGb + Required, sets sizeGb value. + + type + Required, sets type value. + id Required, sets id value. @@ -691,11 +715,11 @@ REQUIRED FLAGS Shorthand Example: - --update-slurm-node-sets=id=string,maxDynamicNodeCount=int,staticNodeCount=int --update-slurm-node-sets=id=string,maxDynamicNodeCount=int,staticNodeCount=int + --update-slurm-node-sets=bootDisk={image=string,sizeGb=int,type=string},id=string,maxDynamicNodeCount=int,staticNodeCount=int --update-slurm-node-sets=bootDisk={image=string,sizeGb=int,type=string},id=string,maxDynamicNodeCount=int,staticNodeCount=int JSON Example: - --update-slurm-node-sets='[{"id": "string", "maxDynamicNodeCount": int, "staticNodeCount": int}]' + --update-slurm-node-sets='[{"bootDisk": {"image": "string", "sizeGb": int, "type": "string"}, "id": "string", "maxDynamicNodeCount": int, "staticNodeCount": int}]' File Example: diff --git a/gcloud/alpha/composer/environments/create b/gcloud/alpha/composer/environments/create index e7e608215..964c611d3 100644 --- a/gcloud/alpha/composer/environments/create +++ b/gcloud/alpha/composer/environments/create @@ -375,12 +375,12 @@ FLAGS --enable-ip-alias Enable use of alias IPs - (https://cloud.google.com/compute/docs/alias-ip/) for Pod IPs. This + (https://cloud.google.com/compute/docs/alias-ip) for Pod IPs. This will require at least two secondary ranges in the subnetwork, one for the pod IPs and another to reserve space for the services range. --enable-ip-masq-agent - When enabled, the IP Masquarade Agent + When enabled, the IP Masquerade Agent (https://cloud.google.com/composer/docs/enable-ip-masquerade-agent) is deployed to your environment's cluster. It performs many-to-one IP address translations to hide a pod's IP address behind the cluster @@ -463,7 +463,7 @@ FLAGS --enable-master-authorized-networks Enable Master Authorized Networks feature - (https://cloud.google.com/kubernetes-engine/docs/how-to/authorized-networks/) + (https://cloud.google.com/kubernetes-engine/docs/how-to/authorized-networks) in the Composer Environment's GKE cluster. --master-authorized-networks=[NETWORK,...] diff --git a/gcloud/alpha/composer/environments/update b/gcloud/alpha/composer/environments/update index 0275c48db..94622a9cb 100644 --- a/gcloud/alpha/composer/environments/update +++ b/gcloud/alpha/composer/environments/update @@ -249,12 +249,12 @@ REQUIRED FLAGS --disable-master-authorized-networks Disable Master Authorized Networks feature - (https://cloud.google.com/kubernetes-engine/docs/how-to/authorized-networks/) + (https://cloud.google.com/kubernetes-engine/docs/how-to/authorized-networks) in the Composer Environment's GKE cluster. --enable-master-authorized-networks Enable Master Authorized Networks feature - (https://cloud.google.com/kubernetes-engine/docs/how-to/authorized-networks/) + (https://cloud.google.com/kubernetes-engine/docs/how-to/authorized-networks) in the Composer Environment's GKE cluster. --master-authorized-networks=[NETWORK,...] diff --git a/gcloud/alpha/compute/backend-services/import b/gcloud/alpha/compute/backend-services/import index 8507a2e75..01e9c04bf 100644 --- a/gcloud/alpha/compute/backend-services/import +++ b/gcloud/alpha/compute/backend-services/import @@ -21,8 +21,8 @@ POSITIONAL ARGUMENTS FLAGS --source=SOURCE Path to a YAML file containing configuration export data. - Alternatively, you may omit this flag to read from standard input.For a - schema describing the export/import format, see: + Alternatively, you may omit this flag to read from standard input. For + a schema describing the export/import format, see: $CLOUDSDKROOT/lib/googlecloudsdk/schemas/compute/alpha/BackendService.yaml. Note: $CLOUDSDKROOT represents the Google Cloud CLI's installation directory. diff --git a/gcloud/alpha/compute/disks/create b/gcloud/alpha/compute/disks/create index 4222928e1..e32f9e5dd 100644 --- a/gcloud/alpha/compute/disks/create +++ b/gcloud/alpha/compute/disks/create @@ -13,6 +13,7 @@ SYNOPSIS [--provisioned-iops=PROVISIONED_IOPS] [--provisioned-throughput=PROVISIONED_THROUGHPUT] [--replica-zones=ZONE,ZONE] [--no-require-csek-key-create] + [--resource-manager-tags=[KEY=VALUE,...]] [--resource-policies=[RESOURCE_POLICY,...]] [--size=SIZE] [--source-instant-snapshot-project=SOURCE_INSTANT_SNAPSHOT_PROJECT] [--storage-pool=STORAGE_POOL] [--type=TYPE] @@ -166,6 +167,9 @@ FLAGS for more details. Enabled by default, use --no-require-csek-key-create to disable. + --resource-manager-tags=[KEY=VALUE,...] + A comma-separated list of Resource Manager tags to apply to the disk. + --resource-policies=[RESOURCE_POLICY,...] A list of resource policy names to be added to the disk. The policies must exist in the same region as the disk. diff --git a/gcloud/alpha/compute/firewall-policies/import-rules b/gcloud/alpha/compute/firewall-policies/import-rules index 1f06ad161..c1fa4c2b0 100644 --- a/gcloud/alpha/compute/firewall-policies/import-rules +++ b/gcloud/alpha/compute/firewall-policies/import-rules @@ -27,8 +27,8 @@ FLAGS --source=SOURCE Path to a YAML file containing configuration export data. - Alternatively, you may omit this flag to read from standard input.For a - schema describing the export/import format, see: + Alternatively, you may omit this flag to read from standard input. For + a schema describing the export/import format, see: $CLOUDSDKROOT/lib/googlecloudsdk/schemas/compute/alpha/FirewallPolicy.yaml. Note: $CLOUDSDKROOT represents the Google Cloud CLI's installation directory. diff --git a/gcloud/alpha/compute/forwarding-rules/import b/gcloud/alpha/compute/forwarding-rules/import index 841c533af..ff6108cd5 100644 --- a/gcloud/alpha/compute/forwarding-rules/import +++ b/gcloud/alpha/compute/forwarding-rules/import @@ -21,8 +21,8 @@ POSITIONAL ARGUMENTS FLAGS --source=SOURCE Path to a YAML file containing configuration export data. - Alternatively, you may omit this flag to read from standard input.For a - schema describing the export/import format, see: + Alternatively, you may omit this flag to read from standard input. For + a schema describing the export/import format, see: $CLOUDSDKROOT/lib/googlecloudsdk/schemas/compute/alpha/ForwardingRule.yaml. Note: $CLOUDSDKROOT represents the Google Cloud CLI's installation directory. diff --git a/gcloud/alpha/compute/instances/update-from-file b/gcloud/alpha/compute/instances/update-from-file index 3dcf623fe..888baadaa 100644 --- a/gcloud/alpha/compute/instances/update-from-file +++ b/gcloud/alpha/compute/instances/update-from-file @@ -42,8 +42,8 @@ FLAGS --source=SOURCE Path to a YAML file containing configuration export data. - Alternatively, you may omit this flag to read from standard input.For a - schema describing the export/import format, see: + Alternatively, you may omit this flag to read from standard input. For + a schema describing the export/import format, see: $CLOUDSDKROOT/lib/googlecloudsdk/schemas/compute/alpha/Instance.yaml. Note: $CLOUDSDKROOT represents the Google Cloud CLI's installation directory. diff --git a/gcloud/alpha/compute/interconnects/attachments/dedicated/create b/gcloud/alpha/compute/interconnects/attachments/dedicated/create index 97459f438..3d3f32c63 100644 --- a/gcloud/alpha/compute/interconnects/attachments/dedicated/create +++ b/gcloud/alpha/compute/interconnects/attachments/dedicated/create @@ -121,9 +121,9 @@ OPTIONAL FLAGS it. --enable-multicast - If supplied, the attachment will be able to carry multicast traffic. If - not provided on creation, defaults to disabled. Use - --no-enable-multicast to disable it. + If supplied, the attachment will be able to carry multicast traffic. + Defaults to disabled. This property can only be set during attachment + creation and cannot be modified later. --encryption=ENCRYPTION Indicates the user-supplied encryption option for this interconnect diff --git a/gcloud/alpha/compute/interconnects/attachments/dedicated/update b/gcloud/alpha/compute/interconnects/attachments/dedicated/update index 507c41768..202219ef6 100644 --- a/gcloud/alpha/compute/interconnects/attachments/dedicated/update +++ b/gcloud/alpha/compute/interconnects/attachments/dedicated/update @@ -10,8 +10,8 @@ SYNOPSIS [--candidate-ipv6-subnets=[IPV6_SUBNET,...]] [--cloud-router-ipv6-interface-id=INTERFACE_ID] [--customer-router-ipv6-interface-id=PEER_INTERFACE_ID] - [--description=DESCRIPTION] [--enable-admin] [--enable-multicast] - [--mtu=MTU] [--region=REGION] [--stack-type=STACK_TYPE] + [--description=DESCRIPTION] [--enable-admin] [--mtu=MTU] + [--region=REGION] [--stack-type=STACK_TYPE] [--update-labels=[KEY=VALUE,...]] [--clear-labels | --remove-labels=[KEY,...]] [GCLOUD_WIDE_FLAG ...] @@ -85,10 +85,6 @@ FLAGS enabled, the attachment is operational and will carry traffic. Use --no-enable-admin to disable it. - --enable-multicast - When enabled, the attachment will be able to carry multicast traffic. - Use --no-enable-multicast to disable it. - --mtu=MTU Maximum transmission unit (MTU) is the size of the largest IP packet passing through this interconnect attachment. Must be one of 1440, diff --git a/gcloud/alpha/compute/network-firewall-policies/import-rules b/gcloud/alpha/compute/network-firewall-policies/import-rules index 5c6fdcd6e..a4a356c12 100644 --- a/gcloud/alpha/compute/network-firewall-policies/import-rules +++ b/gcloud/alpha/compute/network-firewall-policies/import-rules @@ -22,8 +22,8 @@ POSITIONAL ARGUMENTS FLAGS --source=SOURCE Path to a YAML file containing configuration export data. - Alternatively, you may omit this flag to read from standard input.For a - schema describing the export/import format, see: + Alternatively, you may omit this flag to read from standard input. For + a schema describing the export/import format, see: $CLOUDSDKROOT/lib/googlecloudsdk/schemas/compute/alpha/FirewallPolicy.yaml. Note: $CLOUDSDKROOT represents the Google Cloud CLI's installation directory. diff --git a/gcloud/alpha/compute/networks/peerings/cancel-request-delete b/gcloud/alpha/compute/networks/peerings/cancel-request-delete index 3a5ec40b2..8c0a89828 100644 --- a/gcloud/alpha/compute/networks/peerings/cancel-request-delete +++ b/gcloud/alpha/compute/networks/peerings/cancel-request-delete @@ -8,11 +8,11 @@ SYNOPSIS DESCRIPTION (ALPHA) gcloud alpha compute networks peerings cancel-request-delete is - used to cancel a request to delete a consensus network peering connection - between two networks. + used to cancel a pending request to delete a consensus peering between two + networks. EXAMPLES - To cancel a deletion request of a consensus peering with the name + To cancel a request to delete a consensus peering with the name 'peering-name' between the network 'local-network' and the network 'peer-network', run: @@ -47,5 +47,7 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. This variant is also available: + + $ gcloud beta compute networks peerings cancel-request-delete diff --git a/gcloud/alpha/compute/project-info/help b/gcloud/alpha/compute/project-info/help index 7523e5e0d..4315d48a8 100644 --- a/gcloud/alpha/compute/project-info/help +++ b/gcloud/alpha/compute/project-info/help @@ -42,7 +42,7 @@ COMMANDS (ALPHA) Set the default service account on the project. set-usage-bucket - (ALPHA) Set usage reporting bucket for a project. + (ALPHA) (DEPRECATED) Set usage reporting bucket for a project. update (ALPHA) Update a Compute Engine project resource. diff --git a/gcloud/alpha/compute/project-info/set-usage-bucket b/gcloud/alpha/compute/project-info/set-usage-bucket index 901876841..aef403280 100644 --- a/gcloud/alpha/compute/project-info/set-usage-bucket +++ b/gcloud/alpha/compute/project-info/set-usage-bucket @@ -8,7 +8,12 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) gcloud alpha compute project-info set-usage-bucket configures usage + (ALPHA) (DEPRECATED) Set usage reporting bucket for a project. + + This command is deprecated. Please onboard with BigQuery Export instead. + https://docs.cloud.google.com/billing/docs/how-to/export-data-bigquery + + gcloud alpha compute project-info set-usage-bucket configures usage reporting for projects. Setting usage reporting will cause a log of usage per resource to be diff --git a/gcloud/alpha/compute/resource-policies/create/group-placement b/gcloud/alpha/compute/resource-policies/create/group-placement index 4b11a2ec6..9ff641cc5 100644 --- a/gcloud/alpha/compute/resource-policies/create/group-placement +++ b/gcloud/alpha/compute/resource-policies/create/group-placement @@ -4,6 +4,7 @@ NAME SYNOPSIS gcloud alpha compute resource-policies create group-placement NAME + [--accelerator-topology-mode=ACCELERATOR_TOPOLOGY_MODE] [--availability-domain-count=AVAILABILITY_DOMAIN_COUNT] [--collocation=COLLOCATION] [--description=DESCRIPTION] [--gpu-topology=GPU_TOPOLOGY] [--max-distance=MAX_DISTANCE] @@ -23,6 +24,16 @@ POSITIONAL ARGUMENTS Name of the resource policy to operate on. FLAGS + --accelerator-topology-mode=ACCELERATOR_TOPOLOGY_MODE + Defines the accelerator connection strategy for accelerator machine + types like TPUs. ACCELERATOR_TOPOLOGY_MODE must be one of: + + AUTO_CONNECT + This creates a static, pre-formed accelerator topology. + PROVISION_ONLY + The interconnected chips are connected on demand. At the time of VM + creation, the chips are not connected. + --availability-domain-count=AVAILABILITY_DOMAIN_COUNT Number of availability domain in the group placement policy. diff --git a/gcloud/alpha/compute/resource-policies/create/workload-policy b/gcloud/alpha/compute/resource-policies/create/workload-policy index 7613fdeaf..dc3f573ed 100644 --- a/gcloud/alpha/compute/resource-policies/create/workload-policy +++ b/gcloud/alpha/compute/resource-policies/create/workload-policy @@ -4,7 +4,8 @@ NAME SYNOPSIS gcloud alpha compute resource-policies create workload-policy NAME - --type=TYPE [--description=DESCRIPTION] [--region=REGION] + --type=TYPE [--accelerator-topology-mode=ACCELERATOR_TOPOLOGY_MODE] + [--description=DESCRIPTION] [--region=REGION] [--accelerator-topology=ACCELERATOR_TOPOLOGY | --max-topology-distance=MAX_TOPOLOGY_DISTANCE] [GCLOUD_WIDE_FLAG ...] @@ -38,6 +39,16 @@ REQUIRED FLAGS latency between VMs. OPTIONAL FLAGS + --accelerator-topology-mode=ACCELERATOR_TOPOLOGY_MODE + Defines the accelerator connection strategy for accelerator machine + types like TPUs. ACCELERATOR_TOPOLOGY_MODE must be one of: + + AUTO_CONNECT + This creates a static, pre-formed accelerator topology. + PROVISION_ONLY + The interconnected chips are connected on demand. At the time of VM + creation, the chips are not connected. + --description=DESCRIPTION An optional, textual description for the backend. diff --git a/gcloud/alpha/compute/routers/add-bgp-peer b/gcloud/alpha/compute/routers/add-bgp-peer index 605c7aed1..789887707 100644 --- a/gcloud/alpha/compute/routers/add-bgp-peer +++ b/gcloud/alpha/compute/routers/add-bgp-peer @@ -14,6 +14,7 @@ SYNOPSIS [--instance-zone=INSTANCE_ZONE] [--ipv4-nexthop-address=IPV4_NEXTHOP_ADDRESS] [--ipv6-nexthop-address=IPV6_NEXTHOP_ADDRESS] + [--linked-custom-hardware=LINKED_CUSTOM_HARDWARE] [--md5-authentication-key=MD5_AUTHENTICATION_KEY] [--peer-ip-address=PEER_IP_ADDRESS] [--peer-ipv4-nexthop-address=PEER_IPV4_NEXTHOP_ADDRESS] @@ -138,6 +139,12 @@ OPTIONAL FLAGS to the range 2600:2d00:0:2:0:0:0:0/64 or 2600:2d00:0:3:0:0:0:0/64 and must belong to same subnet as the interface address of the peer router. + --linked-custom-hardware=LINKED_CUSTOM_HARDWARE + The linked custom hardware resource. The URI of the custom hardware + link attachment is where you will establish the BGP session from the + Cloud Router. This link attachment must reside in the same subnetwork + as the associated router interface. + --md5-authentication-key=MD5_AUTHENTICATION_KEY The MD5 authentication key for this BGP peer. Maximum length is 80 characters. Can contain only printable ASCII characters. diff --git a/gcloud/alpha/compute/snapshots/create b/gcloud/alpha/compute/snapshots/create index 823a16e36..a0e565954 100644 --- a/gcloud/alpha/compute/snapshots/create +++ b/gcloud/alpha/compute/snapshots/create @@ -6,6 +6,7 @@ SYNOPSIS [--chain-name=CHAIN_NAME] [--csek-key-file=FILE] [--description=DESCRIPTION] [--guest-flush] [--labels=[KEY=VALUE,...]] [--max-retention-days=MAX_RETENTION_DAYS] + [--resource-manager-tags=[KEY=VALUE,...]] [--snapshot-type=SNAPSHOT_TYPE] [--source-disk=SOURCE_DISK] [--source-disk-for-recovery-checkpoint=SOURCE_DISK_FOR_RECOVERY_CHECKPOINT] [--source-disk-for-recovery-checkpoint-region=SOURCE_DISK_FOR_RECOVERY_CHECKPOINT_REGION] @@ -80,6 +81,10 @@ FLAGS Days for snapshot to live before being automatically deleted. If unspecified, the snapshot will live until manually deleted. + --resource-manager-tags=[KEY=VALUE,...] + A comma-separated list of Resource Manager tags to apply to the + snapshot. + --snapshot-type=SNAPSHOT_TYPE Type of snapshot. If a snapshot type is not specified, a STANDARD snapshot will be created. SNAPSHOT_TYPE must be one of: ARCHIVE, diff --git a/gcloud/alpha/compute/ssl-policies/import b/gcloud/alpha/compute/ssl-policies/import index d0f9339db..65d2ec7f5 100644 --- a/gcloud/alpha/compute/ssl-policies/import +++ b/gcloud/alpha/compute/ssl-policies/import @@ -18,8 +18,8 @@ POSITIONAL ARGUMENTS FLAGS --source=SOURCE Path to a YAML file containing configuration export data. - Alternatively, you may omit this flag to read from standard input.For a - schema describing the export/import format, see: + Alternatively, you may omit this flag to read from standard input. For + a schema describing the export/import format, see: $CLOUDSDKROOT/lib/googlecloudsdk/schemas/compute/alpha/SslPolicy.yaml. Note: $CLOUDSDKROOT represents the Google Cloud CLI's installation directory. diff --git a/gcloud/alpha/compute/target-grpc-proxies/import b/gcloud/alpha/compute/target-grpc-proxies/import index d5c54ba3d..8a787a18d 100644 --- a/gcloud/alpha/compute/target-grpc-proxies/import +++ b/gcloud/alpha/compute/target-grpc-proxies/import @@ -16,8 +16,8 @@ POSITIONAL ARGUMENTS FLAGS --source=SOURCE Path to a YAML file containing configuration export data. - Alternatively, you may omit this flag to read from standard input.For a - schema describing the export/import format, see: + Alternatively, you may omit this flag to read from standard input. For + a schema describing the export/import format, see: $CLOUDSDKROOT/lib/googlecloudsdk/schemas/compute/alpha/TargetGrpcProxy.yaml. Note: $CLOUDSDKROOT represents the Google Cloud CLI's installation directory. diff --git a/gcloud/alpha/compute/target-http-proxies/import b/gcloud/alpha/compute/target-http-proxies/import index 82ba955c6..157d1767f 100644 --- a/gcloud/alpha/compute/target-http-proxies/import +++ b/gcloud/alpha/compute/target-http-proxies/import @@ -22,8 +22,8 @@ POSITIONAL ARGUMENTS FLAGS --source=SOURCE Path to a YAML file containing configuration export data. - Alternatively, you may omit this flag to read from standard input.For a - schema describing the export/import format, see: + Alternatively, you may omit this flag to read from standard input. For + a schema describing the export/import format, see: $CLOUDSDKROOT/lib/googlecloudsdk/schemas/compute/alpha/TargetHttpProxy.yaml. Note: $CLOUDSDKROOT represents the Google Cloud CLI's installation directory. diff --git a/gcloud/alpha/compute/target-https-proxies/import b/gcloud/alpha/compute/target-https-proxies/import index b5c6b672a..1c531d699 100644 --- a/gcloud/alpha/compute/target-https-proxies/import +++ b/gcloud/alpha/compute/target-https-proxies/import @@ -27,8 +27,8 @@ POSITIONAL ARGUMENTS FLAGS --source=SOURCE Path to a YAML file containing configuration export data. - Alternatively, you may omit this flag to read from standard input.For a - schema describing the export/import format, see: + Alternatively, you may omit this flag to read from standard input. For + a schema describing the export/import format, see: $CLOUDSDKROOT/lib/googlecloudsdk/schemas/compute/alpha/TargetHttpsProxy.yaml. Note: $CLOUDSDKROOT represents the Google Cloud CLI's installation directory. diff --git a/gcloud/alpha/compute/url-maps/import b/gcloud/alpha/compute/url-maps/import index 8da731c6d..909e36aed 100644 --- a/gcloud/alpha/compute/url-maps/import +++ b/gcloud/alpha/compute/url-maps/import @@ -20,8 +20,8 @@ POSITIONAL ARGUMENTS FLAGS --source=SOURCE Path to a YAML file containing configuration export data. - Alternatively, you may omit this flag to read from standard input.For a - schema describing the export/import format, see: + Alternatively, you may omit this flag to read from standard input. For + a schema describing the export/import format, see: $CLOUDSDKROOT/lib/googlecloudsdk/schemas/compute/alpha/UrlMap.yaml. Note: $CLOUDSDKROOT represents the Google Cloud CLI's installation directory. diff --git a/gcloud/alpha/compute/vpn-tunnels/create b/gcloud/alpha/compute/vpn-tunnels/create index 97248671f..0a195f36a 100644 --- a/gcloud/alpha/compute/vpn-tunnels/create +++ b/gcloud/alpha/compute/vpn-tunnels/create @@ -11,8 +11,9 @@ SYNOPSIS | --target-vpn-gateway-region=TARGET_VPN_GATEWAY_REGION | --vpn-gateway=VPN_GATEWAY | --vpn-gateway-region=VPN_GATEWAY_REGION) - [--description=DESCRIPTION] [--ike-version=IKE_VERSION] - [--interface=INTERFACE] [--local-traffic-selector=CIDR,[CIDR,...]] + [--capacity-tier=CAPACITY_TIER] [--description=DESCRIPTION] + [--ike-version=IKE_VERSION] [--interface=INTERFACE] + [--local-traffic-selector=CIDR,[CIDR,...]] [--peer-external-gateway-interface=PEER_EXTERNAL_GATEWAY_INTERFACE] [--phase1-dh=GROUPS,[GROUPS,...]] [--phase1-encryption=ALGORITHMS,[ALGORITHMS,...]] @@ -82,6 +83,11 @@ REQUIRED FLAGS default compute/region property value for this command invocation. OPTIONAL FLAGS + --capacity-tier=CAPACITY_TIER + The capacity tier of the VPN tunnel. This is used for IPsec over + Interconnect tunnels to indicate different bandwidth limits. + CAPACITY_TIER must be one of: DEFAULT, HIGH. + --description=DESCRIPTION An optional, textual description for the VPN tunnel. diff --git a/gcloud/alpha/config/get b/gcloud/alpha/config/get index 75d12b019..ece9355e9 100644 --- a/gcloud/alpha/config/get +++ b/gcloud/alpha/config/get @@ -232,6 +232,10 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud certificate-manager command group. Defaults to https://certificatemanager.googleapis.com/ + cloudapiregistry + Overrides API endpoint for gcloud api-registry command group. + Defaults to https://cloudapiregistry.googleapis.com/ + cloudasset Overrides API endpoint for gcloud asset command group. Defaults to https://cloudasset.googleapis.com/ diff --git a/gcloud/alpha/config/help b/gcloud/alpha/config/help index 0855868a8..f7ef36f09 100644 --- a/gcloud/alpha/config/help +++ b/gcloud/alpha/config/help @@ -264,6 +264,10 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud certificate-manager command group. Defaults to https://certificatemanager.googleapis.com/ + cloudapiregistry + Overrides API endpoint for gcloud api-registry command group. + Defaults to https://cloudapiregistry.googleapis.com/ + cloudasset Overrides API endpoint for gcloud asset command group. Defaults to https://cloudasset.googleapis.com/ diff --git a/gcloud/alpha/config/list b/gcloud/alpha/config/list index cf2718216..e24b4ff64 100644 --- a/gcloud/alpha/config/list +++ b/gcloud/alpha/config/list @@ -276,6 +276,10 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud certificate-manager command group. Defaults to https://certificatemanager.googleapis.com/ + cloudapiregistry + Overrides API endpoint for gcloud api-registry command group. + Defaults to https://cloudapiregistry.googleapis.com/ + cloudasset Overrides API endpoint for gcloud asset command group. Defaults to https://cloudasset.googleapis.com/ diff --git a/gcloud/alpha/config/set b/gcloud/alpha/config/set index 5634cd6bd..9496998f7 100644 --- a/gcloud/alpha/config/set +++ b/gcloud/alpha/config/set @@ -279,6 +279,10 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud certificate-manager command group. Defaults to https://certificatemanager.googleapis.com/ + cloudapiregistry + Overrides API endpoint for gcloud api-registry command group. + Defaults to https://cloudapiregistry.googleapis.com/ + cloudasset Overrides API endpoint for gcloud asset command group. Defaults to https://cloudasset.googleapis.com/ diff --git a/gcloud/alpha/config/unset b/gcloud/alpha/config/unset index 4217654cd..1338f84d0 100644 --- a/gcloud/alpha/config/unset +++ b/gcloud/alpha/config/unset @@ -240,6 +240,10 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud certificate-manager command group. Defaults to https://certificatemanager.googleapis.com/ + cloudapiregistry + Overrides API endpoint for gcloud api-registry command group. + Defaults to https://cloudapiregistry.googleapis.com/ + cloudasset Overrides API endpoint for gcloud asset command group. Defaults to https://cloudasset.googleapis.com/ diff --git a/gcloud/alpha/container/clusters/create b/gcloud/alpha/container/clusters/create index bf7441b41..9bc253ee9 100644 --- a/gcloud/alpha/container/clusters/create +++ b/gcloud/alpha/container/clusters/create @@ -67,6 +67,7 @@ SYNOPSIS [--local-ssd-encryption-mode=LOCAL_SSD_ENCRYPTION_MODE] [--logging=[COMPONENT,...]] [--logging-variant=LOGGING_VARIANT] [--machine-type=MACHINE_TYPE, -m MACHINE_TYPE] + [--managed-otel-scope=MANAGED_OTEL_SCOPE] [--max-nodes-per-pool=MAX_NODES_PER_POOL] [--max-pods-per-node=MAX_PODS_PER_NODE] [--max-surge-upgrade=MAX_SURGE_UPGRADE; default=1] @@ -236,7 +237,8 @@ FLAGS KubernetesDashboard, NetworkPolicy, NodeLocalDNS, ConfigConnector, GcePersistentDiskCsiDriver, GcpFilestoreCsiDriver, BackupRestore, GcsFuseCsiDriver, ParallelstoreCsiDriver, HighScaleCheckpointing, - LustreCsiDriver, RayOperator, Istio, CloudBuild, CloudRun. + LustreCsiDriver, RayOperator, SlurmOperator, Istio, CloudBuild, + CloudRun. --allow-route-overlap Allows the provided cluster CIDRs to overlap with existing routes that @@ -405,7 +407,7 @@ FLAGS --confidential-node-type=CONFIDENTIAL_NODE_TYPE Enable confidential nodes for the cluster. Enabling Confidential Nodes will create nodes using Confidential VM - https://cloud.google.com/compute/confidential-vm/docs/about-cvm. + https://docs.cloud.google.com/compute/docs/about-confidential-vm. CONFIDENTIAL_NODE_TYPE must be one of: sev, sev_snp, tdx. --containerd-config-from-file=PATH_TO_FILE @@ -590,7 +592,7 @@ FLAGS --enable-confidential-nodes Enable confidential nodes for the cluster. Enabling Confidential Nodes will create nodes using Confidential VM - https://cloud.google.com/compute/confidential-vm/docs/about-cvm. + https://docs.cloud.google.com/compute/docs/about-confidential-vm. --enable-confidential-storage Enable confidential storage for the cluster. Enabling Confidential @@ -981,6 +983,17 @@ FLAGS $ gcloud alpha container clusters create high-mem-pool \ --machine-type=custom-2-12288 + --managed-otel-scope=MANAGED_OTEL_SCOPE + Specifies the scope of Managed OpenTelemetry within the cluster. + + COLLECTION_AND_INSTRUMENTATION_COMPONENTS: Enables GKE Managed + OpenTelemetry Collector and other Instrumentations components like + Instrumentation CRD within the cluster. NONE: Disables the GKE Managed + OpenTelemetry. + + MANAGED_OTEL_SCOPE must be one of: + COLLECTION_AND_INSTRUMENTATION_COMPONENTS, NONE. + --max-nodes-per-pool=MAX_NODES_PER_POOL The maximum number of nodes to allocate per default initial node pool. Kubernetes Engine will automatically create enough nodes pools such @@ -1731,7 +1744,10 @@ FLAGS [65536, 2147483647] vm.overcommit_memory Must be one of {0, - 1, 2} + 1, 2}. Not + supported on + machines with less + than 15 GB memory. vm.overcommit_ratio Must be between [0, 100] vm.vfs_cache_pressure Must be between @@ -1789,9 +1805,15 @@ FLAGS KEY VALUE diskCount integer - Allocated hugepage size should not exceed 60% of available memory on - the node. For example, c2d-highcpu-4 has 8GB memory, total allocated - hugepage of 2m and 1g should not exceed 8GB * 0.6 = 4.8GB. + The upper limit for total allocated hugepage size differs based upon + machine size. + + ◆ On machines with less than 30 GB memory: 60% of the total memory. + For example, on e2-standard-2 machine with 8 GB of memory, you can't + allocate more than 4.8 GB for hugepages. + ◆ On machines with more than 30 GB memory: 80% of the total memory. + For example, on c4a-standard-8 machines with 32 GB of memory, + hugepages cannot exceed 25.6 GB. 1G hugepages are only available in following machine familes: c3, m2, c2d, c3d, h3, m3, a2, a3, g2. diff --git a/gcloud/alpha/container/clusters/create-auto b/gcloud/alpha/container/clusters/create-auto index 2be836ba5..aae2943a4 100644 --- a/gcloud/alpha/container/clusters/create-auto +++ b/gcloud/alpha/container/clusters/create-auto @@ -30,13 +30,13 @@ SYNOPSIS [--enable-ray-cluster-logging] [--enable-ray-cluster-monitoring] [--enable-ray-operator] [--fleet-project=PROJECT_ID_OR_NUMBER] [--hpa-profile=HPA_PROFILE] [--labels=[KEY=VALUE,...]] - [--logging=[COMPONENT,...]] [--membership-type=MEMBERSHIP_TYPE] - [--monitoring=[COMPONENT,...]] [--network=NETWORK] - [--private-endpoint-subnetwork=NAME] [--release-channel=CHANNEL] - [--security-group=SECURITY_GROUP] [--security-posture=SECURITY_POSTURE] - [--services-ipv4-cidr=CIDR] [--services-secondary-range-name=NAME] - [--subnetwork=SUBNETWORK] [--tier=TIER] - [--workload-policies=WORKLOAD_POLICIES] + [--logging=[COMPONENT,...]] [--managed-otel-scope=MANAGED_OTEL_SCOPE] + [--membership-type=MEMBERSHIP_TYPE] [--monitoring=[COMPONENT,...]] + [--network=NETWORK] [--private-endpoint-subnetwork=NAME] + [--release-channel=CHANNEL] [--security-group=SECURITY_GROUP] + [--security-posture=SECURITY_POSTURE] [--services-ipv4-cidr=CIDR] + [--services-secondary-range-name=NAME] [--subnetwork=SUBNETWORK] + [--tier=TIER] [--workload-policies=WORKLOAD_POLICIES] [--workload-vulnerability-scanning=WORKLOAD_VULNERABILITY_SCANNING] [--additive-vpc-scope-dns-domain=ADDITIVE_VPC_SCOPE_DNS_DOMAIN | --disable-additive-vpc-scope] @@ -287,7 +287,7 @@ FLAGS --enable-confidential-nodes Enable confidential nodes for the cluster. Enabling Confidential Nodes will create nodes using Confidential VM - https://cloud.google.com/compute/confidential-vm/docs/about-cvm. + https://docs.cloud.google.com/compute/docs/about-confidential-vm. --enable-default-compute-class Enable the default compute class to use for the cluster. @@ -409,6 +409,17 @@ FLAGS --logging=SYSTEM,WORKLOAD,API_SERVER,CONTROLLER_MANAGER,\ SCHEDULER + --managed-otel-scope=MANAGED_OTEL_SCOPE + Specifies the scope of Managed OpenTelemetry within the cluster. + + COLLECTION_AND_INSTRUMENTATION_COMPONENTS: Enables GKE Managed + OpenTelemetry Collector and other Instrumentations components like + Instrumentation CRD within the cluster. NONE: Disables the GKE Managed + OpenTelemetry. + + MANAGED_OTEL_SCOPE must be one of: + COLLECTION_AND_INSTRUMENTATION_COMPONENTS, NONE. + --membership-type=MEMBERSHIP_TYPE Specify a membership type for the cluster's fleet membership. Example: $ gcloud alpha container clusters create-auto \ diff --git a/gcloud/alpha/container/clusters/update b/gcloud/alpha/container/clusters/update index 617b473d0..c21473a32 100644 --- a/gcloud/alpha/container/clusters/update +++ b/gcloud/alpha/container/clusters/update @@ -63,7 +63,7 @@ SYNOPSIS --remove-additional-pod-ipv4-ranges=NAME,[NAME,...] | --additional-zones=[ZONE,...] | --node-locations=ZONE,[ZONE,...] | --auto-monitoring-scope=AUTO_MONITORING_SCOPE - --logging=[COMPONENT,...] + --logging=[COMPONENT,...] --managed-otel-scope=MANAGED_OTEL_SCOPE --monitoring=[COMPONENT,...] --disable-managed-prometheus | --enable-managed-prometheus | --binauthz-policy-bindings=[name=BINAUTHZ_POLICY, @@ -1008,6 +1008,17 @@ REQUIRED FLAGS --logging=SYSTEM,API_SERVER,WORKLOAD $ gcloud alpha container clusters update --logging=NONE + --managed-otel-scope=MANAGED_OTEL_SCOPE + Specifies the scope of Managed OpenTelemetry within the cluster. + + COLLECTION_AND_INSTRUMENTATION_COMPONENTS: Enables GKE Managed + OpenTelemetry Collector and other Instrumentations components like + Instrumentation CRD within the cluster. NONE: Disables the GKE + Managed OpenTelemetry. + + MANAGED_OTEL_SCOPE must be one of: + COLLECTION_AND_INSTRUMENTATION_COMPONENTS, NONE. + --monitoring=[COMPONENT,...] Set the components that have monitoring enabled. Valid component values are: SYSTEM, WORKLOAD (Deprecated), NONE, API_SERVER, diff --git a/gcloud/alpha/container/node-pools/create b/gcloud/alpha/container/node-pools/create index bfa54f608..d93b3da36 100644 --- a/gcloud/alpha/container/node-pools/create +++ b/gcloud/alpha/container/node-pools/create @@ -81,6 +81,9 @@ SYNOPSIS | --local-ssd-volumes=[[count=COUNT], [type=TYPE],[format=FORMAT],...]] [--location=LOCATION | --region=REGION | --zone=ZONE, -z ZONE] + [--node-drain-grace-period-seconds=NODE_DRAIN_GRACE_PERIOD_SECONDS + --node-drain-pdb-timeout-seconds=NODE_DRAIN_PDB_TIMEOUT_SECONDS + --respect-pdb-during-node-pool-deletion] [--reservation=RESERVATION --reservation-affinity=RESERVATION_AFFINITY] [--scopes=[SCOPE,...]; default="gke-default" --service-account=SERVICE_ACCOUNT] @@ -236,7 +239,7 @@ FLAGS --confidential-node-type=CONFIDENTIAL_NODE_TYPE Enable confidential nodes for the node pool. Enabling Confidential Nodes will create nodes using Confidential VM - https://cloud.google.com/compute/confidential-vm/docs/about-cvm. + https://docs.cloud.google.com/compute/docs/about-confidential-vm. CONFIDENTIAL_NODE_TYPE must be one of: sev, sev_snp, tdx, disabled. --containerd-config-from-file=PATH_TO_FILE @@ -308,7 +311,7 @@ FLAGS --enable-confidential-nodes Enable confidential nodes for the node pool. Enabling Confidential Nodes will create nodes using Confidential VM - https://cloud.google.com/compute/confidential-vm/docs/about-cvm. + https://docs.cloud.google.com/compute/docs/about-confidential-vm. --enable-confidential-storage Enable confidential storage for the node pool. Enabling Confidential @@ -1103,7 +1106,10 @@ FLAGS [65536, 2147483647] vm.overcommit_memory Must be one of {0, - 1, 2} + 1, 2}. Not + supported on + machines with less + than 15 GB memory. vm.overcommit_ratio Must be between [0, 100] vm.vfs_cache_pressure Must be between @@ -1161,9 +1167,15 @@ FLAGS KEY VALUE diskCount integer - Allocated hugepage size should not exceed 60% of available memory on - the node. For example, c2d-highcpu-4 has 8GB memory, total allocated - hugepage of 2m and 1g should not exceed 8GB * 0.6 = 4.8GB. + The upper limit for total allocated hugepage size differs based upon + machine size. + + ◆ On machines with less than 30 GB memory: 60% of the total memory. + For example, on e2-standard-2 machine with 8 GB of memory, you can't + allocate more than 4.8 GB for hugepages. + ◆ On machines with more than 30 GB memory: 80% of the total memory. + For example, on c4a-standard-8 machines with 32 GB of memory, + hugepages cannot exceed 25.6 GB. 1G hugepages are only available in following machine familes: c3, m2, c2d, c3d, h3, m3, a2, a3, g2. @@ -1516,6 +1528,18 @@ FLAGS Compute zone (e.g. us-central1-a) for a zonal cluster. Overrides the default compute/zone property value for this command invocation. + Node drain settings + + --node-drain-grace-period-seconds=NODE_DRAIN_GRACE_PERIOD_SECONDS + The grace period in seconds for nodes to drain before being + forcefully removed. + + --node-drain-pdb-timeout-seconds=NODE_DRAIN_PDB_TIMEOUT_SECONDS + The timeout in seconds for the node pool to be drained. + + --respect-pdb-during-node-pool-deletion + Whether to respect PDBs when deleting nodes in the node pool. + Specifies the reservation for the node pool. --reservation=RESERVATION diff --git a/gcloud/alpha/container/node-pools/update b/gcloud/alpha/container/node-pools/update index fc4cb09ab..6fbe17287 100644 --- a/gcloud/alpha/container/node-pools/update +++ b/gcloud/alpha/container/node-pools/update @@ -37,7 +37,10 @@ SYNOPSIS --location-policy=LOCATION_POLICY --max-nodes=MAX_NODES --min-nodes=MIN_NODES --total-max-nodes=TOTAL_MAX_NODES --total-min-nodes=TOTAL_MIN_NODES - | --enable-autorepair --enable-autoupgrade) [--async] + | --enable-autorepair --enable-autoupgrade + | --node-drain-grace-period-seconds=NODE_DRAIN_GRACE_PERIOD_SECONDS + --node-drain-pdb-timeout-seconds=NODE_DRAIN_PDB_TIMEOUT_SECONDS + --respect-pdb-during-node-pool-deletion) [--async] [--cluster=CLUSTER] [--location=LOCATION | --region=REGION | --zone=ZONE, -z ZONE] [GCLOUD_WIDE_FLAG ...] @@ -104,7 +107,7 @@ REQUIRED FLAGS --confidential-node-type=CONFIDENTIAL_NODE_TYPE Recreate all the nodes in the node pool to be confidential VM - https://cloud.google.com/compute/confidential-vm/docs/about-cvm. + https://docs.cloud.google.com/compute/docs/about-confidential-vm. CONFIDENTIAL_NODE_TYPE must be one of: sev, sev_snp, tdx, disabled. --containerd-config-from-file=PATH_TO_FILE @@ -123,7 +126,7 @@ REQUIRED FLAGS --enable-confidential-nodes Recreate all the nodes in the node pool to be confidential VM - https://cloud.google.com/compute/confidential-vm/docs/about-cvm. + https://docs.cloud.google.com/compute/docs/about-confidential-vm. --enable-gvnic Enable the use of GVNIC for this cluster. Requires re-creation of @@ -608,7 +611,11 @@ REQUIRED FLAGS [65536, 2147483647] vm.overcommit_memory Must be one of - {0, 1, 2} + {0, 1, 2}. Not + supported on + machines with + less than 15 GB + memory. vm.overcommit_ratio Must be between [0, 100] vm.vfs_cache_pressure Must be between @@ -666,9 +673,15 @@ REQUIRED FLAGS KEY VALUE diskCount integer - Allocated hugepage size should not exceed 60% of available memory on - the node. For example, c2d-highcpu-4 has 8GB memory, total allocated - hugepage of 2m and 1g should not exceed 8GB * 0.6 = 4.8GB. + The upper limit for total allocated hugepage size differs based upon + machine size. + + ▸ On machines with less than 30 GB memory: 60% of the total memory. + For example, on e2-standard-2 machine with 8 GB of memory, you + can't allocate more than 4.8 GB for hugepages. + ▸ On machines with more than 30 GB memory: 80% of the total memory. + For example, on c4a-standard-8 machines with 32 GB of memory, + hugepages cannot exceed 25.6 GB. 1G hugepages are only available in following machine familes: c3, m2, c2d, c3d, h3, m3, a2, a3, g2. @@ -982,6 +995,18 @@ REQUIRED FLAGS https://cloud.google.com/kubernetes-engine/docs/node-auto-upgrades for more info. + Node drain settings + + --node-drain-grace-period-seconds=NODE_DRAIN_GRACE_PERIOD_SECONDS + The grace period in seconds for nodes to drain before being + forcefully removed. + + --node-drain-pdb-timeout-seconds=NODE_DRAIN_PDB_TIMEOUT_SECONDS + The timeout in seconds for the node pool to be drained. + + --respect-pdb-during-node-pool-deletion + Whether to respect PDBs when deleting nodes in the node pool. + OPTIONAL FLAGS --async Return immediately, without waiting for the operation in progress to diff --git a/gcloud/alpha/dataplex/datascans/create/data-documentation b/gcloud/alpha/dataplex/datascans/create/data-documentation index 4e48e3bc7..f7423698e 100644 --- a/gcloud/alpha/dataplex/datascans/create/data-documentation +++ b/gcloud/alpha/dataplex/datascans/create/data-documentation @@ -9,7 +9,9 @@ SYNOPSIS | --data-source-resource=DATA_SOURCE_RESOURCE) [--description=DESCRIPTION] [--display-name=DISPLAY_NAME] [--labels=[KEY=VALUE,...]] [--async | --validate-only] - [--on-demand=ON_DEMAND | --schedule=SCHEDULE] [GCLOUD_WIDE_FLAG ...] + [--on-demand=ON_DEMAND | --schedule=SCHEDULE + | --one-time --ttl-after-scan-completion=TTL_AFTER_SCAN_COMPLETION] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Allows users to generate documentation for Dataplex BigQuery @@ -102,7 +104,7 @@ OPTIONAL FLAGS Data documentation scan execution settings. - Data documentation scan scheduling and trigger settings. + Data documentation scan trigger settings. At most one of these can be specified: @@ -117,7 +119,24 @@ OPTIONAL FLAGS "TZ=${IANA_TIME_ZONE}". The ${IANA_TIME_ZONE} may only be a valid string from IANA time zone database. For example, CRON_TZ=America/New_York 1 * * * * or TZ=America/New_York 1 * * * - *. This field is required for RECURRING scans. + *. This field is required for RECURRING scans. The argument is only + valid when --on-demand is not set. + + Data documentation scan one-time trigger settings. + + --one-time + If set, the data documentation scan runs once, and is + auto-deleted once the ttl_after_scan_completion expires. + + --ttl-after-scan-completion=TTL_AFTER_SCAN_COMPLETION + The time to live for one-time scans. Default value is 24 hours, + minimum value is 0 seconds, and maximum value is 365 days. The + time is calculated from the data scan job completion time. If + value is set as 0 seconds, the scan will be immediately deleted + upon job completion, regardless of whether the job succeeded or + failed. The value should be a number followed by a unit suffix + "s". Example: "100s" for 100 seconds. The argument is only valid + when --one-time is set. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/dataplex/datascans/create/data-profile b/gcloud/alpha/dataplex/datascans/create/data-profile index df493d65a..90ff5feec 100644 --- a/gcloud/alpha/dataplex/datascans/create/data-profile +++ b/gcloud/alpha/dataplex/datascans/create/data-profile @@ -10,7 +10,8 @@ SYNOPSIS [--description=DESCRIPTION] [--display-name=DISPLAY_NAME] [--labels=[KEY=VALUE,...]] [--async | --validate-only] [--data-profile-spec-file=DATA_PROFILE_SPEC_FILE - | --exclude-field-names=EXCLUDE_FIELD_NAMES + | --enable-catalog-publishing + --exclude-field-names=EXCLUDE_FIELD_NAMES --export-results-table=EXPORT_RESULTS_TABLE --include-field-names=INCLUDE_FIELD_NAMES --row-filter=ROW_FILTER --sampling-percent=SAMPLING_PERCENT] @@ -120,6 +121,9 @@ OPTIONAL FLAGS Command line spec arguments for the data profile scan. + --enable-catalog-publishing + Publish data profile results to Dataplex catalog. + --exclude-field-names=EXCLUDE_FIELD_NAMES Names of the fields to exclude from data profile. If specified, the respective fields will be excluded from data profile, regardless of diff --git a/gcloud/alpha/dataplex/datascans/update/data-documentation b/gcloud/alpha/dataplex/datascans/update/data-documentation index a320289a7..1439f2121 100644 --- a/gcloud/alpha/dataplex/datascans/update/data-documentation +++ b/gcloud/alpha/dataplex/datascans/update/data-documentation @@ -7,7 +7,9 @@ SYNOPSIS (DATASCAN : --location=LOCATION) [--description=DESCRIPTION] [--display-name=DISPLAY_NAME] [--labels=[KEY=VALUE,...]] [--async | --validate-only] - [--on-demand=ON_DEMAND | --schedule=SCHEDULE] [GCLOUD_WIDE_FLAG ...] + [--on-demand=ON_DEMAND | --schedule=SCHEDULE + | --one-time --ttl-after-scan-completion=TTL_AFTER_SCAN_COMPLETION] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Update a Dataplex data documentation scan job. @@ -81,7 +83,7 @@ FLAGS Data documentation scan execution settings. - Data documentation scan scheduling and trigger settings. + Data documentation scan trigger settings. At most one of these can be specified: @@ -98,6 +100,22 @@ FLAGS CRON_TZ=America/New_York 1 * * * * or TZ=America/New_York 1 * * * *. This field is required for RECURRING scans. + Data documentation scan one-time trigger settings. + + --one-time + If set, the data documentation scan runs once, and auto deleted + once the ttl_after_scan_completion expires. + + --ttl-after-scan-completion=TTL_AFTER_SCAN_COMPLETION + The time to live for one-time scans. Default value is 24 hours, + minimum value is 0 seconds, and maximum value is 365 days. The + time is calculated from the data scan job completion time. If + value is set as 0 seconds, the scan will be immediately deleted + upon job completion, regardless of whether the job succeeded or + failed. The value should be a number followed by a unit suffix + "s". Example: "100s" for 100 seconds. The argument is only valid + when --one-time is set. + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/alpha/dataplex/datascans/update/data-profile b/gcloud/alpha/dataplex/datascans/update/data-profile index 2f5522176..8a9ca98b1 100644 --- a/gcloud/alpha/dataplex/datascans/update/data-profile +++ b/gcloud/alpha/dataplex/datascans/update/data-profile @@ -8,7 +8,8 @@ SYNOPSIS [--display-name=DISPLAY_NAME] [--labels=[KEY=VALUE,...]] [--async | --validate-only] [--data-profile-spec-file=DATA_PROFILE_SPEC_FILE - | --exclude-field-names=EXCLUDE_FIELD_NAMES + | --enable-catalog-publishing + --exclude-field-names=EXCLUDE_FIELD_NAMES --include-field-names=INCLUDE_FIELD_NAMES --row-filter=ROW_FILTER --sampling-percent=SAMPLING_PERCENT] [--on-demand=ON_DEMAND | --schedule=SCHEDULE] [GCLOUD_WIDE_FLAG ...] @@ -96,6 +97,9 @@ FLAGS Command line spec arguments for the data profile scan. + --enable-catalog-publishing + Publish data profile results to Dataplex catalog. + --exclude-field-names=EXCLUDE_FIELD_NAMES Names of the fields to exclude from data profile. If specified, the respective fields will be excluded from data profile, regardless of diff --git a/gcloud/alpha/design-center/operations/help b/gcloud/alpha/design-center/operations/help index 3762cabb2..ab613bd74 100644 --- a/gcloud/alpha/design-center/operations/help +++ b/gcloud/alpha/design-center/operations/help @@ -27,6 +27,9 @@ COMMANDS list (ALPHA) List operations. + wait + (ALPHA) Wait for an operation to complete. + NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct diff --git a/gcloud/alpha/design-center/operations/wait b/gcloud/alpha/design-center/operations/wait new file mode 100644 index 000000000..befb21596 --- /dev/null +++ b/gcloud/alpha/design-center/operations/wait @@ -0,0 +1,70 @@ +NAME + gcloud alpha design-center operations wait - wait for an operation to + complete + +SYNOPSIS + gcloud alpha design-center operations wait + (OPERATION : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Wait for an operation to complete + +EXAMPLES + To wait for the operation myOperation to complete in project my-project and + location us-central1, run: + + $ gcloud alpha design-center operations wait myOperation \ + --project=my-project --location=us-central1 + +POSITIONAL ARGUMENTS + Operation resource - The name of the operation resource to wait on. The + arguments in this group can be used to specify the attributes of this + resource. (NOTE) Some attributes are not given arguments in this group but + can be set in other ways. + + To set the project attribute: + ◆ provide the argument operation on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + OPERATION + ID of the operation or fully qualified identifier for the operation. + + To set the operation attribute: + ▸ provide the argument operation on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The location id of the operation resource. + + To set the location attribute: + ▸ provide the argument operation on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the designcenter/v1alpha API. The full documentation for + this API can be found at: + http://cloud.google.com/application-design-center/docs + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud design-center operations wait + diff --git a/gcloud/alpha/design-center/spaces/applications/create b/gcloud/alpha/design-center/spaces/applications/create index 10910585d..3f31a5f5a 100644 --- a/gcloud/alpha/design-center/spaces/applications/create +++ b/gcloud/alpha/design-center/spaces/applications/create @@ -26,7 +26,7 @@ SYNOPSIS : --criticality-level=CRITICALITY_LEVEL --criticality-mission-critical] [--environment-type=ENVIRONMENT_TYPE : --environment=ENVIRONMENT]] - [--gke-deployment-target-cluster-self-link=GKE_DEPLOYMENT_TARGET_CLUSTER_SELF_LINK --gke-deployment-target-kubernetes-service-account=GKE_DEPLOYMENT_TARGET_KUBERNETES_SERVICE_ACCOUNT --gke-deployment-target-namespace=GKE_DEPLOYMENT_TARGET_NAMESPACE] + [--gke-deployment-target-cluster-self-link=GKE_DEPLOYMENT_TARGET_CLUSTER_SELF_LINK --gke-deployment-target-kubernetes-service-account=GKE_DEPLOYMENT_TARGET_KUBERNETES_SERVICE_ACCOUNT --gke-deployment-target-namespace=GKE_DEPLOYMENT_TARGET_NAMESPACE : --gke-deployment-target-kubernetes-service-account-creation] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -401,6 +401,11 @@ OPTIONAL FLAGS This flag argument must be specified if any of the other arguments in this group are specified. + --gke-deployment-target-kubernetes-service-account-creation + Whether to create the provided KSA. If true, the KSA will be + created in the namespace provided above. If false, the KSA is + expected to already exist in the namespace provided above. + 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/design-center/spaces/applications/deploy b/gcloud/alpha/design-center/spaces/applications/deploy index e8d399524..ec15b019c 100644 --- a/gcloud/alpha/design-center/spaces/applications/deploy +++ b/gcloud/alpha/design-center/spaces/applications/deploy @@ -4,9 +4,9 @@ NAME SYNOPSIS gcloud alpha design-center spaces applications deploy - (APPLICATION : --location=LOCATION --space=SPACE) [--async] [--replace] - [--service-account=SERVICE_ACCOUNT] [--worker-pool=WORKER_POOL] - [GCLOUD_WIDE_FLAG ...] + (APPLICATION : --location=LOCATION --space=SPACE) [--async] + [--create-sa] [--replace] [--service-account=SERVICE_ACCOUNT] + [--worker-pool=WORKER_POOL] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Deploy an application in a space. @@ -16,13 +16,13 @@ EXAMPLES my-project and location us-central1, run: $ gcloud alpha design-center spaces applications deploy \ - my-application --space=my-space --project=my-project \ - --location=us-central1 + my-application --space=my-space --project=my-project \ + --location=us-central1 Or run: $ gcloud alpha design-center spaces applications deploy \ - projects/my-project/locations/us-central1/spaces/my-space/\ + projects/my-project/locations/us-central1/spaces/my-space/\ applications/my-application To deploy the application my-application in space my-space, project @@ -30,35 +30,59 @@ EXAMPLES run: $ gcloud alpha design-center spaces applications deploy \ - my-application --space=my-space --project=my-project \ - --location=us-central1 --replace + my-application --space=my-space --project=my-project \ + --location=us-central1 --replace To deploy the application my-application in space my-space, project my-project and location us-central1 using a worker pool projects/my-project/locations/us-central1/workerPools/my-worker-pool, run: $ gcloud alpha design-center spaces applications deploy \ - my-application --space=my-space --project=my-project \ - --location=us-central1 \ - --worker-pool=projects/my-project/locations/us-central1/\ + my-application --space=my-space --project=my-project \ + --location=us-central1 \ + --worker-pool=projects/my-project/locations/us-central1/\ workerPools/my-worker-pool + To deploy the application my-application and create a new service account + for the deployment, run: + + $ gcloud alpha design-center spaces applications deploy \ + my-application --space=my-space --project=my-project \ + --location=us-central1 --create-sa + + To deploy the application my-application and create a new service account + and create a specific service account for the deployment, run: + + $ gcloud alpha design-center spaces applications deploy \ + my-application --space=my-space --project=my-project \ + --location=us-central1 --create-sa \ + --service-account=my-service-account@my-project.iam.gserviceacco\ + unt.com + + To deploy the application my-application and use a specific service account + for the deployment, run: + + $ gcloud alpha design-center spaces applications deploy \ + my-application --space=my-space --project=my-project \ + --location=us-central1 \ + --service-account=projects/my-project/serviceAccounts/\ + my-service-account@my-project.iam.gserviceaccount.com + To deploy the application my-application in space my-space, project my-project and location us-central1 asynchronously, run: $ gcloud alpha design-center spaces applications deploy \ - my-application --space=my-space --project=my-project \ - --location=us-central1 --async + my-application --space=my-space --project=my-project \ + --location=us-central1 --async POSITIONAL ARGUMENTS - Application resource - The application name. Format: - projects/$project/locations/$location/spaces/$space/applications/$application - The arguments in this group can be used to specify the attributes of this - resource. (NOTE) Some attributes are not given arguments in this group but - can be set in other ways. + Application resource - The application to deploy IaC. The arguments in + this group can be used to specify the attributes of this resource. (NOTE) + Some attributes are not given arguments in this group but can be set in + other ways. To set the project attribute: - ◆ provide the argument application on the command line with a fully + ◆ provide the argument APPLICATION on the command line with a fully specified name; ◆ provide the argument --project on the command line; ◆ set the property core/project. @@ -70,24 +94,24 @@ POSITIONAL ARGUMENTS application. To set the application attribute: - ▸ provide the argument application on the command line. + ▸ provide the argument APPLICATION on the command line. This positional argument must be specified if any of the other arguments in this group are specified. --location=LOCATION - The location id of the application resource. + The Cloud location for the application. To set the location attribute: - ▸ provide the argument application on the command line with a fully + ▸ provide the argument APPLICATION on the command line with a fully specified name; ▸ provide the argument --location on the command line. --space=SPACE - The space id of the application resource. + The ID of the space. To set the space attribute: - ▸ provide the argument application on the command line with a fully + ▸ provide the argument APPLICATION on the command line with a fully specified name; ▸ provide the argument --space on the command line. @@ -96,24 +120,34 @@ FLAGS Return immediately, without waiting for the operation in progress to complete. + --create-sa + Create a new service account for the deployment. + --replace Flag to update the existing deployment. If not set or false, deploy will fail if application state is in the DEPLOYED state. --service-account=SERVICE_ACCOUNT - The email address of the service account to use for this deployment. + The service account to use for this deployment. ◆ If provided, this service account will be used to execute the deployment process, taking precedence over any service_account specified on the Application resource. - ◆ The caller must have the 'iam.serviceAccounts.actAs' permission on + ◆ The caller must have the "iam.serviceAccounts.actAs" permission on this service account. - ◆ If this field is omitted, the system will use the 'service_account' + ◆ If this field is omitted, the system will use the "service_account" defined within the Application resource. + ◆ If this field is omitted with --create-sa flag, the system will + create a new and unique service_account and use it for the + deployment. ◆ We recommend that you provide a service account here or on the Application resource. If you don't provide a service account, the - deployment will fail. Format: - projects/{PROJECT}/serviceAccounts/{EMAIL_ADDRESS} + deployment will fail. + ◆ If the --create-sa flag is also provided, this value is the ID of a + new service account to be created (e.g., my-new-sa). + + Format: projects/{PROJECT}/serviceAccounts/{EMAIL_ADDRESS} (when not + using --create-sa) --worker-pool=WORKER_POOL The user-specified Worker Pool resource in which the Cloud Build job @@ -132,11 +166,6 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. -API REFERENCE - This command uses the designcenter/v1alpha API. The full documentation for - this API can be found at: - http://cloud.google.com/application-design-center/docs - NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct diff --git a/gcloud/alpha/design-center/spaces/applications/help b/gcloud/alpha/design-center/spaces/applications/help index fc4ff69e6..c9469280d 100644 --- a/gcloud/alpha/design-center/spaces/applications/help +++ b/gcloud/alpha/design-center/spaces/applications/help @@ -39,7 +39,7 @@ COMMANDS (ALPHA) List applications. preview - (ALPHA) Preview an application. + (ALPHA) Preview a Design Center application. register (ALPHA) Register resources with a deployed application in App Hub. diff --git a/gcloud/alpha/design-center/spaces/applications/preview b/gcloud/alpha/design-center/spaces/applications/preview index d9ce4e1df..43a835929 100644 --- a/gcloud/alpha/design-center/spaces/applications/preview +++ b/gcloud/alpha/design-center/spaces/applications/preview @@ -1,12 +1,12 @@ NAME - gcloud alpha design-center spaces applications preview - preview an - application + gcloud alpha design-center spaces applications preview - preview a Design + Center application SYNOPSIS gcloud alpha design-center spaces applications preview (APPLICATION : --location=LOCATION --space=SPACE) [--async] - [--service-account=SERVICE_ACCOUNT] [--worker-pool=WORKER_POOL] - [GCLOUD_WIDE_FLAG ...] + [--create-sa] [--service-account=SERVICE_ACCOUNT] + [--worker-pool=WORKER_POOL] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Preview an application in a space. @@ -16,13 +16,13 @@ EXAMPLES my-project and location us-central1, run: $ gcloud alpha design-center spaces applications preview \ - my-application --space=my-space --project=my-project \ - --location=us-central1 + my-application --space=my-space --project=my-project \ + --location=us-central1 Or run: $ gcloud alpha design-center spaces applications preview \ - projects/my-project/locations/us-central1/spaces/my-space/\ + projects/my-project/locations/us-central1/spaces/my-space/\ applications/my-application To preview the application my-application in space my-space, project @@ -30,27 +30,51 @@ EXAMPLES projects/my-project/locations/us-central1/workerPools/my-worker-pool, run: $ gcloud alpha design-center spaces applications preview \ - my-application --space=my-space --project=my-project \ - --location=us-central1 \ - --worker-pool=projects/my-project/locations/us-central1/\ + my-application --space=my-space --project=my-project \ + --location=us-central1 \ + --worker-pool=projects/my-project/locations/us-central1/\ workerPools/my-worker-pool + To preview the application my-application and create a new service account + for the preview, run: + + $ gcloud alpha design-center spaces applications preview \ + my-application --space=my-space --project=my-project \ + --location=us-central1 --create-sa + + To preview the application my-application and create a new provided service + account for the preview, run: + + $ gcloud alpha design-center spaces applications preview \ + my-application --space=my-space --project=my-project \ + --location=us-central1 --create-sa \ + --service-account=my-service-account@my-project.iam.gserviceacco\ + unt.com + + To preview the application my-application and use a specific existing + service account for the preview, run: + + $ gcloud alpha design-center spaces applications preview \ + my-application --space=my-space --project=my-project \ + --location=us-central1 \ + --service-account=projects/my-project/serviceAccounts/\ + my-service-account@my-project.iam.gserviceaccount.com + To preview the application my-application in space my-space, project my-project and location us-central1 asynchronously, run: $ gcloud alpha design-center spaces applications preview \ - my-application --space=my-space --project=my-project \ - --location=us-central1 --async + my-application --space=my-space --project=my-project \ + --location=us-central1 --async POSITIONAL ARGUMENTS - Application resource - The application name in the following format: - projects/$project/locations/$location/spaces/$space/applications/$application - The arguments in this group can be used to specify the attributes of this - resource. (NOTE) Some attributes are not given arguments in this group but - can be set in other ways. + Application resource - The application to preview IaC. The arguments in + this group can be used to specify the attributes of this resource. (NOTE) + Some attributes are not given arguments in this group but can be set in + other ways. To set the project attribute: - ◆ provide the argument application on the command line with a fully + ◆ provide the argument APPLICATION on the command line with a fully specified name; ◆ provide the argument --project on the command line; ◆ set the property core/project. @@ -62,24 +86,24 @@ POSITIONAL ARGUMENTS application. To set the application attribute: - ▸ provide the argument application on the command line. + ▸ provide the argument APPLICATION on the command line. This positional argument must be specified if any of the other arguments in this group are specified. --location=LOCATION - The location id of the application resource. + The Cloud location for the application. To set the location attribute: - ▸ provide the argument application on the command line with a fully + ▸ provide the argument APPLICATION on the command line with a fully specified name; ▸ provide the argument --location on the command line. --space=SPACE - The space id of the application resource. + The ID of the space. To set the space attribute: - ▸ provide the argument application on the command line with a fully + ▸ provide the argument APPLICATION on the command line with a fully specified name; ▸ provide the argument --space on the command line. @@ -88,21 +112,29 @@ FLAGS Return immediately, without waiting for the operation in progress to complete. + --create-sa + Create a new service account for the preview. + --service-account=SERVICE_ACCOUNT - The email address of the service account to use for this preview - operation. + The service account to use for this preview. ◆ If provided, this service account will be used to execute the preview process, taking precedence over any service_account specified on the Application resource. - ◆ The caller must have the 'iam.serviceAccounts.actAs' permission on + ◆ The caller must have the "iam.serviceAccounts.actAs" permission on this service account. - ◆ If this field is omitted, the system will use the 'service_account' + ◆ If this field is omitted, the system will use the "service_account" defined within the Application resource. + ◆ If this field is omitted with --create-sa flag, the system will + create a new and unique service_account and use it for the preview. ◆ We recommend that you provide a service account here or on the Application resource. If you don't provide a service account, the - preview will fail. Format: - projects/{PROJECT}/serviceAccounts/{EMAIL_ADDRESS} + preview will fail. + ◆ If the --create-sa flag is also provided, this value is the ID of a + new service account to be created (e.g., my-new-sa). + + Format: projects/{PROJECT}/serviceAccounts/{EMAIL_ADDRESS} (when not + using --create-sa) --worker-pool=WORKER_POOL The user-specified Worker Pool resource in which the Cloud Build job @@ -121,11 +153,6 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. -API REFERENCE - This command uses the designcenter/v1alpha API. The full documentation for - this API can be found at: - http://cloud.google.com/application-design-center/docs - NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct diff --git a/gcloud/alpha/design-center/spaces/applications/update b/gcloud/alpha/design-center/spaces/applications/update index f3cbe4fe5..da6819b1c 100644 --- a/gcloud/alpha/design-center/spaces/applications/update +++ b/gcloud/alpha/design-center/spaces/applications/update @@ -39,7 +39,7 @@ SYNOPSIS --criticality-type=CRITICALITY_TYPE --environment=ENVIRONMENT --environment-type=ENVIRONMENT_TYPE] [--clear-deployment-target - --gke-deployment-target-cluster-self-link=GKE_DEPLOYMENT_TARGET_CLUSTER_SELF_LINK --gke-deployment-target-kubernetes-service-account=GKE_DEPLOYMENT_TARGET_KUBERNETES_SERVICE_ACCOUNT --gke-deployment-target-namespace=GKE_DEPLOYMENT_TARGET_NAMESPACE] + --gke-deployment-target-cluster-self-link=GKE_DEPLOYMENT_TARGET_CLUSTER_SELF_LINK --gke-deployment-target-kubernetes-service-account=GKE_DEPLOYMENT_TARGET_KUBERNETES_SERVICE_ACCOUNT --[no-]gke-deployment-target-kubernetes-service-account-creation --gke-deployment-target-namespace=GKE_DEPLOYMENT_TARGET_NAMESPACE] [--clear-scope --scope-type=SCOPE_TYPE] [--clear-source --source-application-template-revision=SOURCE_APPLICATION_TEMPLATE_REVISION | --source-shared-template-revision-uri=SOURCE_SHARED_TEMPLATE_REVISION_URI] @@ -617,6 +617,15 @@ FLAGS The kubernetes service account that is created within the namespace provided above. Example: default or node-sa + --[no-]gke-deployment-target-kubernetes-service-account-creation + Whether to create the provided KSA. If true, the KSA will be + created in the namespace provided above. If false, the KSA is + expected to already exist in the namespace provided above. Use + --gke-deployment-target-kubernetes-service-account-creation to + enable and + --no-gke-deployment-target-kubernetes-service-account-creation to + disable. + --gke-deployment-target-namespace=GKE_DEPLOYMENT_TARGET_NAMESPACE The namespace where the application is deployed. diff --git a/gcloud/alpha/developer-connect/connections/create b/gcloud/alpha/developer-connect/connections/create index fecab6335..125696ce3 100644 --- a/gcloud/alpha/developer-connect/connections/create +++ b/gcloud/alpha/developer-connect/connections/create @@ -8,7 +8,7 @@ SYNOPSIS [--git-proxy-config-enabled] [--labels=[LABELS,...]] [--location=LOCATION] [--namespace=NAMESPACE] [--request-id=REQUEST_ID] [--secret=SECRET] [--validate-only] - [--bitbucket-cloud-config-authorizer-credential-user-token-secret-version=BITBUCKET_CLOUD_CONFIG_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --bitbucket-cloud-config-read-authorizer-credential-user-token-secret-version=BITBUCKET_CLOUD_CONFIG_READ_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --bitbucket-cloud-config-webhook-secret-version=BITBUCKET_CLOUD_CONFIG_WEBHOOK_SECRET_VERSION --bitbucket-cloud-config-workspace=BITBUCKET_CLOUD_CONFIG_WORKSPACE | [--bitbucket-data-center-config-authorizer-credential-user-token-secret-version=BITBUCKET_DATA_CENTER_CONFIG_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --bitbucket-data-center-config-host-uri=BITBUCKET_DATA_CENTER_CONFIG_HOST_URI --bitbucket-data-center-config-read-authorizer-credential-user-token-secret-version=BITBUCKET_DATA_CENTER_CONFIG_READ_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --bitbucket-data-center-config-webhook-secret-version=BITBUCKET_DATA_CENTER_CONFIG_WEBHOOK_SECRET_VERSION : --bitbucket-data-center-config-service-directory=BITBUCKET_DATA_CENTER_CONFIG_SERVICE_DIRECTORY --bitbucket-data-center-config-ssl-ca-certificate=BITBUCKET_DATA_CENTER_CONFIG_SSL_CA_CERTIFICATE] | [--github-config-app=GITHUB_CONFIG_APP : --github-config-app-installation-id=GITHUB_CONFIG_APP_INSTALLATION_ID --github-config-authorizer-credential-oauth-token-secret-version=GITHUB_CONFIG_AUTHORIZER_CREDENTIAL_OAUTH_TOKEN_SECRET_VERSION] | [--github-enterprise-config-host-uri=GITHUB_ENTERPRISE_CONFIG_HOST_URI : --github-enterprise-config-app-id=GITHUB_ENTERPRISE_CONFIG_APP_ID --github-enterprise-config-app-installation-id=GITHUB_ENTERPRISE_CONFIG_APP_INSTALLATION_ID --github-enterprise-config-private-key-secret-version=GITHUB_ENTERPRISE_CONFIG_PRIVATE_KEY_SECRET_VERSION --github-enterprise-config-service-directory=GITHUB_ENTERPRISE_CONFIG_SERVICE_DIRECTORY --github-enterprise-config-ssl-ca-certificate=GITHUB_ENTERPRISE_CONFIG_SSL_CA_CERTIFICATE --github-enterprise-config-webhook-secret-version=GITHUB_ENTERPRISE_CONFIG_WEBHOOK_SECRET_VERSION] | --gitlab-config-authorizer-credential-user-token-secret-version=GITLAB_CONFIG_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --gitlab-config-read-authorizer-credential-user-token-secret-version=GITLAB_CONFIG_READ_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --gitlab-config-webhook-secret-version=GITLAB_CONFIG_WEBHOOK_SECRET_VERSION | [--gitlab-enterprise-config-authorizer-credential-user-token-secret-version=GITLAB_ENTERPRISE_CONFIG_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --gitlab-enterprise-config-host-uri=GITLAB_ENTERPRISE_CONFIG_HOST_URI --gitlab-enterprise-config-read-authorizer-credential-user-token-secret-version=GITLAB_ENTERPRISE_CONFIG_READ_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --gitlab-enterprise-config-webhook-secret-version=GITLAB_ENTERPRISE_CONFIG_WEBHOOK_SECRET_VERSION : --gitlab-enterprise-config-service-directory=GITLAB_ENTERPRISE_CONFIG_SERVICE_DIRECTORY --gitlab-enterprise-config-ssl-ca-certificate=GITLAB_ENTERPRISE_CONFIG_SSL_CA_CERTIFICATE]] + [--bitbucket-cloud-config-authorizer-credential-user-token-secret-version=BITBUCKET_CLOUD_CONFIG_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --bitbucket-cloud-config-read-authorizer-credential-user-token-secret-version=BITBUCKET_CLOUD_CONFIG_READ_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --bitbucket-cloud-config-webhook-secret-version=BITBUCKET_CLOUD_CONFIG_WEBHOOK_SECRET_VERSION --bitbucket-cloud-config-workspace=BITBUCKET_CLOUD_CONFIG_WORKSPACE | [--bitbucket-data-center-config-authorizer-credential-user-token-secret-version=BITBUCKET_DATA_CENTER_CONFIG_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --bitbucket-data-center-config-host-uri=BITBUCKET_DATA_CENTER_CONFIG_HOST_URI --bitbucket-data-center-config-read-authorizer-credential-user-token-secret-version=BITBUCKET_DATA_CENTER_CONFIG_READ_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --bitbucket-data-center-config-webhook-secret-version=BITBUCKET_DATA_CENTER_CONFIG_WEBHOOK_SECRET_VERSION : --bitbucket-data-center-config-service-directory=BITBUCKET_DATA_CENTER_CONFIG_SERVICE_DIRECTORY --bitbucket-data-center-config-ssl-ca-certificate=BITBUCKET_DATA_CENTER_CONFIG_SSL_CA_CERTIFICATE] | [--github-config-app=GITHUB_CONFIG_APP : --github-config-app-installation-id=GITHUB_CONFIG_APP_INSTALLATION_ID --github-config-authorizer-credential-oauth-token-secret-version=GITHUB_CONFIG_AUTHORIZER_CREDENTIAL_OAUTH_TOKEN_SECRET_VERSION] | [--github-enterprise-config-host-uri=GITHUB_ENTERPRISE_CONFIG_HOST_URI : --github-enterprise-config-app-id=GITHUB_ENTERPRISE_CONFIG_APP_ID --github-enterprise-config-app-installation-id=GITHUB_ENTERPRISE_CONFIG_APP_INSTALLATION_ID --github-enterprise-config-private-key-secret-version=GITHUB_ENTERPRISE_CONFIG_PRIVATE_KEY_SECRET_VERSION --github-enterprise-config-service-directory=GITHUB_ENTERPRISE_CONFIG_SERVICE_DIRECTORY --github-enterprise-config-ssl-ca-certificate=GITHUB_ENTERPRISE_CONFIG_SSL_CA_CERTIFICATE --github-enterprise-config-webhook-secret-version=GITHUB_ENTERPRISE_CONFIG_WEBHOOK_SECRET_VERSION] | --gitlab-config-authorizer-credential-user-token-secret-version=GITLAB_CONFIG_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --gitlab-config-read-authorizer-credential-user-token-secret-version=GITLAB_CONFIG_READ_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --gitlab-config-webhook-secret-version=GITLAB_CONFIG_WEBHOOK_SECRET_VERSION | [--gitlab-enterprise-config-authorizer-credential-user-token-secret-version=GITLAB_ENTERPRISE_CONFIG_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --gitlab-enterprise-config-host-uri=GITLAB_ENTERPRISE_CONFIG_HOST_URI --gitlab-enterprise-config-read-authorizer-credential-user-token-secret-version=GITLAB_ENTERPRISE_CONFIG_READ_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --gitlab-enterprise-config-webhook-secret-version=GITLAB_ENTERPRISE_CONFIG_WEBHOOK_SECRET_VERSION : --gitlab-enterprise-config-service-directory=GITLAB_ENTERPRISE_CONFIG_SERVICE_DIRECTORY --gitlab-enterprise-config-ssl-ca-certificate=GITLAB_ENTERPRISE_CONFIG_SSL_CA_CERTIFICATE] | [--http-config-host-uri=HTTP_CONFIG_HOST_URI : --http-config-service-directory=HTTP_CONFIG_SERVICE_DIRECTORY --http-config-ssl-ca-certificate=HTTP_CONFIG_SSL_CA_CERTIFICATE --http-config-bearer-token-authentication-secret-version=HTTP_CONFIG_BEARER_TOKEN_AUTHENTICATION_SECRET_VERSION | [--http-config-basic-authentication-username=HTTP_CONFIG_BASIC_AUTHENTICATION_USERNAME : --http-config-basic-authentication-password-secret-version=HTTP_CONFIG_BASIC_AUTHENTICATION_PASSWORD_SECRET_VERSION]]] [(--crypto-key-config-reference=CRYPTO_KEY_CONFIG_REFERENCE : --key-ring=KEY_RING)] [GCLOUD_WIDE_FLAG ...] @@ -1019,6 +1019,142 @@ FLAGS SSL Certificate Authority certificate to use for requests to GitLab Enterprise instance. + Configuration for connections to an HTTP service provider. + + --http-config-host-uri=HTTP_CONFIG_HOST_URI + The service provider's https endpoint. + + This flag argument must be specified if any of the other arguments + in this group are specified. + + ServiceDirectoryConfig represents Service Directory configuration for + a connection. + + Service resource - The Service Directory service name. Format: + projects/{project}/locations/{location}/namespaces/{namespace}/services/{service}. + 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 --http-config-service-directory on the + command line with a fully specified name; + ◇ provide the argument --project on the command line; + ◇ set the property core/project. + + To set the location attribute: + ◇ provide the argument --http-config-service-directory on the + command line with a fully specified name; + ◇ provide the argument --location on the command line. + + To set the namespace attribute: + ◇ provide the argument --http-config-service-directory on the + command line with a fully specified name; + ◇ provide the argument --namespace on the command line. + + This must be specified. + + --http-config-service-directory=HTTP_CONFIG_SERVICE_DIRECTORY + ID of the service or fully qualified identifier for the + service. + + To set the service attribute: + ▹ provide the argument --http-config-service-directory on the + command line. + + --http-config-ssl-ca-certificate=HTTP_CONFIG_SSL_CA_CERTIFICATE + The SSL certificate to use for requests to the HTTP service + provider. + + Arguments for the authentication. + + At most one of these can be specified: + + Bearer token authentication with a token. + + Arguments for the token. + + SecretVersion resource - The token SecretManager secret version + to authenticate as. 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 + --http-config-bearer-token-authentication-secret-version on + the command line with a fully specified name; + ▪ provide the argument --project on the command line; + ▪ set the property core/project. + + To set the location attribute: + ▪ provide the argument + --http-config-bearer-token-authentication-secret-version on + the command line with a fully specified name; + ▪ provide the argument --location on the command line. + + To set the secret attribute: + ▪ provide the argument + --http-config-bearer-token-authentication-secret-version on + the command line with a fully specified name; + ▪ provide the argument --secret on the command line. This + resource can be one of the following types: + [developerconnect.projects.locations.secrets.versions, + developerconnect.projects.secrets.versions]. + + --http-config-bearer-token-authentication-secret-version=HTTP_CONFIG_BEARER_TOKEN_AUTHENTICATION_SECRET_VERSION + ID of the secretVersion or fully qualified identifier for + the secretVersion. + + To set the secret_version attribute: + ◆ provide the argument + --http-config-bearer-token-authentication-secret-version + on the command line. + + Basic authentication with username and password. + + --http-config-basic-authentication-username=HTTP_CONFIG_BASIC_AUTHENTICATION_USERNAME + The username to authenticate as. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + Arguments for the password. + + SecretVersion resource - The password SecretManager secret + version to authenticate as. 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 + --http-config-basic-authentication-password-secret-version on + the command line with a fully specified name; + ▪ provide the argument --project on the command line; + ▪ set the property core/project. + + To set the location attribute: + ▪ provide the argument + --http-config-basic-authentication-password-secret-version on + the command line with a fully specified name; + ▪ provide the argument --location on the command line. + + To set the secret attribute: + ▪ provide the argument + --http-config-basic-authentication-password-secret-version on + the command line with a fully specified name; + ▪ provide the argument --secret on the command line. This + resource can be one of the following types: + [developerconnect.projects.locations.secrets.versions, + developerconnect.projects.secrets.versions]. + + --http-config-basic-authentication-password-secret-version=HTTP_CONFIG_BASIC_AUTHENTICATION_PASSWORD_SECRET_VERSION + ID of the secretVersion or fully qualified identifier for + the secretVersion. + + To set the secret_version attribute: + ◆ provide the argument + --http-config-basic-authentication-password-secret-version + on the command line. + The crypto key configuration. This field is used by the Customer-managed encryption keys (CMEK) feature. diff --git a/gcloud/alpha/developer-connect/connections/update b/gcloud/alpha/developer-connect/connections/update index 0e4d763cf..8e86801b7 100644 --- a/gcloud/alpha/developer-connect/connections/update +++ b/gcloud/alpha/developer-connect/connections/update @@ -10,7 +10,7 @@ SYNOPSIS [--annotations=[ANNOTATIONS,...] | --update-annotations=[UPDATE_ANNOTATIONS,...] --clear-annotations | --remove-annotations=REMOVE_ANNOTATIONS] - [--bitbucket-cloud-config-authorizer-credential-user-token-secret-version=BITBUCKET_CLOUD_CONFIG_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --bitbucket-cloud-config-read-authorizer-credential-user-token-secret-version=BITBUCKET_CLOUD_CONFIG_READ_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --bitbucket-cloud-config-workspace=BITBUCKET_CLOUD_CONFIG_WORKSPACE --clear-bitbucket-cloud-config | --bitbucket-data-center-config-authorizer-credential-user-token-secret-version=BITBUCKET_DATA_CENTER_CONFIG_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --bitbucket-data-center-config-host-uri=BITBUCKET_DATA_CENTER_CONFIG_HOST_URI --bitbucket-data-center-config-read-authorizer-credential-user-token-secret-version=BITBUCKET_DATA_CENTER_CONFIG_READ_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --bitbucket-data-center-config-service-directory=BITBUCKET_DATA_CENTER_CONFIG_SERVICE_DIRECTORY --bitbucket-data-center-config-ssl-ca-certificate=BITBUCKET_DATA_CENTER_CONFIG_SSL_CA_CERTIFICATE --clear-bitbucket-data-center-config | --clear-github-config --github-config-app-installation-id=GITHUB_CONFIG_APP_INSTALLATION_ID --github-config-authorizer-credential-oauth-token-secret-version=GITHUB_CONFIG_AUTHORIZER_CREDENTIAL_OAUTH_TOKEN_SECRET_VERSION | --clear-github-enterprise-config --github-enterprise-config-app-id=GITHUB_ENTERPRISE_CONFIG_APP_ID --github-enterprise-config-app-installation-id=GITHUB_ENTERPRISE_CONFIG_APP_INSTALLATION_ID --github-enterprise-config-host-uri=GITHUB_ENTERPRISE_CONFIG_HOST_URI --github-enterprise-config-service-directory=GITHUB_ENTERPRISE_CONFIG_SERVICE_DIRECTORY --github-enterprise-config-ssl-ca-certificate=GITHUB_ENTERPRISE_CONFIG_SSL_CA_CERTIFICATE --clear-github-enterprise-config-private-key-secret-version | --github-enterprise-config-private-key-secret-version=GITHUB_ENTERPRISE_CONFIG_PRIVATE_KEY_SECRET_VERSION --clear-github-enterprise-config-webhook-secret-version | --github-enterprise-config-webhook-secret-version=GITHUB_ENTERPRISE_CONFIG_WEBHOOK_SECRET_VERSION | --clear-gitlab-config --gitlab-config-authorizer-credential-user-token-secret-version=GITLAB_CONFIG_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --gitlab-config-read-authorizer-credential-user-token-secret-version=GITLAB_CONFIG_READ_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION | --clear-gitlab-enterprise-config --gitlab-enterprise-config-authorizer-credential-user-token-secret-version=GITLAB_ENTERPRISE_CONFIG_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --gitlab-enterprise-config-host-uri=GITLAB_ENTERPRISE_CONFIG_HOST_URI --gitlab-enterprise-config-read-authorizer-credential-user-token-secret-version=GITLAB_ENTERPRISE_CONFIG_READ_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --gitlab-enterprise-config-service-directory=GITLAB_ENTERPRISE_CONFIG_SERVICE_DIRECTORY --gitlab-enterprise-config-ssl-ca-certificate=GITLAB_ENTERPRISE_CONFIG_SSL_CA_CERTIFICATE] + [--bitbucket-cloud-config-authorizer-credential-user-token-secret-version=BITBUCKET_CLOUD_CONFIG_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --bitbucket-cloud-config-read-authorizer-credential-user-token-secret-version=BITBUCKET_CLOUD_CONFIG_READ_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --bitbucket-cloud-config-workspace=BITBUCKET_CLOUD_CONFIG_WORKSPACE --clear-bitbucket-cloud-config | --bitbucket-data-center-config-authorizer-credential-user-token-secret-version=BITBUCKET_DATA_CENTER_CONFIG_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --bitbucket-data-center-config-host-uri=BITBUCKET_DATA_CENTER_CONFIG_HOST_URI --bitbucket-data-center-config-read-authorizer-credential-user-token-secret-version=BITBUCKET_DATA_CENTER_CONFIG_READ_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --bitbucket-data-center-config-service-directory=BITBUCKET_DATA_CENTER_CONFIG_SERVICE_DIRECTORY --bitbucket-data-center-config-ssl-ca-certificate=BITBUCKET_DATA_CENTER_CONFIG_SSL_CA_CERTIFICATE --clear-bitbucket-data-center-config | --clear-github-config --github-config-app-installation-id=GITHUB_CONFIG_APP_INSTALLATION_ID --github-config-authorizer-credential-oauth-token-secret-version=GITHUB_CONFIG_AUTHORIZER_CREDENTIAL_OAUTH_TOKEN_SECRET_VERSION | --clear-github-enterprise-config --github-enterprise-config-app-id=GITHUB_ENTERPRISE_CONFIG_APP_ID --github-enterprise-config-app-installation-id=GITHUB_ENTERPRISE_CONFIG_APP_INSTALLATION_ID --github-enterprise-config-host-uri=GITHUB_ENTERPRISE_CONFIG_HOST_URI --github-enterprise-config-service-directory=GITHUB_ENTERPRISE_CONFIG_SERVICE_DIRECTORY --github-enterprise-config-ssl-ca-certificate=GITHUB_ENTERPRISE_CONFIG_SSL_CA_CERTIFICATE --clear-github-enterprise-config-private-key-secret-version | --github-enterprise-config-private-key-secret-version=GITHUB_ENTERPRISE_CONFIG_PRIVATE_KEY_SECRET_VERSION --clear-github-enterprise-config-webhook-secret-version | --github-enterprise-config-webhook-secret-version=GITHUB_ENTERPRISE_CONFIG_WEBHOOK_SECRET_VERSION | --clear-gitlab-config --gitlab-config-authorizer-credential-user-token-secret-version=GITLAB_CONFIG_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --gitlab-config-read-authorizer-credential-user-token-secret-version=GITLAB_CONFIG_READ_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION | --clear-gitlab-enterprise-config --gitlab-enterprise-config-authorizer-credential-user-token-secret-version=GITLAB_ENTERPRISE_CONFIG_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --gitlab-enterprise-config-host-uri=GITLAB_ENTERPRISE_CONFIG_HOST_URI --gitlab-enterprise-config-read-authorizer-credential-user-token-secret-version=GITLAB_ENTERPRISE_CONFIG_READ_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --gitlab-enterprise-config-service-directory=GITLAB_ENTERPRISE_CONFIG_SERVICE_DIRECTORY --gitlab-enterprise-config-ssl-ca-certificate=GITLAB_ENTERPRISE_CONFIG_SSL_CA_CERTIFICATE | --clear-http-config --http-config-service-directory=HTTP_CONFIG_SERVICE_DIRECTORY --http-config-ssl-ca-certificate=HTTP_CONFIG_SSL_CA_CERTIFICATE --clear-http-config-bearer-token-authentication-secret-version | --http-config-bearer-token-authentication-secret-version=HTTP_CONFIG_BEARER_TOKEN_AUTHENTICATION_SECRET_VERSION | --http-config-basic-authentication-username=HTTP_CONFIG_BASIC_AUTHENTICATION_USERNAME --clear-http-config-basic-authentication-password-secret-version | --http-config-basic-authentication-password-secret-version=HTTP_CONFIG_BASIC_AUTHENTICATION_PASSWORD_SECRET_VERSION] [--clear-crypto-key-config [--crypto-key-config-reference=CRYPTO_KEY_CONFIG_REFERENCE : --key-ring=KEY_RING]] @@ -868,6 +868,160 @@ FLAGS SSL Certificate Authority certificate to use for requests to GitLab Enterprise instance. + Configuration for connections to an HTTP service provider. + + --clear-http-config + Set connection.httpConfig back to default value. + + ServiceDirectoryConfig represents Service Directory configuration for + a connection. + + Service resource - The Service Directory service name. Format: + projects/{project}/locations/{location}/namespaces/{namespace}/services/{service}. + 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 --http-config-service-directory on the + command line with a fully specified name; + ◇ provide the argument --project on the command line; + ◇ set the property core/project. + + To set the location attribute: + ◇ provide the argument --http-config-service-directory on the + command line with a fully specified name; + ◇ provide the argument --location on the command line. + + To set the namespace attribute: + ◇ provide the argument --http-config-service-directory on the + command line with a fully specified name; + ◇ provide the argument --namespace on the command line. + + --http-config-service-directory=HTTP_CONFIG_SERVICE_DIRECTORY + ID of the service or fully qualified identifier for the + service. + + To set the service attribute: + ▹ provide the argument --http-config-service-directory on the + command line. + + --http-config-ssl-ca-certificate=HTTP_CONFIG_SSL_CA_CERTIFICATE + The SSL certificate to use for requests to the HTTP service + provider. + + Arguments for the authentication. + + At most one of these can be specified: + + Bearer token authentication with a token. + + Arguments for the token. + + Update http_config_bearer_token_authentication_secret_version. + + At most one of these can be specified: + + --clear-http-config-bearer-token-authentication-secret-version + Clear + http_config_bearer_token_authentication_secret_version + value and set to null. + + SecretVersion resource - Set + http_config_bearer_token_authentication_secret_version to new + value. + + The token SecretManager secret version to authenticate as. + 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 + --http-config-bearer-token-authentication-secret-version on + the command line with a fully specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + To set the location attribute: + ◆ provide the argument + --http-config-bearer-token-authentication-secret-version on + the command line with a fully specified name; + ◆ provide the argument --location on the command line. + + To set the secret attribute: + ◆ provide the argument + --http-config-bearer-token-authentication-secret-version on + the command line with a fully specified name; + ◆ provide the argument --secret on the command line. This + resource can be one of the following types: + [developerconnect.projects.locations.secrets.versions, + developerconnect.projects.secrets.versions]. + + --http-config-bearer-token-authentication-secret-version=HTTP_CONFIG_BEARER_TOKEN_AUTHENTICATION_SECRET_VERSION + ID of the secretVersion or fully qualified identifier for + the secretVersion. + + To set the secret_version attribute: + ▸ provide the argument + --http-config-bearer-token-authentication-secret-version + on the command line. + + Basic authentication with username and password. + + --http-config-basic-authentication-username=HTTP_CONFIG_BASIC_AUTHENTICATION_USERNAME + The username to authenticate as. + + Arguments for the password. + + Update http_config_basic_authentication_password_secret_version. + + At most one of these can be specified: + + --clear-http-config-basic-authentication-password-secret-version + Clear + http_config_basic_authentication_password_secret_version + value and set to null. + + SecretVersion resource - Set + http_config_basic_authentication_password_secret_version to + new value. + + The password SecretManager secret version to authenticate as. + 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 + --http-config-basic-authentication-password-secret-version + on the command line with a fully specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + To set the location attribute: + ◆ provide the argument + --http-config-basic-authentication-password-secret-version + on the command line with a fully specified name; + ◆ provide the argument --location on the command line. + + To set the secret attribute: + ◆ provide the argument + --http-config-basic-authentication-password-secret-version + on the command line with a fully specified name; + ◆ provide the argument --secret on the command line. This + resource can be one of the following types: + [developerconnect.projects.locations.secrets.versions, + developerconnect.projects.secrets.versions]. + + --http-config-basic-authentication-password-secret-version=HTTP_CONFIG_BASIC_AUTHENTICATION_PASSWORD_SECRET_VERSION + ID of the secretVersion or fully qualified identifier for + the secretVersion. + + To set the secret_version attribute: + ▸ provide the argument + --http-config-basic-authentication-password-secret-version + on the command line. + The crypto key configuration. This field is used by the Customer-managed encryption keys (CMEK) feature. diff --git a/gcloud/alpha/firestore/databases/create b/gcloud/alpha/firestore/databases/create index 430a44171..d5e752c5c 100644 --- a/gcloud/alpha/firestore/databases/create +++ b/gcloud/alpha/firestore/databases/create @@ -5,16 +5,34 @@ NAME SYNOPSIS gcloud alpha firestore databases create --location=LOCATION [--database=DATABASE; default="(default)"] [--delete-protection] - [--edition=EDITION; default="standard"] [--enable-pitr] - [--kms-key-name=KMS_KEY_NAME] [--tags=[KEY=VALUE,...]] - [--type=TYPE; default="firestore-native"] [GCLOUD_WIDE_FLAG ...] + [--edition=EDITION; default="standard"] + [--enable-firestore-data-access] + [--enable-mongodb-compatible-data-access] [--enable-pitr] + [--enable-realtime-updates] [--kms-key-name=KMS_KEY_NAME] + [--tags=[KEY=VALUE,...]] [--type=TYPE; default="firestore-native"] + [GCLOUD_WIDE_FLAG ...] EXAMPLES To create a Firestore Enterprise database named foo in nam5 for use with - MongoDB Compatibility. + MongoDB Compatible API with Data Access Mode enabled. $ gcloud alpha firestore databases create --database=foo \ - --edition=enterprise --location=nam5 + --edition=enterprise --location=nam5 \ + --enable-mongodb-compatible-data-access + + To create a Firestore Enterprise database named foo in nam5 for use with + Firestore API Data Access Mode enabled and Realtime Updates disabled. + + $ gcloud alpha firestore databases create --database=foo \ + --edition=enterprise --location=nam5 \ + --enable-firestore-data-access + + To create a Firestore Enterprise database named foo in nam5 for use with + Firestore API Data Access Mode enabled and Realtime Updates enabled. + + $ gcloud alpha firestore databases create --database=foo \ + --edition=enterprise --location=nam5 \ + --enable-firestore-data-access --enable-realtime-updates To create a Firestore Native database in nam5. @@ -88,6 +106,23 @@ OPTIONAL FLAGS The edition of the database. EDITION must be one of: standard, enterprise. + --enable-firestore-data-access + Whether to enable Firestore API Data Access on the created database. + + If set to true, Firestore API Data Access on the new database will be + enabled. By default, this feature is disabled for Enterprise edition + databases. To explicitly disable, use + --no-enable-firestore-data-access. + + --enable-mongodb-compatible-data-access + Whether to enable MongoDB Compatible API Data Access on the created + database. + + If set to true, MongoDB Compatible API Data Access on the new database + will be enabled. By default, this feature is enabled for Enterprise + edition databases. To disable, use + --no-enable-mongodb-compatible-data-access. + --enable-pitr Whether to enable Point In Time Recovery (PITR) on the created database. @@ -95,6 +130,13 @@ OPTIONAL FLAGS If set to true, PITR on the new database will be enabled. By default, this feature is not enabled. + --enable-realtime-updates + Whether to enable Realtime Updates feature on the created database. + + If set to true, Realtime Updates feature on the new database will be + enabled. By default, this feature is disabled for Enterprise edition + databases. To explicitly disable, use --no-enable-realtime-updates. + --kms-key-name=KMS_KEY_NAME The resource ID of a Cloud KMS key. If set, the database created will be a Customer-Managed Encryption Key (CMEK) database encrypted with diff --git a/gcloud/alpha/functions/deploy b/gcloud/alpha/functions/deploy index 8bbbeb322..56babf108 100644 --- a/gcloud/alpha/functions/deploy +++ b/gcloud/alpha/functions/deploy @@ -4,9 +4,9 @@ NAME SYNOPSIS gcloud alpha functions deploy (NAME : --region=REGION) [--[no-]allow-unauthenticated] [--buildpack-stack=BUILDPACK_STACK] - [--concurrency=CONCURRENCY] [--docker-registry=DOCKER_REGISTRY] - [--egress-settings=EGRESS_SETTINGS] [--entry-point=ENTRY_POINT] - [--gen2] [--ignore-file=IGNORE_FILE] + [--concurrency=CONCURRENCY] [--direct-vpc-egress=DIRECT_VPC_EGRESS] + [--docker-registry=DOCKER_REGISTRY] [--egress-settings=EGRESS_SETTINGS] + [--entry-point=ENTRY_POINT] [--gen2] [--ignore-file=IGNORE_FILE] [--ingress-settings=INGRESS_SETTINGS] [--retry] [--run-service-account=RUN_SERVICE_ACCOUNT] [--runtime=RUNTIME] [--runtime-update-policy=RUNTIME_UPDATE_POLICY] @@ -34,6 +34,9 @@ SYNOPSIS [--clear-labels | --remove-labels=[KEY,...]] [--clear-max-instances | --max-instances=MAX_INSTANCES] [--clear-min-instances | --min-instances=MIN_INSTANCES] + [--clear-network + | --network=NETWORK --subnet=SUBNET --clear-network-tags + | --network-tags=[TAGS,...]] [--clear-secrets | --set-secrets=[SECRET_ENV_VAR=SECRET_VALUE_REF, /secret_path=SECRET_VALUE_REF, @@ -115,6 +118,11 @@ FLAGS instance. Leave concurrency unspecified to receive the server default value. + --direct-vpc-egress=DIRECT_VPC_EGRESS + Specify which of the outbound traffic to send through Direct VPC + egress. Configuring Direct VPC network is required to use this flag. + DIRECT_VPC_EGRESS must be one of: private-ranges-only, all. + --docker-registry=DOCKER_REGISTRY (DEPRECATED) Docker Registry to use for storing the function's Docker images. The option artifact-registry is used by default. @@ -485,6 +493,37 @@ FLAGS Sets the minimum number of instances for the function. This is helpful for reducing cold start times. Defaults to zero. + At most one of these can be specified: + + --clear-network + Disconnect this Cloud Function from the Direct VPC network it is + connected to. + + Direct VPC egress setting flags group. + + --network=NETWORK + The VPC network that the Cloud Function will be able to send + traffic to. If --subnet is also specified, subnet must be a + subnetwork of the network specified by this --network flag. To + clear existing VPC network settings, use --clear-network. + + --subnet=SUBNET + The VPC subnetwork that the Cloud Function will get IPs from. The + subnetwork must be /26 or larger. If --network is also specified, + subnet must be a subnetwork of the network specified by the + --network flag. If --network is not specified, network will be + looked up from this subnetwork. To clear existing VPC network + settings, use --clear-network. + + At most one of these can be specified: + + --clear-network-tags + Clears all existing network tags from the Cloud Function. + + --network-tags=[TAGS,...] + Applies the given network tags (comma separated) to the Cloud + Function. To clear existing tags, use --clear-network-tags. + At most one of these can be specified: --clear-secrets diff --git a/gcloud/alpha/functions/upgrade b/gcloud/alpha/functions/upgrade index c69984757..c93b16518 100644 --- a/gcloud/alpha/functions/upgrade +++ b/gcloud/alpha/functions/upgrade @@ -5,7 +5,8 @@ NAME SYNOPSIS gcloud alpha functions upgrade (NAME : --region=REGION) [--abort | --commit | --redirect-traffic | --rollback-traffic - | --setup-config --trigger-service-account=TRIGGER_SERVICE_ACCOUNT] + | --max-instances=MAX_INSTANCES --runtime=RUNTIME + --setup-config --trigger-service-account=TRIGGER_SERVICE_ACCOUNT] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -68,12 +69,12 @@ POSITIONAL ARGUMENTS ▸ set the property functions/region. FLAGS - Upgrade a 1st gen Cloud Function to the 2nd gen environment. You must - specify one of the following flags: + Upgrade a 1st gen Cloud Function to a Cloud Run Function. You must specify + one of the following flags: ◆ --setup-config and optionally --trigger-service-account, ◆ --redirect-traffic, ◆ --rollback-traffic, - ◆ --commit, + ◆ --commit and optionally --skip-detach, ◆ --abort. At most one of these can be specified: @@ -94,6 +95,18 @@ FLAGS Rolls back production traffic to the original 1st gen copy of the function. The 2nd gen copy will still be available for testing. + --max-instances=MAX_INSTANCES + Sets the maximum number of instances for the function. A function + execution that would exceed max-instances times out. + + --runtime=RUNTIME + Runtime in which to run the function. + + Required when deploying a new function; optional when updating an + existing function. + + For a list of available runtimes, run gcloud functions runtimes list. + --setup-config Sets up the function upgrade config by creating a 2nd gen copy of the function's code and configuration. diff --git a/gcloud/alpha/network-services/help b/gcloud/alpha/network-services/help index de26bebf2..a5cb7ef0f 100644 --- a/gcloud/alpha/network-services/help +++ b/gcloud/alpha/network-services/help @@ -49,7 +49,7 @@ GROUPS (ALPHA) Manage Network Services MulticastGroupConsumerActivations. multicast-group-definitions - (ALPHA) Manage Network Services MulticastGroupDefinitions. + (ALPHA) (DEPRECATED) Manage Network Services MulticastGroupDefinitions. multicast-group-producer-activations (ALPHA) Manage Network Services MulticastGroupProducerActivations. @@ -61,7 +61,7 @@ GROUPS (ALPHA) Manage Network Services MulticastGroupRanges. multicast-groups - (ALPHA) Manage Network Services MulticastGroups. + (ALPHA) (DEPRECATED) Manage Network Services MulticastGroups. multicast-producer-associations (ALPHA) Manage Network Services MulticastProducerAssociations. diff --git a/gcloud/alpha/network-services/multicast-group-definitions/create b/gcloud/alpha/network-services/multicast-group-definitions/create deleted file mode 100644 index fd2757499..000000000 --- a/gcloud/alpha/network-services/multicast-group-definitions/create +++ /dev/null @@ -1,114 +0,0 @@ -NAME - gcloud alpha network-services multicast-group-definitions create - create a - multicast group definition - -SYNOPSIS - gcloud alpha network-services multicast-group-definitions create - (MULTICAST_GROUP_DEFINITION : --location=LOCATION) - --multicast-domain=MULTICAST_DOMAIN - --reserved-internal-range=RESERVED_INTERNAL_RANGE [--async] - [--consumer-accept-list=[CONSUMER_ACCEPT_LIST,...]] - [--description=DESCRIPTION] [--[no-]enable-logging] - [--labels=[KEY=VALUE,...]] [--require-explicit-accept] - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) Create a multicast group definition in the specified location of - the current project. - -EXAMPLES - Create a multicast group definition with the name - 'my-multicast-group-definition', reserved-internal-range 'path-to-ir', - multicast-domain 'path-to-md', and location 'global'. - - $ gcloud alpha network-services multicast-group-definitions create \ - my-multicast-group-definition \ - --reserved-internal-range=path-to-ir \ - --multicast-domain=path-to-md --location=global - -POSITIONAL ARGUMENTS - Multicast group definition resource - Name of the multicast group - definition to be created. The arguments in this group can be used to - specify the attributes of this resource. (NOTE) Some attributes are not - given arguments in this group but can be set in other ways. - - To set the project attribute: - ◆ provide the argument multicast_group_definition 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. - - MULTICAST_GROUP_DEFINITION - ID of the multicast group definition or fully qualified identifier - for the multicast group definition. - - To set the multicast_group_definition attribute: - ▸ provide the argument multicast_group_definition 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 multicast_group_definition on the command - line with a fully specified name; - ▸ provide the argument --location on the command line. - -REQUIRED FLAGS - --multicast-domain=MULTICAST_DOMAIN - The multicast domain to be used. - - --reserved-internal-range=RESERVED_INTERNAL_RANGE - The reserved internal range to be used. - -OPTIONAL FLAGS - --async - Return immediately, without waiting for the operation in progress to - complete. - - --consumer-accept-list=[CONSUMER_ACCEPT_LIST,...] - An optional list of consumer projects that can use this multicast group - definition. - - --description=DESCRIPTION - The description for the multicast group definition. - - --[no-]enable-logging - Whether to enable logging for this multicast group definition. Use - --enable-logging to enable and --no-enable-logging to disable. - - --labels=[KEY=VALUE,...] - List of label KEY=VALUE pairs to add. - - Keys must start with a lowercase character and contain only hyphens - (-), underscores (_), lowercase characters, and numbers. Values must - contain only hyphens (-), underscores (_), lowercase characters, and - numbers. - - --require-explicit-accept - Whether an empty consumer accept list will reject all consumer - projects. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -API REFERENCE - This command uses the networkservices/v1alpha1 API. The full documentation - for this API can be found at: https://cloud.google.com/networking - -NOTES - This command is currently in alpha and might change without notice. If this - command fails with API permission errors despite specifying the correct - project, you might be trying to access an API with an invitation-only early - access allowlist. - diff --git a/gcloud/alpha/network-services/multicast-group-definitions/delete b/gcloud/alpha/network-services/multicast-group-definitions/delete index 8b22b9931..1f6bbbf1b 100644 --- a/gcloud/alpha/network-services/multicast-group-definitions/delete +++ b/gcloud/alpha/network-services/multicast-group-definitions/delete @@ -8,8 +8,11 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Delete a multicast group definition in the specified location of - the current project. + (ALPHA) (DEPRECATED) Multicast Group Definition is deprecated. Please use + the Multicast Group Range resource instead. + + Delete a multicast group definition in the specified location of the + current project. EXAMPLES To delete a multicast group definition in the current project, run: diff --git a/gcloud/alpha/network-services/multicast-group-definitions/describe b/gcloud/alpha/network-services/multicast-group-definitions/describe index 7a8f7a158..f3555003b 100644 --- a/gcloud/alpha/network-services/multicast-group-definitions/describe +++ b/gcloud/alpha/network-services/multicast-group-definitions/describe @@ -8,8 +8,11 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Show details of a multicast group definition in the specified - location of the current project. + (ALPHA) (DEPRECATED) Multicast Group Definition is deprecated. Please use + the Multicast Group Range resource instead. + + Show details of a multicast group definition in the specified location of + the current project. EXAMPLES To describe a multicast group definition in the current project, run: diff --git a/gcloud/alpha/network-services/multicast-group-definitions/help b/gcloud/alpha/network-services/multicast-group-definitions/help index ebf8c4f1f..8eb5e4c6b 100644 --- a/gcloud/alpha/network-services/multicast-group-definitions/help +++ b/gcloud/alpha/network-services/multicast-group-definitions/help @@ -7,7 +7,10 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Manage Network Services MulticastGroupDefinitions. + (ALPHA) (DEPRECATED) Manage Network Services MulticastGroupDefinitions. + + Multicast Group Definition is deprecated. Please use the Multicast Group + Range resource instead. GCLOUD WIDE FLAGS These flags are available to all commands: --help. @@ -17,17 +20,14 @@ GCLOUD WIDE FLAGS COMMANDS COMMAND is one of the following: - create - (ALPHA) Create a multicast group definition. - delete - (ALPHA) Delete a multicast group definition. + (ALPHA) (DEPRECATED) Delete a multicast group definition. describe - (ALPHA) Describe a multicast group definition. + (ALPHA) (DEPRECATED) Describe a multicast group definition. list - (ALPHA) List multicast group definitions. + (ALPHA) (DEPRECATED) List multicast group definitions. NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/network-services/multicast-group-definitions/list b/gcloud/alpha/network-services/multicast-group-definitions/list index df801ab3f..0720d9e45 100644 --- a/gcloud/alpha/network-services/multicast-group-definitions/list +++ b/gcloud/alpha/network-services/multicast-group-definitions/list @@ -9,8 +9,11 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) List all multicast group definitions in the specified location of - the current project. + (ALPHA) (DEPRECATED) Multicast Group Definition is deprecated. Please use + the Multicast Group Range resource instead. + + List all multicast group definitions in the specified location of the + current project. EXAMPLES To list multicast group definitions in the current project, run: diff --git a/gcloud/alpha/network-services/multicast-groups/create b/gcloud/alpha/network-services/multicast-groups/create deleted file mode 100644 index 7468cc343..000000000 --- a/gcloud/alpha/network-services/multicast-groups/create +++ /dev/null @@ -1,102 +0,0 @@ -NAME - gcloud alpha network-services multicast-groups create - create a multicast - group - -SYNOPSIS - gcloud alpha network-services multicast-groups create - (MULTICAST_GROUP : --location=LOCATION) - --multicast-domain-activation=MULTICAST_DOMAIN_ACTIVATION - --multicast-group-definition=MULTICAST_GROUP_DEFINITION [--async] - [--description=DESCRIPTION] [--[no-]enable-logging] - [--labels=[KEY=VALUE,...]] [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) Create a multicast group in the specified location of the current - project. - -EXAMPLES - Create a multicast group with the name 'my-multicast-group', - multicast-group-definition 'path-to-mgd', multicast-domain-activation - 'path-to-mda', and location 'zone'. - - $ gcloud alpha network-services multicast-groups create \ - my-multicast-group --multicast-group-definition=path-to-mgd \ - --multicast-domain-activation=path-to-mda --location=zone - -POSITIONAL ARGUMENTS - Multicast group resource - Name of the multicast group to be created. The - arguments in this group can be used to specify the attributes of this - resource. (NOTE) Some attributes are not given arguments in this group but - can be set in other ways. - - To set the project attribute: - ◆ provide the argument multicast_group 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. - - MULTICAST_GROUP - ID of the multicast group or fully qualified identifier for the - multicast group. - - To set the multicast_group attribute: - ▸ provide the argument multicast_group 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 multicast_group on the command line with a - fully specified name; - ▸ provide the argument --location on the command line. - -REQUIRED FLAGS - --multicast-domain-activation=MULTICAST_DOMAIN_ACTIVATION - The multicast domain activation to be used. - - --multicast-group-definition=MULTICAST_GROUP_DEFINITION - The multicast group definition to be used. - -OPTIONAL FLAGS - --async - Return immediately, without waiting for the operation in progress to - complete. - - --description=DESCRIPTION - The description for the multicast group. - - --[no-]enable-logging - Whether to enable logging for this multicast group. Use - --enable-logging to enable and --no-enable-logging to disable. - - --labels=[KEY=VALUE,...] - List of label KEY=VALUE pairs to add. - - Keys must start with a lowercase character and contain only hyphens - (-), underscores (_), lowercase characters, and numbers. Values must - contain only hyphens (-), underscores (_), lowercase characters, and - numbers. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -API REFERENCE - This command uses the networkservices/v1alpha1 API. The full documentation - for this API can be found at: https://cloud.google.com/networking - -NOTES - This command is currently in alpha and might change without notice. If this - command fails with API permission errors despite specifying the correct - project, you might be trying to access an API with an invitation-only early - access allowlist. - diff --git a/gcloud/alpha/network-services/multicast-groups/delete b/gcloud/alpha/network-services/multicast-groups/delete index bc9d06dee..ee304675e 100644 --- a/gcloud/alpha/network-services/multicast-groups/delete +++ b/gcloud/alpha/network-services/multicast-groups/delete @@ -8,8 +8,10 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Delete a multicast group in the specified location of the current - project. + (ALPHA) (DEPRECATED) Multicast Group is deprecated. Please use the + Multicast Group Range Activation resource instead. + + Delete a multicast group in the specified location of the current project. EXAMPLES To delete a multicast group in the current project, run: diff --git a/gcloud/alpha/network-services/multicast-groups/describe b/gcloud/alpha/network-services/multicast-groups/describe index e78baa177..61865c36d 100644 --- a/gcloud/alpha/network-services/multicast-groups/describe +++ b/gcloud/alpha/network-services/multicast-groups/describe @@ -7,8 +7,11 @@ SYNOPSIS (MULTICAST_GROUP : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Show details of a multicast group in the specified location of the - current project. + (ALPHA) (DEPRECATED) Multicast Group is deprecated. Please use the + Multicast Group Range Activation resource instead. + + Show details of a multicast group in the specified location of the current + project. EXAMPLES To describe details of a multicast group in the current project and diff --git a/gcloud/alpha/network-services/multicast-groups/help b/gcloud/alpha/network-services/multicast-groups/help index 7995c369b..dffe5e671 100644 --- a/gcloud/alpha/network-services/multicast-groups/help +++ b/gcloud/alpha/network-services/multicast-groups/help @@ -7,7 +7,10 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Manage Network Services MulticastGroups. + (ALPHA) (DEPRECATED) Manage Network Services MulticastGroups. + + Multicast Group is deprecated. Please use the Multicast Group Range + Activation resource instead. GCLOUD WIDE FLAGS These flags are available to all commands: --help. @@ -17,17 +20,14 @@ GCLOUD WIDE FLAGS COMMANDS COMMAND is one of the following: - create - (ALPHA) Create a multicast group. - delete - (ALPHA) Delete a multicast group. + (ALPHA) (DEPRECATED) Delete a multicast group. describe - (ALPHA) Describe a multicast groups. + (ALPHA) (DEPRECATED) Describe a multicast groups. list - (ALPHA) List multicast groups. + (ALPHA) (DEPRECATED) List multicast groups. NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/network-services/multicast-groups/list b/gcloud/alpha/network-services/multicast-groups/list index 31d3c9930..4335063e2 100644 --- a/gcloud/alpha/network-services/multicast-groups/list +++ b/gcloud/alpha/network-services/multicast-groups/list @@ -7,8 +7,10 @@ SYNOPSIS [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) List all multicast groups in the specified location of the current - project. + (ALPHA) (DEPRECATED) Multicast Group is deprecated. Please use the + Multicast Group Range Activation resource instead. + + List all multicast groups in the specified location of the current project. EXAMPLES To list multicast groups in the current project and location, run: diff --git a/gcloud/alpha/redis/clusters/create b/gcloud/alpha/redis/clusters/create index 3f2a55b92..6947abea4 100644 --- a/gcloud/alpha/redis/clusters/create +++ b/gcloud/alpha/redis/clusters/create @@ -9,7 +9,7 @@ SYNOPSIS [--automated-backup-start-time=AUTOMATED_BACKUP_START_TIME] [--automated-backup-ttl=AUTOMATED_BACKUP_TTL] [--cross-cluster-replication-role=CROSS_CLUSTER_REPLICATION_ROLE] - [--deletion-protection] [--kms-key=KMS_KEY] + [--deletion-protection] [--kms-key=KMS_KEY] [--labels=[KEY=VALUE,...]] [--maintenance-window-day=MAINTENANCE_WINDOW_DAY] [--maintenance-window-hour=MAINTENANCE_WINDOW_HOUR] [--network=NETWORK] [--node-type=NODE_TYPE] [--persistence-mode=PERSISTENCE_MODE] @@ -151,6 +151,14 @@ FLAGS The key must be in the same region as the cluster. Otherwise, the create operation fails. + --labels=[KEY=VALUE,...] + List of label KEY=VALUE pairs to add. + + Keys must start with a lowercase character and contain only hyphens + (-), underscores (_), lowercase characters, and numbers. Values must + contain only hyphens (-), underscores (_), lowercase characters, and + numbers. + --maintenance-window-day=MAINTENANCE_WINDOW_DAY Day of week when the window starts, e.g. sunday. MAINTENANCE_WINDOW_DAY must be one of: friday, monday, saturday, sunday, thursday, tuesday, diff --git a/gcloud/alpha/redis/clusters/update b/gcloud/alpha/redis/clusters/update index 9bbf5e7ab..ad3c5f64c 100644 --- a/gcloud/alpha/redis/clusters/update +++ b/gcloud/alpha/redis/clusters/update @@ -14,7 +14,8 @@ SYNOPSIS [--rdb-snapshot-start-time=RDB_SNAPSHOT_START_TIME] [--remove-redis-config=[KEY,...]] [--replica-count=REPLICA_COUNT] [--shard-count=SHARD_COUNT] [--simulate-maintenance-event] - [--update-redis-config=KEY=VALUE] + [--update-labels=[KEY=VALUE,...]] [--update-redis-config=KEY=VALUE] + [--clear-labels | --remove-labels=[KEY,...]] [--maintenance-window-any | --maintenance-window-day=MAINTENANCE_WINDOW_DAY --maintenance-window-hour=MAINTENANCE_WINDOW_HOUR] @@ -157,11 +158,40 @@ FLAGS --simulate-maintenance-event Trigger a simulation for maintenance event. + --update-labels=[KEY=VALUE,...] + List of label KEY=VALUE pairs to update. If a label exists, its value + is modified. Otherwise, a new label is created. + + Keys must start with a lowercase character and contain only hyphens + (-), underscores (_), lowercase characters, and numbers. Values must + contain only hyphens (-), underscores (_), lowercase characters, and + numbers. + --update-redis-config=KEY=VALUE A list of Redis Cluster config KEY=VALUE pairs to update. If a config parameter is already set, its value is modified; otherwise a new Redis config parameter is added. + At most one of these can be specified: + + --clear-labels + Remove all labels. If --update-labels is also specified then + --clear-labels is applied first. + + For example, to remove all labels: + + $ gcloud alpha redis clusters update --clear-labels + + To remove all existing labels and create two new labels, foo and baz: + + $ gcloud alpha redis clusters update --clear-labels \ + --update-labels foo=bar,baz=qux + + --remove-labels=[KEY,...] + List of label keys to remove. If a label does not exist it is + silently ignored. If --update-labels is also specified then + --update-labels is applied first. + At most one of these can be specified: --maintenance-window-any diff --git a/gcloud/alpha/run/deploy b/gcloud/alpha/run/deploy index 4fce2632d..dd4913380 100644 --- a/gcloud/alpha/run/deploy +++ b/gcloud/alpha/run/deploy @@ -269,7 +269,7 @@ FLAGS and resume server-assigned naming. --scaling=SCALING - The scaling mode to use for this resource. Flag value could be either + The scaling mode to use for this service. Flag value could be either "auto" for automatic scaling, or a positive integer to configure manual scaling with the given integer as a fixed instance count. @@ -661,7 +661,8 @@ FLAGS KEY_1: "value1" KEY_2: "value 2" - Example ENV content: + + Example ENV content: KEY_1="value1" KEY_2="value 2" diff --git a/gcloud/alpha/run/instances/create b/gcloud/alpha/run/instances/create new file mode 100644 index 000000000..3eb79224c --- /dev/null +++ b/gcloud/alpha/run/instances/create @@ -0,0 +1,393 @@ +NAME + gcloud alpha run instances create - create a Cloud Run instance + +SYNOPSIS + gcloud alpha run instances create [INSTANCE] [--async] + [--binary-authorization=POLICY] [--breakglass=JUSTIFICATION] + [--container=CONTAINER] [--gpu-type=GPU_TYPE] + [--[no-]gpu-zonal-redundancy] [--key=KEY] [--labels=[KEY=VALUE,...]] + [--region=REGION] [--service-account=SERVICE_ACCOUNT] + [--set-cloudsql-instances=[CLOUDSQL-INSTANCES,...]] + [--vpc-connector=VPC_CONNECTOR] [--vpc-egress=VPC_EGRESS] + [--add-volume=[KEY=VALUE,...] + --clear-volumes --remove-volume=[VOLUME,...]] + [--add-volume-mount=[volume=NAME,mount-path=MOUNT_PATH,...] + --args=[ARG,...] --clear-volume-mounts --command=[COMMAND,...] + --cpu=CPU --depends-on=[CONTAINER,...] --gpu=GPU --image=IMAGE + --memory=MEMORY --remove-volume-mount=[MOUNT_PATH,...] + --startup-probe=[KEY=VALUE,...] --clear-env-vars + | --env-vars-file=FILE_PATH | --set-env-vars=[KEY=VALUE,...] + | --remove-env-vars=[KEY,...] + --update-env-vars=[KEY=VALUE,...] --clear-secrets + | --set-secrets=[KEY=VALUE,...] + | --remove-secrets=[KEY,...] --update-secrets=[KEY=VALUE,...]] + [--network=NETWORK --network-tags=[TAG,...] --subnet=SUBNET] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Creates a new Cloud Run instance. + +EXAMPLES + To create a new instance my-instance on Cloud Run: + + $ gcloud alpha run instances create my-instance \ + --image=us-docker.pkg.dev/project/image + + You may also omit the instance name. Then a prompt will be displayed with a + suggested default value: + + $ gcloud alpha run instances create \ + --image=us-docker.pkg.dev/project/image + +POSITIONAL ARGUMENTS + Instance resource - Instance to create. This represents a Cloud resource. + (NOTE) Some attributes are not given arguments in this group but can be + set in other ways. + + To set the project attribute: + ◆ provide the argument INSTANCE on the command line with a fully + specified name; + ◆ specify the instance name from an interactive prompt with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + [INSTANCE] + ID of the Instance or fully qualified identifier for the Instance. + + To set the instances attribute: + ▸ provide the argument INSTANCE on the command line; + ▸ specify the instance name from an interactive prompt. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --binary-authorization=POLICY + Binary Authorization policy to check against. This must be set to + "default". + + --breakglass=JUSTIFICATION + Justification to bypass Binary Authorization policy constraints and + allow the operation. See + https://cloud.google.com/binary-authorization/docs/using-breakglass for + more information. Next update or deploy command will automatically + clear existing breakglass justification. + + --container=CONTAINER + Specifies a container by name. Flags following --container will apply + to the specified container. + + Flags that are not container-specific must be specified before + --container. + + --gpu-type=GPU_TYPE + The GPU type to use. + + --[no-]gpu-zonal-redundancy + Set GPU zonal redundancy. Use --gpu-zonal-redundancy to enable and + --no-gpu-zonal-redundancy to disable. + + --key=KEY + CMEK key reference to encrypt the container with. + + --labels=[KEY=VALUE,...] + List of label KEY=VALUE pairs to add. + + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. + + --service-account=SERVICE_ACCOUNT + the email address of an IAM service account associated with the + revision of the service. The service account represents the identity of + the running revision, and determines what permissions the revision has. + + --set-cloudsql-instances=[CLOUDSQL-INSTANCES,...] + You can specify a name of a Cloud SQL instance if it's in the same + project and region as your Cloud Run resource; otherwise specify + :: for the instance. + + --vpc-connector=VPC_CONNECTOR + Set a VPC connector for this resource. + + --vpc-egress=VPC_EGRESS + Specify which of the outbound traffic to send through Direct VPC egress + or the VPC connector for this resource. This resource must have Direct + VPC egress enabled or a VPC connector to set this flag. VPC_EGRESS must + be one of: + + all + (DEPRECATED) Sends all outbound traffic through Direct VPC egress + or the VPC connector. Provides the same functionality as + 'all-traffic'. Prefer to use 'all-traffic' instead. + all-traffic + Sends all outbound traffic through Direct VPC egress or the VPC + connector. + private-ranges-only + Default option. Sends outbound traffic to private IP addresses (RFC + 1918 and Private Google Access IPs) through Direct VPC egress or + the VPC connector. + + Traffic to other Cloud Run services might require additional + configuration. See + https://cloud.google.com/run/docs/securing/private-networking#send_requests_to_other_services_and_services + for more information. + + --add-volume=[KEY=VALUE,...] + Adds a volume to the Cloud Run resource. To add more than one volume, + specify this flag multiple times. Volumes must have a type key. Volumes + must have a name key if mount-path is not specified. A name key is + optional if mount-path is specified.Only certain values are supported + for type. Depending on the provided type, other keys will be required. + The following types are supported with the specified additional keys: + + cloud-storage: A volume representing a Cloud Storage bucket. This + volume type is mounted using Cloud Storage FUSE. See + https://cloud.google.com/storage/docs/gcs-fuse for the details and + limitations of this filesystem. Additional keys: + ◆ readonly: (optional) A boolean. If true, this volume will be + read-only from all mounts. + ◆ mount-options: (optional) A list of flags to pass to GCSFuse. Flags + should be specified without leading dashes and separated by + semicolons. + ◆ bucket: (optional) the name of the bucket to use as the source of + this volume. + ◆ dynamic-mounting: (optional) A boolean. If true, the volume will be + mounted dynamically. Note: You will either need to specify a bucket + or set dynamic-mounting to true, but not both. + ◆ mount-path: (optional) The path at which the volume should be + mounted. The mount-path parameter is only supported for single + container services which do not make use of the --container flag. For + multi-container services, specify the mount-path parameter under the + --add-volume-mount flag. + + cloudsql: Represents a Cloud SQL instance as a volume. Additional keys: + ◆ instances: (required) The name of the Cloud SQL instances to mount. + Must be in the form project_id:region:instance_id and separated by + semicolons. + ◆ mount-path: (optional) The path at which the volume should be + mounted. The mount-path parameter is only supported for single + container services which do not make use of the --container flag. For + multi-container services, specify the mount-path parameter under the + --add-volume-mount flag. + + ephemeral-disk: A volume that stores data on a temporary disk. With + this type of volume, data is not shared between instances and all data + will be lost when the instance it is on is terminated. Additional keys: + ◆ mount-path: (optional) The path at which the volume should be + mounted. The mount-path parameter is only supported for single + container services which do not make use of the --container flag. For + multi-container services, specify the mount-path parameter under the + --add-volume-mount flag. + ◆ size: (optional) A quantity representing the amount of disk space + allocated to this volume, such as "512Mi" or "3G". + + in-memory: An ephemeral volume that stores data in the instance's + memory. With this type of volume, data is not shared between instances + and all data will be lost when the instance it is on is terminated. + Additional keys: + ◆ mount-path: (optional) The path at which the volume should be + mounted. The mount-path parameter is only supported for single + container services which do not make use of the --container flag. For + multi-container services, specify the mount-path parameter under the + --add-volume-mount flag. + ◆ size-limit: (optional) A quantity representing the maximum amount + of memory allocated to this volume, such as "512Mi" or "3G". Data + stored in an in-memory volume consumes the memory allocation of the + container that wrote the data. If size-limit is not specified, the + maximum size will be half the total memory limit of all containers. + + nfs: Represents a volume backed by an NFS server. Additional keys: + ◆ location: (required) The location of the NFS Server, in the form + SERVER:/PATH + ◆ mount-path: (optional) The path at which the volume should be + mounted. The mount-path parameter is only supported for single + container services which do not make use of the --container flag. For + multi-container services, specify the mount-path parameter under the + --add-volume-mount flag. + ◆ readonly: (optional) A boolean. If true, this volume will be + read-only from all mounts. + + secret: Represents a secret stored in Secret Manager as a volume. + Additional keys: + ◆ secret: (required) The name of the secret in Secret Manager. Must + be a secret in the same project being deployed or be an alias mapped + in the run.googleapis.com/secrets annotation. + ◆ version: (required) The version of the secret to make available in + the volume. + ◆ path: (required) The relative path within the volume to mount that + version. + ◆ mount-path: (optional) The path at which the volume should be + mounted. The mount-path parameter is only supported for single + container services which do not make use of the --container flag. For + multi-container services, specify the mount-path parameter under the + --add-volume-mount flag. + + --clear-volumes + Remove all existing volumes from the Cloud Run resource, including + volumes mounted as secrets + + --remove-volume=[VOLUME,...] + Removes volumes from the Cloud Run resource. + + Container Flags + + If the --container is specified the following arguments may only be specified after a --container flag. + + --add-volume-mount=[volume=NAME,mount-path=MOUNT_PATH,...] + Adds a mount to the current container. Must contain the keys + volume=NAME and mount-path=/PATH where NAME is the name of a volume + on this resource and PATH is the path within the container's + filesystem to mount this volume. + + --args=[ARG,...] + Comma-separated arguments passed to the command run by the + container image. If not specified and no '--command' is provided, + the container image's default Cmd is used. Otherwise, if not + specified, no arguments are passed. To reset this field to its + default, pass an empty string. + + --clear-volume-mounts + Remove all existing mounts from the current container. + + --command=[COMMAND,...] + Entrypoint for the container image. If not specified, the container + image's default Entrypoint is run. To reset this field to its + default, pass an empty string. + + --cpu=CPU + Set a CPU limit in Kubernetes cpu units. + + Cloud Run supports values fractional values below 1, 1, 2, 4, and + 8. Some CPU values requires a minimum Memory --memory value. + + --depends-on=[CONTAINER,...] + List of container dependencies to add to the current container. + + --gpu=GPU + Cloud Run supports values 0 or 1. 1 gpu also requires a minimum 4 + --cpu value and a minimum 16Gi --memory value. + + --image=IMAGE + Name of the container image to deploy (e.g. + us-docker.pkg.dev/cloudrun/container/hello:latest). + + --memory=MEMORY + Set a memory limit. Ex: 1024Mi, 4Gi. + + --remove-volume-mount=[MOUNT_PATH,...] + Removes the volume mounted at the specified path from the current + container. + + --startup-probe=[KEY=VALUE,...] + Comma separated settings for startup probe in the form KEY=VALUE. + Each key stands for a field of the probe described in + https://cloud.google.com/run/docs/reference/rest/v1/Container#Probe. + Currently supported keys are: initialDelaySeconds, timeoutSeconds, + periodSeconds, failureThreshold, httpGet.port, httpGet.path, + grpc.port, grpc.service, tcpSocket.port. + + For example, to set a probe with 10s timeout and HTTP probe + requests sent to 8080 port of the container: + + $ --startup-probe=timeoutSeconds=10,httpGet.port=8080 + + To remove existing probe: + + $ --startup-probe="" + + At most one of these can be specified: + + --clear-env-vars + Remove all environment variables. + + --env-vars-file=FILE_PATH + Path to a local YAML or ENV file with definitions for all + environment variables. All existing environment variables will be + removed before the new environment variables are added. Example + YAML content: + + KEY_1: "value1" + KEY_2: "value 2" + + Example ENV content: + + KEY_1="value1" + KEY_2="value 2" + + --set-env-vars=[KEY=VALUE,...] + List of key-value pairs to set as environment variables. All + existing environment variables will be removed first. + + Only --update-env-vars and --remove-env-vars can be used together. + If both are specified, --remove-env-vars will be applied first. + + --remove-env-vars=[KEY,...] + List of environment variables to be removed. + + --update-env-vars=[KEY=VALUE,...] + List of key-value pairs to set as environment variables. + + Specify secrets to mount or provide as environment variables. Keys + starting with a forward slash '/' are mount paths. All other keys + correspond to environment variables. Values should be in the form + SECRET_NAME:SECRET_VERSION. For example: + '--update-secrets=/secrets/api/key=mysecret:latest,ENV=othersecret:1' + will mount a volume at '/secrets/api' containing a file 'key' with the + latest version of secret 'mysecret'. An environment variable named ENV + will also be created whose value is version 1 of secret 'othersecret'. + + At most one of these can be specified: + + --clear-secrets + Remove all secrets. + + --set-secrets=[KEY=VALUE,...] + List of key-value pairs to set as secrets. All existing secrets + will be removed first. + + Only --update-secrets and --remove-secrets can be used together. If + both are specified, --remove-secrets will be applied first. + + --remove-secrets=[KEY,...] + List of secrets to be removed. + + --update-secrets=[KEY=VALUE,...] + List of key-value pairs to set as secrets. + + Direct VPC egress setting flags group. + + --network=NETWORK + The VPC network that the Cloud Run job will be able to send traffic + to. If --subnet is also specified, subnet must be a subnetwork of the + network specified by this --network flag. To clear existing VPC + network settings, use --clear-network. + + --network-tags=[TAG,...] + Applies the given network tags (comma separated) to the Cloud Run + job. To clear existing tags, use --clear-network-tags. + + --subnet=SUBNET + The VPC subnetwork that the Cloud Run job will get IPs from. The + subnetwork must be /26 or larger. If --network is also specified, + subnet must be a subnetwork of the network specified by the --network + flag. If --network is not specified, network will be looked up from + this subnetwork. To clear existing VPC network settings, use + --clear-network. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/run/instances/delete b/gcloud/alpha/run/instances/delete new file mode 100644 index 000000000..06c82cece --- /dev/null +++ b/gcloud/alpha/run/instances/delete @@ -0,0 +1,58 @@ +NAME + gcloud alpha run instances delete - delete an instance + +SYNOPSIS + gcloud alpha run instances delete INSTANCE [--[no-]async] [--region=REGION] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Delete an instance. + +EXAMPLES + To delete an instance: + + $ gcloud alpha run instances delete instance-name + +POSITIONAL ARGUMENTS + Instance resource - Instance to delete. This represents a Cloud resource. + (NOTE) Some attributes are not given arguments in this group but can be + set in other ways. + + To set the project attribute: + ◆ provide the argument INSTANCE on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + INSTANCE + ID of the Instance or fully qualified identifier for the Instance. + + To set the instances attribute: + ▸ provide the argument INSTANCE on the command line. + +FLAGS + --[no-]async + Return immediately, without waiting for the operation in progress to + complete. Defaults to --no-async. Use --async to enable and --no-async + to disable. + + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/run/instances/help b/gcloud/alpha/run/instances/help index 51d4611f9..98148a42e 100644 --- a/gcloud/alpha/run/instances/help +++ b/gcloud/alpha/run/instances/help @@ -26,6 +26,12 @@ GCLOUD WIDE FLAGS COMMANDS COMMAND is one of the following: + create + (ALPHA) Create a Cloud Run instance. + + delete + (ALPHA) Delete an instance. + describe (ALPHA) Obtain details about instances. diff --git a/gcloud/alpha/run/jobs/create b/gcloud/alpha/run/jobs/create index e0c9e8bee..e322f8bbb 100644 --- a/gcloud/alpha/run/jobs/create +++ b/gcloud/alpha/run/jobs/create @@ -331,7 +331,8 @@ FLAGS KEY_1: "value1" KEY_2: "value 2" - Example ENV content: + + Example ENV content: KEY_1="value1" KEY_2="value 2" diff --git a/gcloud/alpha/run/jobs/deploy b/gcloud/alpha/run/jobs/deploy index 6b8c8f07f..70ab862b1 100644 --- a/gcloud/alpha/run/jobs/deploy +++ b/gcloud/alpha/run/jobs/deploy @@ -333,7 +333,8 @@ FLAGS KEY_1: "value1" KEY_2: "value 2" - Example ENV content: + + Example ENV content: KEY_1="value1" KEY_2="value 2" diff --git a/gcloud/alpha/run/jobs/update b/gcloud/alpha/run/jobs/update index d72d4830e..1176ff37f 100644 --- a/gcloud/alpha/run/jobs/update +++ b/gcloud/alpha/run/jobs/update @@ -347,7 +347,8 @@ FLAGS KEY_1: "value1" KEY_2: "value 2" - Example ENV content: + + Example ENV content: KEY_1="value1" KEY_2="value 2" diff --git a/gcloud/alpha/run/multi-region-services/update b/gcloud/alpha/run/multi-region-services/update index 85e8eefc6..1d546da12 100644 --- a/gcloud/alpha/run/multi-region-services/update +++ b/gcloud/alpha/run/multi-region-services/update @@ -240,7 +240,7 @@ FLAGS and resume server-assigned naming. --scaling=SCALING - The scaling mode to use for this resource. Flag value could be either + The scaling mode to use for this service. Flag value could be either "auto" for automatic scaling, or a positive integer to configure manual scaling with the given integer as a fixed instance count. @@ -490,7 +490,8 @@ FLAGS KEY_1: "value1" KEY_2: "value 2" - Example ENV content: + + Example ENV content: KEY_1="value1" KEY_2="value 2" diff --git a/gcloud/alpha/run/services/update b/gcloud/alpha/run/services/update index da9bbe90e..367ea51e7 100644 --- a/gcloud/alpha/run/services/update +++ b/gcloud/alpha/run/services/update @@ -238,7 +238,7 @@ FLAGS and resume server-assigned naming. --scaling=SCALING - The scaling mode to use for this resource. Flag value could be either + The scaling mode to use for this service. Flag value could be either "auto" for automatic scaling, or a positive integer to configure manual scaling with the given integer as a fixed instance count. @@ -570,7 +570,8 @@ FLAGS KEY_1: "value1" KEY_2: "value 2" - Example ENV content: + + Example ENV content: KEY_1="value1" KEY_2="value 2" diff --git a/gcloud/alpha/run/worker-pools/deploy b/gcloud/alpha/run/worker-pools/deploy index d11970ee7..aaa605d24 100644 --- a/gcloud/alpha/run/worker-pools/deploy +++ b/gcloud/alpha/run/worker-pools/deploy @@ -6,10 +6,10 @@ SYNOPSIS gcloud alpha run worker-pools deploy [[WORKER_POOL] --region=REGION] [--async] [--breakglass=JUSTIFICATION] [--container=CONTAINER] [--description=DESCRIPTION] [--gpu-type=GPU_TYPE] - [--[no-]gpu-zonal-redundancy] [--max=MAX] [--min=MIN] [--no-promote] + [--[no-]gpu-zonal-redundancy] [--instances=INSTANCES] [--no-promote] [--remove-containers=[CONTAINER,...]] - [--revision-suffix=REVISION_SUFFIX] [--scaling=SCALING] - [--service-account=SERVICE_ACCOUNT] [--vpc-egress=VPC_EGRESS] + [--revision-suffix=REVISION_SUFFIX] [--service-account=SERVICE_ACCOUNT] + [--vpc-egress=VPC_EGRESS] [--add-cloudsql-instances=[CLOUDSQL-INSTANCES,...] | --clear-cloudsql-instances | --remove-cloudsql-instances=[CLOUDSQL-INSTANCES,...] @@ -117,17 +117,10 @@ FLAGS Set GPU zonal redundancy. Use --gpu-zonal-redundancy to enable and --no-gpu-zonal-redundancy to disable. - --max=MAX - The maximum number of container instances to run for this WorkerPool or - 'default' to use system default of 100. This instance limit will be - divided among all Revisions receiving a percentage of instance - assignments and can be modified without deploying a new Revision. - - --min=MIN - The minimum number of container instances to run for this WorkerPool or - 'default' to use system default of 1. These instances will be divided - among all Revisions receiving a percentage of instance assignments and - can be modified without deploying a new Revision. + --instances=INSTANCES + The number of instances to run for this WorkerPool. Flag value should + be a positive integer to configure manual scaling with the given + integer as a fixed instance count. --no-promote True to avoid assign instances to the worker revision being deployed. @@ -151,11 +144,6 @@ FLAGS a revision named 'helloworld-v1'. Set empty string to clear the suffix and resume server-assigned naming. - --scaling=SCALING - The scaling mode to use for this resource. Flag value could be either - "auto" for automatic scaling, or a positive integer to configure manual - scaling with the given integer as a fixed instance count. - --service-account=SERVICE_ACCOUNT the email address of an IAM service account associated with the revision of the service. The service account represents the identity of @@ -359,7 +347,8 @@ FLAGS KEY_1: "value1" KEY_2: "value 2" - Example ENV content: + + Example ENV content: KEY_1="value1" KEY_2="value 2" diff --git a/gcloud/alpha/run/worker-pools/logs/help b/gcloud/alpha/run/worker-pools/logs/help index 3a252ba86..b81d041a6 100644 --- a/gcloud/alpha/run/worker-pools/logs/help +++ b/gcloud/alpha/run/worker-pools/logs/help @@ -2,7 +2,8 @@ NAME gcloud alpha run worker-pools logs - read logs for Cloud Run worker pools SYNOPSIS - gcloud alpha run worker-pools logs COMMAND [GCLOUD_WIDE_FLAG ...] + gcloud alpha run worker-pools logs COMMAND [--region=REGION] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Read logs for Cloud Run worker pools. @@ -16,6 +17,11 @@ EXAMPLES $ gcloud alpha run worker-pools logs read my-worker-pool +FLAGS + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. + GCLOUD WIDE FLAGS These flags are available to all commands: --help. @@ -34,5 +40,7 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. This variant is also available: + + $ gcloud beta run worker-pools logs diff --git a/gcloud/alpha/run/worker-pools/logs/read b/gcloud/alpha/run/worker-pools/logs/read index c67b28db0..310743d63 100644 --- a/gcloud/alpha/run/worker-pools/logs/read +++ b/gcloud/alpha/run/worker-pools/logs/read @@ -5,7 +5,8 @@ NAME SYNOPSIS gcloud alpha run worker-pools logs read WORKER_POOL [--freshness=FRESHNESS; default="1d"] [--log-filter=LOG_FILTER] - [--order=ORDER; default="desc"] [--limit=LIMIT] [GCLOUD_WIDE_FLAG ...] + [--order=ORDER; default="desc"] [--region=REGION] [--limit=LIMIT] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) gcloud alpha run worker-pools logs read reads log entries. Log @@ -57,6 +58,10 @@ FLAGS Ordering of returned log entries based on timestamp field. ORDER must be one of: desc, asc. + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. + LIST COMMAND FLAGS --limit=LIMIT Maximum number of resources to list. The default is unlimited. This @@ -75,5 +80,7 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. This variant is also available: + + $ gcloud beta run worker-pools logs read diff --git a/gcloud/alpha/run/worker-pools/logs/tail b/gcloud/alpha/run/worker-pools/logs/tail index c2e3b6ff7..d02f7e4ab 100644 --- a/gcloud/alpha/run/worker-pools/logs/tail +++ b/gcloud/alpha/run/worker-pools/logs/tail @@ -4,7 +4,7 @@ NAME SYNOPSIS gcloud alpha run worker-pools logs tail WORKER_POOL - [--log-filter=LOG_FILTER] [GCLOUD_WIDE_FLAG ...] + [--log-filter=LOG_FILTER] [--region=REGION] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) gcloud alpha run worker-pools logs tail tails log-entries for a @@ -34,6 +34,10 @@ FLAGS information about filters can be found at: https://cloud.google.com/logging/docs/view/logging-query-language + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, @@ -46,5 +50,7 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. This variant is also available: + + $ gcloud beta run worker-pools logs tail diff --git a/gcloud/alpha/run/worker-pools/update b/gcloud/alpha/run/worker-pools/update index 1ea201cfd..0cc26c320 100644 --- a/gcloud/alpha/run/worker-pools/update +++ b/gcloud/alpha/run/worker-pools/update @@ -6,10 +6,10 @@ SYNOPSIS gcloud alpha run worker-pools update [[WORKER_POOL] --region=REGION] [--async] [--breakglass=JUSTIFICATION] [--container=CONTAINER] [--description=DESCRIPTION] [--gpu-type=GPU_TYPE] - [--[no-]gpu-zonal-redundancy] [--max=MAX] [--min=MIN] [--no-promote] + [--[no-]gpu-zonal-redundancy] [--instances=INSTANCES] [--no-promote] [--remove-containers=[CONTAINER,...]] - [--revision-suffix=REVISION_SUFFIX] [--scaling=SCALING] - [--service-account=SERVICE_ACCOUNT] [--vpc-egress=VPC_EGRESS] + [--revision-suffix=REVISION_SUFFIX] [--service-account=SERVICE_ACCOUNT] + [--vpc-egress=VPC_EGRESS] [--add-cloudsql-instances=[CLOUDSQL-INSTANCES,...] | --clear-cloudsql-instances | --remove-cloudsql-instances=[CLOUDSQL-INSTANCES,...] @@ -113,17 +113,10 @@ FLAGS Set GPU zonal redundancy. Use --gpu-zonal-redundancy to enable and --no-gpu-zonal-redundancy to disable. - --max=MAX - The maximum number of container instances to run for this WorkerPool or - 'default' to use system default of 100. This instance limit will be - divided among all Revisions receiving a percentage of instance - assignments and can be modified without deploying a new Revision. - - --min=MIN - The minimum number of container instances to run for this WorkerPool or - 'default' to use system default of 1. These instances will be divided - among all Revisions receiving a percentage of instance assignments and - can be modified without deploying a new Revision. + --instances=INSTANCES + The number of instances to run for this WorkerPool. Flag value should + be a positive integer to configure manual scaling with the given + integer as a fixed instance count. --no-promote True to avoid assign instances to the worker revision being deployed. @@ -147,11 +140,6 @@ FLAGS a revision named 'helloworld-v1'. Set empty string to clear the suffix and resume server-assigned naming. - --scaling=SCALING - The scaling mode to use for this resource. Flag value could be either - "auto" for automatic scaling, or a positive integer to configure manual - scaling with the given integer as a fixed instance count. - --service-account=SERVICE_ACCOUNT the email address of an IAM service account associated with the revision of the service. The service account represents the identity of @@ -359,7 +347,8 @@ FLAGS KEY_1: "value1" KEY_2: "value 2" - Example ENV content: + + Example ENV content: KEY_1="value1" KEY_2="value 2" diff --git a/gcloud/alpha/spanner/instance-partitions/create b/gcloud/alpha/spanner/instance-partitions/create index f73473345..9fdb4c2c1 100644 --- a/gcloud/alpha/spanner/instance-partitions/create +++ b/gcloud/alpha/spanner/instance-partitions/create @@ -6,7 +6,9 @@ SYNOPSIS gcloud alpha spanner instance-partitions create (INSTANCE_PARTITION : --instance=INSTANCE) --config=CONFIG --description=DESCRIPTION [--async] - [--nodes=NODES | --processing-units=PROCESSING_UNITS] + [--nodes=NODES | --processing-units=PROCESSING_UNITS + | --autoscaling-storage-target=AUTOSCALING_STORAGE_TARGET + (--autoscaling-high-priority-cpu-target=AUTOSCALING_HIGH_PRIORITY_CPU_TARGET --autoscaling-total-cpu-target=AUTOSCALING_TOTAL_CPU_TARGET) (--autoscaling-max-nodes=AUTOSCALING_MAX_NODES --autoscaling-min-nodes=AUTOSCALING_MIN_NODES | --autoscaling-max-processing-units=AUTOSCALING_MAX_PROCESSING_UNITS --autoscaling-min-processing-units=AUTOSCALING_MIN_PROCESSING_UNITS)] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -75,6 +77,59 @@ OPTIONAL FLAGS --processing-units=PROCESSING_UNITS Number of processing units for the instance partition. + Autoscaling + + --autoscaling-storage-target=AUTOSCALING_STORAGE_TARGET + Specifies the target percentage of storage the autoscaled instance + can utilize. + + This flag argument must be specified if any of the other arguments + in this group are specified. + + Autoscaling CPU targets. + + At least one of these must be specified: + + --autoscaling-high-priority-cpu-target=AUTOSCALING_HIGH_PRIORITY_CPU_TARGET + Specifies the target percentage of high-priority CPU the + autoscaled instance can utilize. + + --autoscaling-total-cpu-target=AUTOSCALING_TOTAL_CPU_TARGET + Specifies the target percentage of total CPU the autoscaled + instance can utilize. + + Autoscaling limits can be defined in either nodes or processing units. + + Exactly one of these must be specified: + + Autoscaling limits in nodes: + + --autoscaling-max-nodes=AUTOSCALING_MAX_NODES + Maximum number of nodes for the autoscaled instance. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --autoscaling-min-nodes=AUTOSCALING_MIN_NODES + Minimum number of nodes for the autoscaled instance. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + Autoscaling limits in processing units: + + --autoscaling-max-processing-units=AUTOSCALING_MAX_PROCESSING_UNITS + Maximum number of processing units for the autoscaled instance. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --autoscaling-min-processing-units=AUTOSCALING_MIN_PROCESSING_UNITS + Minimum number of processing units for the autoscaled instance. + + This flag argument must be specified if any of the other + arguments in this group are specified. + 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/spanner/instance-partitions/update b/gcloud/alpha/spanner/instance-partitions/update index a02aafac4..42ca04659 100644 --- a/gcloud/alpha/spanner/instance-partitions/update +++ b/gcloud/alpha/spanner/instance-partitions/update @@ -7,7 +7,9 @@ SYNOPSIS gcloud alpha spanner instance-partitions update (INSTANCE_PARTITION : --instance=INSTANCE) [--async] [--description=DESCRIPTION] - [--nodes=NODES | --processing-units=PROCESSING_UNITS] + [--nodes=NODES | --processing-units=PROCESSING_UNITS + | --autoscaling-storage-target=AUTOSCALING_STORAGE_TARGET + --autoscaling-high-priority-cpu-target=AUTOSCALING_HIGH_PRIORITY_CPU_TARGET --autoscaling-total-cpu-target=AUTOSCALING_TOTAL_CPU_TARGET --autoscaling-max-nodes=AUTOSCALING_MAX_NODES --autoscaling-min-nodes=AUTOSCALING_MIN_NODES | --autoscaling-max-processing-units=AUTOSCALING_MAX_PROCESSING_UNITS --autoscaling-min-processing-units=AUTOSCALING_MIN_PROCESSING_UNITS] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -75,6 +77,42 @@ FLAGS --processing-units=PROCESSING_UNITS Number of processing units for the instance partition. + Autoscaling + + --autoscaling-storage-target=AUTOSCALING_STORAGE_TARGET + Specifies the target percentage of storage the autoscaled instance + can utilize. + + Autoscaling CPU targets. + + --autoscaling-high-priority-cpu-target=AUTOSCALING_HIGH_PRIORITY_CPU_TARGET + Specifies the target percentage of high-priority CPU the + autoscaled instance can utilize. + + --autoscaling-total-cpu-target=AUTOSCALING_TOTAL_CPU_TARGET + Specifies the target percentage of total CPU the autoscaled + instance can utilize. + + Autoscaling limits can be defined in either nodes or processing units. + + At most one of these can be specified: + + Autoscaling limits in nodes: + + --autoscaling-max-nodes=AUTOSCALING_MAX_NODES + Maximum number of nodes for the autoscaled instance. + + --autoscaling-min-nodes=AUTOSCALING_MIN_NODES + Minimum number of nodes for the autoscaled instance. + + Autoscaling limits in processing units: + + --autoscaling-max-processing-units=AUTOSCALING_MAX_PROCESSING_UNITS + Maximum number of processing units for the autoscaled instance. + + --autoscaling-min-processing-units=AUTOSCALING_MIN_PROCESSING_UNITS + Minimum number of processing units for the autoscaled instance. + 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/spanner/instances/create b/gcloud/alpha/spanner/instances/create index 422ac31a5..646a4dd0d 100644 --- a/gcloud/alpha/spanner/instances/create +++ b/gcloud/alpha/spanner/instances/create @@ -8,13 +8,15 @@ SYNOPSIS [--edition=EDITION] [--expire-behavior=EXPIRE_BEHAVIOR] [--instance-type=INSTANCE_TYPE] [--nodes=NODES | --processing-units=PROCESSING_UNITS - | [--autoscaling-high-priority-cpu-target=AUTOSCALING_HIGH_PRIORITY_CPU_TARGET --autoscaling-storage-target=AUTOSCALING_STORAGE_TARGET (--autoscaling-max-nodes=AUTOSCALING_MAX_NODES --autoscaling-min-nodes=AUTOSCALING_MIN_NODES | --autoscaling-max-processing-units=AUTOSCALING_MAX_PROCESSING_UNITS --autoscaling-min-processing-units=AUTOSCALING_MIN_PROCESSING_UNITS) : --asymmetric-autoscaling-option=[disable_high_priority_cpu_autoscaling=DISABLE_HIGH_PRIORITY_CPU_AUTOSCALING], + | [--autoscaling-storage-target=AUTOSCALING_STORAGE_TARGET + (--autoscaling-high-priority-cpu-target=AUTOSCALING_HIGH_PRIORITY_CPU_TARGET --autoscaling-total-cpu-target=AUTOSCALING_TOTAL_CPU_TARGET) (--autoscaling-max-nodes=AUTOSCALING_MAX_NODES --autoscaling-min-nodes=AUTOSCALING_MIN_NODES | --autoscaling-max-processing-units=AUTOSCALING_MAX_PROCESSING_UNITS --autoscaling-min-processing-units=AUTOSCALING_MIN_PROCESSING_UNITS) : --asymmetric-autoscaling-option=[disable_high_priority_cpu_autoscaling=DISABLE_HIGH_PRIORITY_CPU_AUTOSCALING], [disable_total_cpu_autoscaling=DISABLE_TOTAL_CPU_AUTOSCALING], [high_priority_cpu_target=HIGH_PRIORITY_CPU_TARGET], [location=LOCATION],[max_nodes=MAX_NODES], [max_processing_units=MAX_PROCESSING_UNITS],[min_nodes=MIN_NODES], [min_processing_units=MIN_PROCESSING_UNITS], - [total_cpu_target=TOTAL_CPU_TARGET]]] [GCLOUD_WIDE_FLAG ...] + [total_cpu_target=TOTAL_CPU_TARGET] --[no-]disable-downscaling]] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Create a Cloud Spanner instance. @@ -107,13 +109,6 @@ OPTIONAL FLAGS Autoscaling - --autoscaling-high-priority-cpu-target=AUTOSCALING_HIGH_PRIORITY_CPU_TARGET - Specifies the target percentage of high-priority CPU the autoscaled - instance can utilize. - - This flag argument must be specified if any of the other arguments - in this group are specified. - --autoscaling-storage-target=AUTOSCALING_STORAGE_TARGET Specifies the target percentage of storage the autoscaled instance can utilize. @@ -124,6 +119,23 @@ OPTIONAL FLAGS --asymmetric-autoscaling-option=[disable_high_priority_cpu_autoscaling=DISABLE_HIGH_PRIORITY_CPU_AUTOSCALING],[disable_total_cpu_autoscaling=DISABLE_TOTAL_CPU_AUTOSCALING],[high_priority_cpu_target=HIGH_PRIORITY_CPU_TARGET],[location=LOCATION],[max_nodes=MAX_NODES],[max_processing_units=MAX_PROCESSING_UNITS],[min_nodes=MIN_NODES],[min_processing_units=MIN_PROCESSING_UNITS],[total_cpu_target=TOTAL_CPU_TARGET] Specifies the asymmetric autoscaling option for the instance. + --[no-]disable-downscaling + Set the flag to disable downscaling for the autoscaled instance. + Use --disable-downscaling to enable and --no-disable-downscaling to + disable. + + Specify one or both CPU targets: + + At least one of these must be specified: + + --autoscaling-high-priority-cpu-target=AUTOSCALING_HIGH_PRIORITY_CPU_TARGET + Specifies the target percentage of high-priority CPU the + autoscaled instance can utilize. + + --autoscaling-total-cpu-target=AUTOSCALING_TOTAL_CPU_TARGET + Specifies the target percentage of total CPU the autoscaled + instance can utilize. + Autoscaling limits can be defined in either nodes or processing units. Exactly one of these must be specified: diff --git a/gcloud/alpha/spanner/instances/update b/gcloud/alpha/spanner/instances/update index 1f3910ca6..872749a57 100644 --- a/gcloud/alpha/spanner/instances/update +++ b/gcloud/alpha/spanner/instances/update @@ -7,7 +7,9 @@ SYNOPSIS [--description=DESCRIPTION] [--edition=EDITION] [--expire-behavior=EXPIRE_BEHAVIOR] [--instance-type=INSTANCE_TYPE] [--nodes=NODES | --processing-units=PROCESSING_UNITS - | --autoscaling-high-priority-cpu-target=AUTOSCALING_HIGH_PRIORITY_CPU_TARGET --autoscaling-storage-target=AUTOSCALING_STORAGE_TARGET --asymmetric-autoscaling-option=[disable_high_priority_cpu_autoscaling=DISABLE_HIGH_PRIORITY_CPU_AUTOSCALING], + | --autoscaling-storage-target=AUTOSCALING_STORAGE_TARGET + --[no-]disable-downscaling + --asymmetric-autoscaling-option=[disable_high_priority_cpu_autoscaling=DISABLE_HIGH_PRIORITY_CPU_AUTOSCALING], [disable_total_cpu_autoscaling=DISABLE_TOTAL_CPU_AUTOSCALING], [high_priority_cpu_target=HIGH_PRIORITY_CPU_TARGET], [location=LOCATION],[max_nodes=MAX_NODES], @@ -15,10 +17,7 @@ SYNOPSIS [min_processing_units=MIN_PROCESSING_UNITS], [total_cpu_target=TOTAL_CPU_TARGET] | --clear-asymmetric-autoscaling-option=LOCATION,[LOCATION,...] - --autoscaling-max-nodes=AUTOSCALING_MAX_NODES - --autoscaling-min-nodes=AUTOSCALING_MIN_NODES - | --autoscaling-max-processing-units=AUTOSCALING_MAX_PROCESSING_UNITS - --autoscaling-min-processing-units=AUTOSCALING_MIN_PROCESSING_UNITS] + --autoscaling-high-priority-cpu-target=AUTOSCALING_HIGH_PRIORITY_CPU_TARGET --autoscaling-total-cpu-target=AUTOSCALING_TOTAL_CPU_TARGET --autoscaling-max-nodes=AUTOSCALING_MAX_NODES --autoscaling-min-nodes=AUTOSCALING_MIN_NODES | --autoscaling-max-processing-units=AUTOSCALING_MAX_PROCESSING_UNITS --autoscaling-min-processing-units=AUTOSCALING_MIN_PROCESSING_UNITS] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -106,14 +105,15 @@ FLAGS Autoscaling - --autoscaling-high-priority-cpu-target=AUTOSCALING_HIGH_PRIORITY_CPU_TARGET - Specifies the target percentage of high-priority CPU the autoscaled - instance can utilize. - --autoscaling-storage-target=AUTOSCALING_STORAGE_TARGET Specifies the target percentage of storage the autoscaled instance can utilize. + --[no-]disable-downscaling + Set the flag to disable downscaling for the autoscaled instance. + Use --disable-downscaling to enable and --no-disable-downscaling to + disable. + At most one of these can be specified: --asymmetric-autoscaling-option=[disable_high_priority_cpu_autoscaling=DISABLE_HIGH_PRIORITY_CPU_AUTOSCALING],[disable_total_cpu_autoscaling=DISABLE_TOTAL_CPU_AUTOSCALING],[high_priority_cpu_target=HIGH_PRIORITY_CPU_TARGET],[location=LOCATION],[max_nodes=MAX_NODES],[max_processing_units=MAX_PROCESSING_UNITS],[min_nodes=MIN_NODES],[min_processing_units=MIN_PROCESSING_UNITS],[total_cpu_target=TOTAL_CPU_TARGET] @@ -123,6 +123,16 @@ FLAGS Specify a comma separated list of locations from which to remove asymmetric autoscaling options + Specify one or both CPU targets: + + --autoscaling-high-priority-cpu-target=AUTOSCALING_HIGH_PRIORITY_CPU_TARGET + Specifies the target percentage of high-priority CPU the + autoscaled instance can utilize. + + --autoscaling-total-cpu-target=AUTOSCALING_TOTAL_CPU_TARGET + Specifies the target percentage of total CPU the autoscaled + instance can utilize. + Autoscaling limits can be defined in either nodes or processing units. At most one of these can be specified: diff --git a/gcloud/alpha/storage/batch-operations/jobs/create b/gcloud/alpha/storage/batch-operations/jobs/create index 6005b0fa1..754a082d1 100644 --- a/gcloud/alpha/storage/batch-operations/jobs/create +++ b/gcloud/alpha/storage/batch-operations/jobs/create @@ -12,6 +12,7 @@ SYNOPSIS | [--delete-object : --enable-permanent-object-deletion] | --[no-]put-object-event-based-hold --[no-]put-object-temporary-hold) [--description=DESCRIPTION] + [--dry-run] [--log-actions=[LOG_ACTIONS,...] --log-action-states=[LOG_ACTION_STATES,...]] [GCLOUD_WIDE_FLAG ...] @@ -21,6 +22,15 @@ DESCRIPTION manner. EXAMPLES + The following example command creates a batch job, named my-dry-run, that + performs a dry run of object deletion on bucket my-bucket for objects + specified in the manifest file gs://my-bucket/manifest.csv: + + $ gcloud alpha storage batch-operations jobs create my-dry-run-job \ + --bucket=my-bucket \ + --manifest-location=gs://my-bucket/manifest.csv \ + --delete-object --dry-run + The following example command creates a batch job, named my-job, that performs object deletion on bucket my-bucket for objects specified in the manifest file gs://my-bucket/manifest.csv: @@ -175,6 +185,11 @@ FLAGS --description=DESCRIPTION Description for the batch job. + --dry-run + If true, the job will run in dry run mode, returning the total object + count and, if the object configuration is a prefix list, the bytes + found from source. No transformations will be performed. + LOGGING_CONFIG FLAGS LOGGING CONFIG diff --git a/gcloud/alpha/storage/cp b/gcloud/alpha/storage/cp index 6d4017096..1da778e99 100644 --- a/gcloud/alpha/storage/cp +++ b/gcloud/alpha/storage/cp @@ -189,9 +189,13 @@ FLAGS --read-paths-from-stdin, -I Read the list of resources to copy from stdin. No need to enter a source argument if this flag is present. Example: "storage cp -I - gs://bucket/destination" Note: To copy the contents of one file - directly from stdin, use "-" as the source argument without the "-I" - flag. + gs://bucket/destination". The input format must consist of one path + (e.g., "Documents/data/file1.txt") or one object URL (e.g., + "gs://example-bucket/event.log") per line. Use a pipe to send the file + list to the command. Example: "cat example-file-list.txt | gcloud + storage cp --read-paths-from-stdin gs://example-destination-bucket". + Note: To copy the contents of one file directly from stdin, use "-" as + the source argument without the "-I" flag. --recursive, -R, -r Recursively copy the contents of any directories that match the source diff --git a/gcloud/alpha/storage/help b/gcloud/alpha/storage/help index 0234cbf6d..493cec754 100644 --- a/gcloud/alpha/storage/help +++ b/gcloud/alpha/storage/help @@ -41,9 +41,6 @@ GROUPS managed-folders (ALPHA) Manage Cloud Storage managed folders. - management-hub - (ALPHA) (DEPRECATED) Manage Cloud Storage Management Hub. - objects (ALPHA) Manage Cloud Storage objects. diff --git a/gcloud/alpha/storage/management-hub/describe b/gcloud/alpha/storage/management-hub/describe deleted file mode 100644 index da23f648f..000000000 --- a/gcloud/alpha/storage/management-hub/describe +++ /dev/null @@ -1,46 +0,0 @@ -NAME - gcloud alpha storage management-hub describe - describes Management Hub - -SYNOPSIS - gcloud alpha storage management-hub describe - (--organization=ORGANIZATION | --project=PROJECT - | --sub-folder=SUB_FOLDER) [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) (DEPRECATED) This command group is deprecated. Use gcloud alpha - storage intelligence-configs command group instead. - - Describe management hub for the organization, sub-folder or project. - -EXAMPLES - The following command describes management hub for the sub-folder with id - 123456. - - $gcloud alpha storage management-hub describe --sub-folder=123456 - -REQUIRED FLAGS - Exactly one of these must be specified: - - --organization=ORGANIZATION - Specifies organization id for the management hub. - - --project=PROJECT - Specifies project for the management hub. - - --sub-folder=SUB_FOLDER - Specifies sub-folder id for the management hub. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -NOTES - This command is currently in alpha and might change without notice. If this - command fails with API permission errors despite specifying the correct - project, you might be trying to access an API with an invitation-only early - access allowlist. - diff --git a/gcloud/alpha/storage/management-hub/disable b/gcloud/alpha/storage/management-hub/disable deleted file mode 100644 index 458b0d4a7..000000000 --- a/gcloud/alpha/storage/management-hub/disable +++ /dev/null @@ -1,45 +0,0 @@ -NAME - gcloud alpha storage management-hub disable - disables Management Hub - -SYNOPSIS - gcloud alpha storage management-hub disable - (--organization=ORGANIZATION | --project=PROJECT - | --sub-folder=SUB_FOLDER) [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) (DEPRECATED) This command group is deprecated. Use gcloud alpha - storage intelligence-configs command group instead. - - Disable management hub for the organization, sub-folder or project. - -EXAMPLES - The following command disables management hub for the project. - - $gcloud alpha storage management-hub disable --project=my-project - -REQUIRED FLAGS - Exactly one of these must be specified: - - --organization=ORGANIZATION - Specifies organization id for the management hub. - - --project=PROJECT - Specifies project for the management hub. - - --sub-folder=SUB_FOLDER - Specifies sub-folder id for the management hub. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -NOTES - This command is currently in alpha and might change without notice. If this - command fails with API permission errors despite specifying the correct - project, you might be trying to access an API with an invitation-only early - access allowlist. - diff --git a/gcloud/alpha/storage/management-hub/enable b/gcloud/alpha/storage/management-hub/enable deleted file mode 100644 index 290bb62ed..000000000 --- a/gcloud/alpha/storage/management-hub/enable +++ /dev/null @@ -1,118 +0,0 @@ -NAME - gcloud alpha storage management-hub enable - enables Management Hub - -SYNOPSIS - gcloud alpha storage management-hub enable - (--organization=ORGANIZATION | --project=PROJECT - | --sub-folder=SUB_FOLDER) - [--exclude-locations=[EXCLUDE_LOCATIONS,...] - | --include-locations=[INCLUDE_LOCATIONS,...]] - [--exclude-bucket-id-regexes=[EXCLUDE_BUCKET_ID_REGEXES,...] - --exclude-bucket-ids=[EXCLUDE_BUCKET_IDS,...] - | --include-bucket-id-regexes=[INCLUDE_BUCKET_ID_REGEXES,...] - --include-bucket-ids=[INCLUDE_BUCKET_IDS,...]] [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) (DEPRECATED) This command group is deprecated. Use gcloud alpha - storage intelligence-configs command group instead. - - Enable management hub plan for the organization, sub-folder or project - along with filters. - -EXAMPLES - To remove buckets from the management hub plan, Use the following command - with --exclude-bucket-ids and --exclude-bucket-regexes flags to specify - list of bucket ids and bucket id regexes., - - $gcloud alpha storage management-hub enable --organization=my-org --exclude-bucket-ids="my-bucket" --exclude-bucket-regexes="my-bucket-.*" - - To apply location based filters in the management hub plan, Use - --include-locations or --exclude-locations flags to specify allowed list of - locations or excluded list of locations. The following command updates - management hub plan of sub-folder 123456 with the specified list of - included locations., - - $gcloud alpha storage management-hub enable --sub-folder=123456 --include-locations="us-east1","us-west1" - -REQUIRED FLAGS - Exactly one of these must be specified: - - --organization=ORGANIZATION - Specifies organization id for the management hub. - - --project=PROJECT - Specifies project for the management hub. - - --sub-folder=SUB_FOLDER - Specifies sub-folder id for the management hub. - -LOCATION FLAGS - At most one of these can be specified: - - --exclude-locations=[EXCLUDE_LOCATIONS,...] - Comma separated list of locations - (https://cloud.google.com/storage/docs/locations#available-locations) - to exclude in Management Hub filter. To clear excluded locations, - provide flag with empty list. e.g --exclude-locations="" or - --exclude-locations= . - - --include-locations=[INCLUDE_LOCATIONS,...] - Comma separated list of locations - (https://cloud.google.com/storage/docs/locations#available-locations) - to include in management hub filter. To clear included locations, - provide flag with empty list. e.g --include-locations="" or - --include-locations= . - -BUCKET_FILTER FLAGS - At most one of these can be specified: - - Sets the cloud storage buckets exclusion filter. Full filters should be - specified using available flags in this group, gcloud CLI infers missing - flags of this group as empty which will result in clearing of the - individual filters. - - --exclude-bucket-id-regexes=[EXCLUDE_BUCKET_ID_REGEXES,...] - Sets filter for bucket id regexes to exclude. Accepts list of - bucket id regexes in comma separated format. If the regex contains - special characters that may have a specific meaning in the shell, - escape them using backslashes(\). To clear bucket id regexes list, - provide flag with an empty list. e.g --exclude-bucket-id-regexes="" - or --exclude-bucket-id-regexes= . - - --exclude-bucket-ids=[EXCLUDE_BUCKET_IDS,...] - Comma separated list of bucket ids to exclude in the management hub - filter. To clear bucket id list, provide flag with an empty list. - e.g --exclude-bucket-ids="" or --exclude-bucket-ids= . - - Sets the cloud storage buckets inclusion filter. Full filters should be - specified using available flags in this group, gcloud CLI infers missing - flags of this group as empty which will result in clearing of the - individual filters. - - --include-bucket-id-regexes=[INCLUDE_BUCKET_ID_REGEXES,...] - Sets filter for bucket id regexes to include. Accepts list of - bucket id regexes in comma separated format. If the regex contains - special characters that may have a specific meaning in the shell, - escape them using backslashes(\). To clear bucket id regexes list, - provide flag with empty list. e.g --include-bucket-id-regexes="" or - --include-bucket-id-regexes= . - - --include-bucket-ids=[INCLUDE_BUCKET_IDS,...] - Comma separated list of bucket ids to include in the management hub - filter. To clear bucket id list, provide flag with empty list. e.g - --include-bucket-ids="" or --include-bucket-ids= . - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -NOTES - This command is currently in alpha and might change without notice. If this - command fails with API permission errors despite specifying the correct - project, you might be trying to access an API with an invitation-only early - access allowlist. - diff --git a/gcloud/alpha/storage/management-hub/help b/gcloud/alpha/storage/management-hub/help deleted file mode 100644 index 4b3116aab..000000000 --- a/gcloud/alpha/storage/management-hub/help +++ /dev/null @@ -1,38 +0,0 @@ -NAME - gcloud alpha storage management-hub - manage Cloud Storage Management Hub - -SYNOPSIS - gcloud alpha storage management-hub COMMAND [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) (DEPRECATED) Manage Cloud Storage Management Hub. - - This command group is deprecated. Use gcloud alpha storage - intelligence-configs command group instead. - -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) (DEPRECATED) Describes Management Hub. - - disable - (ALPHA) (DEPRECATED) Disables Management Hub. - - enable - (ALPHA) (DEPRECATED) Enables Management Hub. - - update - (ALPHA) (DEPRECATED) Updates Management Hub. - -NOTES - This command is currently in alpha and might change without notice. If this - command fails with API permission errors despite specifying the correct - project, you might be trying to access an API with an invitation-only early - access allowlist. - diff --git a/gcloud/alpha/storage/management-hub/update b/gcloud/alpha/storage/management-hub/update deleted file mode 100644 index b829d09e9..000000000 --- a/gcloud/alpha/storage/management-hub/update +++ /dev/null @@ -1,143 +0,0 @@ -NAME - gcloud alpha storage management-hub update - updates Management Hub - -SYNOPSIS - gcloud alpha storage management-hub update - (--organization=ORGANIZATION | --project=PROJECT - | --sub-folder=SUB_FOLDER) - (--inherit-from-parent - | --exclude-bucket-id-regexes=[EXCLUDE_BUCKET_ID_REGEXES,...] - --exclude-bucket-ids=[EXCLUDE_BUCKET_IDS,...] - | --include-bucket-id-regexes=[INCLUDE_BUCKET_ID_REGEXES,...] - --include-bucket-ids=[INCLUDE_BUCKET_IDS,...] - --exclude-locations=[EXCLUDE_LOCATIONS,...] - | --include-locations=[INCLUDE_LOCATIONS,...]) [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) (DEPRECATED) This command group is deprecated. Use gcloud alpha - storage intelligence-configs command group instead. - - Update management hub plan for the organization, sub-folder or project. - -EXAMPLES - To limit buckets in the management hub plan, Use the following command with - --include-bucket-ids and --include-bucket-regexes flags to specify list of - bucket ids and bucket id regexes., - - $gcloud alpha storage management-hub update --organization=my-org --include-bucket-ids=my-bucket --include-bucket-regexes=my-bucket-.* - - To apply location based filters in the management hub plan, Use - --include-locations or --exclude-locations flags to specify allowed list of - locations or excluded list of locations. The following command updates - management hub plan of sub-folder 123456 with the specified list of - excluded locations., - - $gcloud alpha storage management-hub update --sub-folder=123456 --exclude-locations=us-east1,us-west1 - - The following command updates management hub for the given project by - inheriting existing management hub plan from the hierarchical parent - resource., - - $gcloud alpha storage management-hub update --project=my-project --inherit-from-parent - - To clear included locations from the project management hub, Use the - following command., - - $gcloud alpha storage management-hub update --project=my-project --include-locations= - - To clear excluded bucket ids from the project management hub and to replace - existing excluded bucket ids regexes, Use the following command., - - $gcloud alpha storage management-hub update --project=my-project --exclude-bucket-id-regexes="test1*","test2*" --exclude-bucket-ids="" - - Alternatively, use the following command to do same operation since the - absense of cloud storage bucket filter flags will be considered as empty - list, - - $gcloud alpha storage management-hub update --project=my-project --exclude-bucket-id-regexes="test1*","test2*" - -REQUIRED FLAGS - Exactly one of these must be specified: - - --organization=ORGANIZATION - Specifies organization id for the management hub. - - --project=PROJECT - Specifies project for the management hub. - - --sub-folder=SUB_FOLDER - Specifies sub-folder id for the management hub. - - Exactly one of these must be specified: - - --inherit-from-parent - Specifies management hub config to be inherited from parent. - - At most one of these can be specified: - - Sets the cloud storage buckets exclusion filter. Full filters should - be specified using available flags in this group, gcloud CLI infers - missing flags of this group as empty which will result in clearing of - the individual filters. - - --exclude-bucket-id-regexes=[EXCLUDE_BUCKET_ID_REGEXES,...] - Sets filter for bucket id regexes to exclude. Accepts list of - bucket id regexes in comma separated format. If the regex - contains special characters that may have a specific meaning in - the shell, escape them using backslashes(\). To clear bucket id - regexes list, provide flag with an empty list. e.g - --exclude-bucket-id-regexes="" or --exclude-bucket-id-regexes= . - - --exclude-bucket-ids=[EXCLUDE_BUCKET_IDS,...] - Comma separated list of bucket ids to exclude in the management - hub filter. To clear bucket id list, provide flag with an empty - list. e.g --exclude-bucket-ids="" or --exclude-bucket-ids= . - - Sets the cloud storage buckets inclusion filter. Full filters should - be specified using available flags in this group, gcloud CLI infers - missing flags of this group as empty which will result in clearing of - the individual filters. - - --include-bucket-id-regexes=[INCLUDE_BUCKET_ID_REGEXES,...] - Sets filter for bucket id regexes to include. Accepts list of - bucket id regexes in comma separated format. If the regex - contains special characters that may have a specific meaning in - the shell, escape them using backslashes(\). To clear bucket id - regexes list, provide flag with empty list. e.g - --include-bucket-id-regexes="" or --include-bucket-id-regexes= . - - --include-bucket-ids=[INCLUDE_BUCKET_IDS,...] - Comma separated list of bucket ids to include in the management - hub filter. To clear bucket id list, provide flag with empty - list. e.g --include-bucket-ids="" or --include-bucket-ids= . - - At most one of these can be specified: - - --exclude-locations=[EXCLUDE_LOCATIONS,...] - Comma separated list of locations - (https://cloud.google.com/storage/docs/locations#available-locations) - to exclude in Management Hub filter. To clear excluded locations, - provide flag with empty list. e.g --exclude-locations="" or - --exclude-locations= . - - --include-locations=[INCLUDE_LOCATIONS,...] - Comma separated list of locations - (https://cloud.google.com/storage/docs/locations#available-locations) - to include in management hub filter. To clear included locations, - provide flag with empty list. e.g --include-locations="" or - --include-locations= . - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -NOTES - This command is currently in alpha and might change without notice. If this - command fails with API permission errors despite specifying the correct - project, you might be trying to access an API with an invitation-only early - access allowlist. - diff --git a/gcloud/alpha/storage/mv b/gcloud/alpha/storage/mv index d0503a18d..856cd2d3a 100644 --- a/gcloud/alpha/storage/mv +++ b/gcloud/alpha/storage/mv @@ -194,9 +194,13 @@ FLAGS --read-paths-from-stdin, -I Read the list of resources to copy from stdin. No need to enter a source argument if this flag is present. Example: "storage cp -I - gs://bucket/destination" Note: To copy the contents of one file - directly from stdin, use "-" as the source argument without the "-I" - flag. + gs://bucket/destination". The input format must consist of one path + (e.g., "Documents/data/file1.txt") or one object URL (e.g., + "gs://example-bucket/event.log") per line. Use a pipe to send the file + list to the command. Example: "cat example-file-list.txt | gcloud + storage cp --read-paths-from-stdin gs://example-destination-bucket". + Note: To copy the contents of one file directly from stdin, use "-" as + the source argument without the "-I" flag. --skip-unsupported, -U Skip objects with unsupported object types. diff --git a/gcloud/alpha/transfer/jobs/create b/gcloud/alpha/transfer/jobs/create index 2db45ef0a..29a418e48 100644 --- a/gcloud/alpha/transfer/jobs/create +++ b/gcloud/alpha/transfer/jobs/create @@ -16,7 +16,7 @@ SYNOPSIS --schedule-repeats-every=SCHEDULE_REPEATS_EVERY --schedule-repeats-until=SCHEDULE_REPEATS_UNTIL] [--include-prefixes=[INCLUDED_PREFIXES,...] - --exclude-prefixes=[EXCLUDED_PREFIXES,...] + --exclude-prefixes=[EXCLUDED_PREFIXES,...] --match-glob=MATCH_GLOB --include-modified-before-absolute=INCLUDE_MODIFIED_BEFORE_ABSOLUTE --include-modified-after-absolute=INCLUDE_MODIFIED_AFTER_ABSOLUTE --include-modified-before-relative=INCLUDE_MODIFIED_BEFORE_RELATIVE @@ -261,6 +261,11 @@ FLAGS multiple prefixes with commas, omitting spaces after the commas (e.g., --exclude-prefixes=foo,bar). + --match-glob=MATCH_GLOB + Include only objects that match the specified glob pattern. For more + information about glob patterns, see + https://docs.cloud.google.com/storage-transfer/docs/filter-by-glob-pattern + --include-modified-before-absolute=INCLUDE_MODIFIED_BEFORE_ABSOLUTE Include objects last modified before an absolute date/time. Ex. by specifying '2020-01-01', the transfer would include objects last diff --git a/gcloud/alpha/transfer/jobs/update b/gcloud/alpha/transfer/jobs/update index da0e83f05..2c26e0d19 100644 --- a/gcloud/alpha/transfer/jobs/update +++ b/gcloud/alpha/transfer/jobs/update @@ -18,13 +18,13 @@ SYNOPSIS [--clear-schedule --schedule-starts=SCHEDULE_STARTS --schedule-repeats-every=SCHEDULE_REPEATS_EVERY --schedule-repeats-until=SCHEDULE_REPEATS_UNTIL] - [--clear-include-prefixes --clear-exclude-prefixes + [--clear-include-prefixes --clear-exclude-prefixes --clear-match-glob --clear-include-modified-before-absolute --clear-include-modified-after-absolute --clear-include-modified-before-relative --clear-include-modified-after-relative --include-prefixes=[INCLUDED_PREFIXES,...] - --exclude-prefixes=[EXCLUDED_PREFIXES,...] + --exclude-prefixes=[EXCLUDED_PREFIXES,...] --match-glob=MATCH_GLOB --include-modified-before-absolute=INCLUDE_MODIFIED_BEFORE_ABSOLUTE --include-modified-after-absolute=INCLUDE_MODIFIED_AFTER_ABSOLUTE --include-modified-before-relative=INCLUDE_MODIFIED_BEFORE_RELATIVE @@ -279,6 +279,9 @@ FLAGS Remove the list of object prefixes to exclude from the object conditions. + --clear-match-glob + Remove the glob pattern from the object conditions. + --clear-include-modified-before-absolute Remove the maximum modification datetime from the object conditions. @@ -303,6 +306,11 @@ FLAGS multiple prefixes with commas, omitting spaces after the commas (e.g., --exclude-prefixes=foo,bar). + --match-glob=MATCH_GLOB + Include only objects that match the specified glob pattern. For more + information about glob patterns, see + https://docs.cloud.google.com/storage-transfer/docs/filter-by-glob-pattern + --include-modified-before-absolute=INCLUDE_MODIFIED_BEFORE_ABSOLUTE Include objects last modified before an absolute date/time. Ex. by specifying '2020-01-01', the transfer would include objects last diff --git a/gcloud/backup-dr/help b/gcloud/backup-dr/help index d541f698b..fd4465acf 100644 --- a/gcloud/backup-dr/help +++ b/gcloud/backup-dr/help @@ -45,6 +45,10 @@ GROUPS operations Manage Backup and DR operations. + resource-backup-config + Show protection summary for resources in a particular location and + project. + service-config Manage Backup and DR Service configuration. diff --git a/gcloud/backup-dr/resource-backup-config/help b/gcloud/backup-dr/resource-backup-config/help new file mode 100644 index 000000000..aa4cb216f --- /dev/null +++ b/gcloud/backup-dr/resource-backup-config/help @@ -0,0 +1,27 @@ +NAME + gcloud backup-dr resource-backup-config - show protection summary for + resources in a particular location and project + +SYNOPSIS + gcloud backup-dr resource-backup-config COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Show protection summary for resources in a particular location and project. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + list + Show backup configuration metadata associated with specified resources + in a particular location for the project. + +NOTES + This variant is also available: + + $ gcloud alpha backup-dr resource-backup-config + diff --git a/gcloud/backup-dr/resource-backup-config/list b/gcloud/backup-dr/resource-backup-config/list new file mode 100644 index 000000000..8176bfbed --- /dev/null +++ b/gcloud/backup-dr/resource-backup-config/list @@ -0,0 +1,141 @@ +NAME + gcloud backup-dr resource-backup-config list - show backup configuration + metadata associated with specified resources in a particular location + for the project + +SYNOPSIS + gcloud backup-dr resource-backup-config list --location=LOCATION + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Show backup configuration metadata associated with specified resources in a + particular location for the project. + +EXAMPLES + ▪ To list protection summary for a resource named resource-1: + + $ gcloud backup-dr resource-backup-config list \ + --project=sample-project --location=us-central1 \ + --filter="target_resource_display_name=resource-1" + + ▪ To list protection summary for a resource named resource-1 that has + backup configured: + + $ gcloud backup-dr resource-backup-config list \ + --project=sample-project --location=us-central1 \ + --filter="target_resource_display_name=resource-1 AND \ + backup_configured=true" + + You can sort the results using the --sort-by flag. The only supported field + for sorting is target_resource_display_name. + + Example of sorting: + + $ gcloud backup-dr resource-backup-config list \ + --project=sample-project --location=us-central1 \ + --sort-by="target_resource_display_name" + +REQUIRED FLAGS + Location resource - Location for which the resource backup config should + be listed. This represents a Cloud resource. (NOTE) Some attributes are + not given arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument --location on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + --location=LOCATION + ID of the location or fully qualified identifier for the location. + + To set the location attribute: + ▸ provide the argument --location on the command line. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +BRIEF + list backup configurations for a specified project and location. + +FLAGS/ARGUMENTS + --project: Project for which backup configurations should be listed. + + --location: Location for which backup configurations should be listed. + + --filter: The filter expression to filter results. + + --sort-by: The field to sort results by. + +SUBARGUMENTS + target_resource_display_name: Name of the resource for which protection + summary is to be listed. + + target_resource_type: Type of resource for which protection summary is to + be displayed. + + Allowed values: + ▪ CLOUD_SQL_INSTANCE + ▪ COMPUTE_ENGINE_VM + + backup_configured: Displays if the specified resource has backups + configured. + + vaulted: Displays if configured backups are protected using a backup vault. + + backup_configs_details.backup_config_source_display_name: Name of the + backup schedule applied to the resource. + + backup_configs_details.type: Backup schedule type applied to the resource. + + Allowed values: + ▪ CLOUD_SQL_INSTANCE_BACKUP_CONFIG + ▪ COMPUTE_ENGINE_RESOURCE_POLICY + ▪ BACKUPDR_BACKUP_PLAN + ▪ BACKUPDR_TEMPLATE + +NOTES + This variant is also available: + + $ gcloud alpha backup-dr resource-backup-config list + diff --git a/gcloud/beta/composer/environments/create b/gcloud/beta/composer/environments/create index 6f5cd63ff..b31a8dd48 100644 --- a/gcloud/beta/composer/environments/create +++ b/gcloud/beta/composer/environments/create @@ -375,12 +375,12 @@ FLAGS --enable-ip-alias Enable use of alias IPs - (https://cloud.google.com/compute/docs/alias-ip/) for Pod IPs. This + (https://cloud.google.com/compute/docs/alias-ip) for Pod IPs. This will require at least two secondary ranges in the subnetwork, one for the pod IPs and another to reserve space for the services range. --enable-ip-masq-agent - When enabled, the IP Masquarade Agent + When enabled, the IP Masquerade Agent (https://cloud.google.com/composer/docs/enable-ip-masquerade-agent) is deployed to your environment's cluster. It performs many-to-one IP address translations to hide a pod's IP address behind the cluster @@ -463,7 +463,7 @@ FLAGS --enable-master-authorized-networks Enable Master Authorized Networks feature - (https://cloud.google.com/kubernetes-engine/docs/how-to/authorized-networks/) + (https://cloud.google.com/kubernetes-engine/docs/how-to/authorized-networks) in the Composer Environment's GKE cluster. --master-authorized-networks=[NETWORK,...] diff --git a/gcloud/beta/composer/environments/update b/gcloud/beta/composer/environments/update index fd0200098..70b65de8a 100644 --- a/gcloud/beta/composer/environments/update +++ b/gcloud/beta/composer/environments/update @@ -249,12 +249,12 @@ REQUIRED FLAGS --disable-master-authorized-networks Disable Master Authorized Networks feature - (https://cloud.google.com/kubernetes-engine/docs/how-to/authorized-networks/) + (https://cloud.google.com/kubernetes-engine/docs/how-to/authorized-networks) in the Composer Environment's GKE cluster. --enable-master-authorized-networks Enable Master Authorized Networks feature - (https://cloud.google.com/kubernetes-engine/docs/how-to/authorized-networks/) + (https://cloud.google.com/kubernetes-engine/docs/how-to/authorized-networks) in the Composer Environment's GKE cluster. --master-authorized-networks=[NETWORK,...] diff --git a/gcloud/beta/compute/backend-services/import b/gcloud/beta/compute/backend-services/import index 2e1abefc8..3ca580a27 100644 --- a/gcloud/beta/compute/backend-services/import +++ b/gcloud/beta/compute/backend-services/import @@ -21,8 +21,8 @@ POSITIONAL ARGUMENTS FLAGS --source=SOURCE Path to a YAML file containing configuration export data. - Alternatively, you may omit this flag to read from standard input.For a - schema describing the export/import format, see: + Alternatively, you may omit this flag to read from standard input. For + a schema describing the export/import format, see: $CLOUDSDKROOT/lib/googlecloudsdk/schemas/compute/beta/BackendService.yaml. Note: $CLOUDSDKROOT represents the Google Cloud CLI's installation directory. diff --git a/gcloud/beta/compute/commitments/create b/gcloud/beta/compute/commitments/create index e3af9f630..91a0bde78 100644 --- a/gcloud/beta/compute/commitments/create +++ b/gcloud/beta/compute/commitments/create @@ -115,8 +115,11 @@ OPTIONAL FLAGS general-purpose-n2d, general-purpose-n4, general-purpose-n4d, general-purpose-t2d, graphics-optimized, graphics-optimized-g4, memory-optimized, memory-optimized-m3, memory-optimized-m4, - memory-optimized-m4-6tb, memory-optimized-x4-16tb, + memory-optimized-m4-6tb, memory-optimized-x4-1440-24t, + memory-optimized-x4-16tb, memory-optimized-x4-1920-32t, memory-optimized-x4-24tb, memory-optimized-x4-32tb, + memory-optimized-x4-480-6t, memory-optimized-x4-480-8t, + memory-optimized-x4-960-12t, memory-optimized-x4-960-16t, storage-optimized-z3. Manage the reservations to be created with the commitment. diff --git a/gcloud/beta/compute/firewall-policies/import-rules b/gcloud/beta/compute/firewall-policies/import-rules index d53c6bd88..268d46062 100644 --- a/gcloud/beta/compute/firewall-policies/import-rules +++ b/gcloud/beta/compute/firewall-policies/import-rules @@ -27,8 +27,8 @@ FLAGS --source=SOURCE Path to a YAML file containing configuration export data. - Alternatively, you may omit this flag to read from standard input.For a - schema describing the export/import format, see: + Alternatively, you may omit this flag to read from standard input. For + a schema describing the export/import format, see: $CLOUDSDKROOT/lib/googlecloudsdk/schemas/compute/beta/FirewallPolicy.yaml. Note: $CLOUDSDKROOT represents the Google Cloud CLI's installation directory. diff --git a/gcloud/beta/compute/firewall-policies/rules/create b/gcloud/beta/compute/firewall-policies/rules/create index 9422e037c..c09d6e7da 100644 --- a/gcloud/beta/compute/firewall-policies/rules/create +++ b/gcloud/beta/compute/firewall-policies/rules/create @@ -8,6 +8,7 @@ SYNOPSIS [--description=DESCRIPTION] [--dest-address-groups=[DEST_ADDRESS_GROUPS,...]] [--dest-fqdns=[DEST_FQDNS,...]] [--dest-ip-ranges=[DEST_IP_RANGE,...]] + [--dest-network-context=DEST_NETWORK_CONTEXT] [--dest-network-type=DEST_NETWORK_TYPE] [--dest-region-codes=[DEST_REGION_CODES,...]] [--dest-threat-intelligence=[DEST_THREAT_INTELLIGENCE_LISTS,...]] @@ -16,6 +17,7 @@ SYNOPSIS [--security-profile-group=SECURITY_PROFILE_GROUP] [--src-address-groups=[SOURCE_ADDRESS_GROUPS,...]] [--src-fqdns=[SOURCE_FQDNS,...]] [--src-ip-ranges=[SRC_IP_RANGE,...]] + [--src-network-context=SRC_NETWORK_CONTEXT] [--src-network-type=SRC_NETWORK_TYPE] [--src-networks=[SRC_NETWORKS,...]] [--src-region-codes=[SOURCE_REGION_CODES,...]] @@ -70,6 +72,12 @@ OPTIONAL FLAGS --dest-ip-ranges=[DEST_IP_RANGE,...] Destination IP ranges to match for this rule. + --dest-network-context=DEST_NETWORK_CONTEXT + Use this flag to indicate that the rule should match internet or + non-internet traffic. It applies to destination traffic for egress + rules. Valid values are INTERNET and NON_INTERNET. Use empty string to + clear the field. + --dest-network-type=DEST_NETWORK_TYPE Use this flag to indicate that the rule should match internet or non-internet traffic. It applies to destination traffic for egress @@ -127,6 +135,13 @@ OPTIONAL FLAGS --src-ip-ranges=[SRC_IP_RANGE,...] Source IP ranges to match for this rule. + --src-network-context=SRC_NETWORK_CONTEXT + Use this flag to indicate that the rule should match internet, + non-internet traffic or traffic coming from the network specified by + --src-network. It applies to ingress rules. Valid values are INTERNET, + NON_INTERNET, VPC_NETWORKS and INTRA_VPC. Use empty string to clear the + field. + --src-network-type=SRC_NETWORK_TYPE Use this flag to indicate that the rule should match internet, non-internet traffic or traffic coming from the network specified by diff --git a/gcloud/beta/compute/firewall-policies/rules/update b/gcloud/beta/compute/firewall-policies/rules/update index a2e7de33e..9055fe53e 100644 --- a/gcloud/beta/compute/firewall-policies/rules/update +++ b/gcloud/beta/compute/firewall-policies/rules/update @@ -8,6 +8,7 @@ SYNOPSIS [--description=DESCRIPTION] [--dest-address-groups=[DEST_ADDRESS_GROUPS,...]] [--dest-fqdns=[DEST_FQDNS,...]] [--dest-ip-ranges=[DEST_IP_RANGE,...]] + [--dest-network-context=DEST_NETWORK_CONTEXT] [--dest-network-type=DEST_NETWORK_TYPE] [--dest-region-codes=[DEST_REGION_CODES,...]] [--dest-threat-intelligence=[DEST_THREAT_INTELLIGENCE_LISTS,...]] @@ -17,6 +18,7 @@ SYNOPSIS [--security-profile-group=SECURITY_PROFILE_GROUP] [--src-address-groups=[SOURCE_ADDRESS_GROUPS,...]] [--src-fqdns=[SOURCE_FQDNS,...]] [--src-ip-ranges=[SRC_IP_RANGE,...]] + [--src-network-context=SRC_NETWORK_CONTEXT] [--src-network-type=SRC_NETWORK_TYPE] [--src-networks=[SRC_NETWORKS,...]] [--src-region-codes=[SOURCE_REGION_CODES,...]] @@ -68,6 +70,12 @@ OPTIONAL FLAGS --dest-ip-ranges=[DEST_IP_RANGE,...] Destination IP ranges to match for this rule. + --dest-network-context=DEST_NETWORK_CONTEXT + Use this flag to indicate that the rule should match internet or + non-internet traffic. It applies to destination traffic for egress + rules. Valid values are INTERNET and NON_INTERNET. Use empty string to + clear the field. + --dest-network-type=DEST_NETWORK_TYPE Use this flag to indicate that the rule should match internet or non-internet traffic. It applies to destination traffic for egress @@ -132,6 +140,13 @@ OPTIONAL FLAGS --src-ip-ranges=[SRC_IP_RANGE,...] Source IP ranges to match for this rule. + --src-network-context=SRC_NETWORK_CONTEXT + Use this flag to indicate that the rule should match internet, + non-internet traffic or traffic coming from the network specified by + --src-network. It applies to ingress rules. Valid values are INTERNET, + NON_INTERNET, VPC_NETWORKS and INTRA_VPC. Use empty string to clear the + field. + --src-network-type=SRC_NETWORK_TYPE Use this flag to indicate that the rule should match internet, non-internet traffic or traffic coming from the network specified by diff --git a/gcloud/beta/compute/forwarding-rules/import b/gcloud/beta/compute/forwarding-rules/import index 151ae5304..1f9efdd8c 100644 --- a/gcloud/beta/compute/forwarding-rules/import +++ b/gcloud/beta/compute/forwarding-rules/import @@ -21,8 +21,8 @@ POSITIONAL ARGUMENTS FLAGS --source=SOURCE Path to a YAML file containing configuration export data. - Alternatively, you may omit this flag to read from standard input.For a - schema describing the export/import format, see: + Alternatively, you may omit this flag to read from standard input. For + a schema describing the export/import format, see: $CLOUDSDKROOT/lib/googlecloudsdk/schemas/compute/beta/ForwardingRule.yaml. Note: $CLOUDSDKROOT represents the Google Cloud CLI's installation directory. diff --git a/gcloud/beta/compute/instances/update-from-file b/gcloud/beta/compute/instances/update-from-file index 65b4e1102..6360a0348 100644 --- a/gcloud/beta/compute/instances/update-from-file +++ b/gcloud/beta/compute/instances/update-from-file @@ -39,8 +39,8 @@ FLAGS --source=SOURCE Path to a YAML file containing configuration export data. - Alternatively, you may omit this flag to read from standard input.For a - schema describing the export/import format, see: + Alternatively, you may omit this flag to read from standard input. For + a schema describing the export/import format, see: $CLOUDSDKROOT/lib/googlecloudsdk/schemas/compute/beta/Instance.yaml. Note: $CLOUDSDKROOT represents the Google Cloud CLI's installation directory. diff --git a/gcloud/beta/compute/interconnects/attachments/dedicated/create b/gcloud/beta/compute/interconnects/attachments/dedicated/create index 74c419ce3..b847b468d 100644 --- a/gcloud/beta/compute/interconnects/attachments/dedicated/create +++ b/gcloud/beta/compute/interconnects/attachments/dedicated/create @@ -65,6 +65,8 @@ OPTIONAL FLAGS 50 Gbit/s 100g 100 Gbit/s + 400g + 400 Gbit/s --candidate-cloud-router-ip-address=CANDIDATE_CLOUD_ROUTER_IP_ADDRESS Single IPv4 address + prefix length to be configured on the cloud diff --git a/gcloud/beta/compute/interconnects/attachments/dedicated/update b/gcloud/beta/compute/interconnects/attachments/dedicated/update index bb005daac..a8906f080 100644 --- a/gcloud/beta/compute/interconnects/attachments/dedicated/update +++ b/gcloud/beta/compute/interconnects/attachments/dedicated/update @@ -55,6 +55,8 @@ FLAGS 50 Gbit/s 100g 100 Gbit/s + 400g + 400 Gbit/s --candidate-cloud-router-ipv6-address=CANDIDATE_CLOUD_ROUTER_IPV6_ADDRESS Single IPv6 address + prefix length to be configured on the cloud diff --git a/gcloud/beta/compute/network-firewall-policies/import-rules b/gcloud/beta/compute/network-firewall-policies/import-rules index 75735519f..86ce398f7 100644 --- a/gcloud/beta/compute/network-firewall-policies/import-rules +++ b/gcloud/beta/compute/network-firewall-policies/import-rules @@ -22,8 +22,8 @@ POSITIONAL ARGUMENTS FLAGS --source=SOURCE Path to a YAML file containing configuration export data. - Alternatively, you may omit this flag to read from standard input.For a - schema describing the export/import format, see: + Alternatively, you may omit this flag to read from standard input. For + a schema describing the export/import format, see: $CLOUDSDKROOT/lib/googlecloudsdk/schemas/compute/beta/FirewallPolicy.yaml. Note: $CLOUDSDKROOT represents the Google Cloud CLI's installation directory. diff --git a/gcloud/beta/compute/network-firewall-policies/rules/create b/gcloud/beta/compute/network-firewall-policies/rules/create index d88cc8beb..b1cc53233 100644 --- a/gcloud/beta/compute/network-firewall-policies/rules/create +++ b/gcloud/beta/compute/network-firewall-policies/rules/create @@ -8,6 +8,7 @@ SYNOPSIS --layer4-configs=[LAYER4_CONFIG,...] [--description=DESCRIPTION] [--dest-address-groups=[DEST_ADDRESS_GROUPS,...]] [--dest-fqdns=[DEST_FQDNS,...]] [--dest-ip-ranges=[DEST_IP_RANGE,...]] + [--dest-network-context=DEST_NETWORK_CONTEXT] [--dest-network-type=DEST_NETWORK_TYPE] [--dest-region-codes=[DEST_REGION_CODES,...]] [--dest-threat-intelligence=[DEST_THREAT_INTELLIGENCE_LISTS,...]] @@ -15,6 +16,7 @@ SYNOPSIS [--security-profile-group=SECURITY_PROFILE_GROUP] [--src-address-groups=[SOURCE_ADDRESS_GROUPS,...]] [--src-fqdns=[SOURCE_FQDNS,...]] [--src-ip-ranges=[SRC_IP_RANGE,...]] + [--src-network-context=SRC_NETWORK_CONTEXT] [--src-network-type=SRC_NETWORK_TYPE] [--src-networks=[SRC_NETWORKS,...]] [--src-region-codes=[SOURCE_REGION_CODES,...]] @@ -78,6 +80,12 @@ OPTIONAL FLAGS --dest-ip-ranges=[DEST_IP_RANGE,...] Destination IP ranges to match for this rule. + --dest-network-context=DEST_NETWORK_CONTEXT + Use this flag to indicate that the rule should match internet or + non-internet traffic. It applies to destination traffic for egress + rules. Valid values are INTERNET and NON_INTERNET. Use empty string to + clear the field. + --dest-network-type=DEST_NETWORK_TYPE Use this flag to indicate that the rule should match internet or non-internet traffic. It applies to destination traffic for egress @@ -132,6 +140,13 @@ OPTIONAL FLAGS --src-secure-tags.Multiple IP address blocks can be specified if they are separated by commas. + --src-network-context=SRC_NETWORK_CONTEXT + Use this flag to indicate that the rule should match internet, + non-internet traffic or traffic coming from the network specified by + --src-networks. It applies to ingress rules. Valid values are INTERNET, + NON_INTERNET, VPC_NETWORKS and INTRA_VPC. Use empty string to clear the + field. + --src-network-type=SRC_NETWORK_TYPE Use this flag to indicate that the rule should match internet, non-internet traffic or traffic coming from the network specified by diff --git a/gcloud/beta/compute/network-firewall-policies/rules/update b/gcloud/beta/compute/network-firewall-policies/rules/update index 7979a0499..5326f514c 100644 --- a/gcloud/beta/compute/network-firewall-policies/rules/update +++ b/gcloud/beta/compute/network-firewall-policies/rules/update @@ -8,6 +8,7 @@ SYNOPSIS [--description=DESCRIPTION] [--dest-address-groups=[DEST_ADDRESS_GROUPS,...]] [--dest-fqdns=[DEST_FQDNS,...]] [--dest-ip-ranges=[DEST_IP_RANGE,...]] + [--dest-network-context=DEST_NETWORK_CONTEXT] [--dest-network-type=DEST_NETWORK_TYPE] [--dest-region-codes=[DEST_REGION_CODES,...]] [--dest-threat-intelligence=[DEST_THREAT_INTELLIGENCE_LISTS,...]] @@ -16,6 +17,7 @@ SYNOPSIS [--security-profile-group=SECURITY_PROFILE_GROUP] [--src-address-groups=[SOURCE_ADDRESS_GROUPS,...]] [--src-fqdns=[SOURCE_FQDNS,...]] [--src-ip-ranges=[SRC_IP_RANGE,...]] + [--src-network-context=SRC_NETWORK_CONTEXT] [--src-network-type=SRC_NETWORK_TYPE] [--src-networks=[SRC_NETWORKS,...]] [--src-region-codes=[SOURCE_REGION_CODES,...]] @@ -68,6 +70,12 @@ OPTIONAL FLAGS --dest-ip-ranges=[DEST_IP_RANGE,...] Destination IP ranges to match for this rule. + --dest-network-context=DEST_NETWORK_CONTEXT + Use this flag to indicate that the rule should match internet or + non-internet traffic. It applies to destination traffic for egress + rules. Valid values are INTERNET and NON_INTERNET. Use empty string to + clear the field. + --dest-network-type=DEST_NETWORK_TYPE Use this flag to indicate that the rule should match internet or non-internet traffic. It applies to destination traffic for egress @@ -129,6 +137,13 @@ OPTIONAL FLAGS --src-secure-tags.Multiple IP address blocks can be specified if they are separated by commas. + --src-network-context=SRC_NETWORK_CONTEXT + Use this flag to indicate that the rule should match internet, + non-internet traffic or traffic coming from the network specified by + --src-networks. It applies to ingress rules. Valid values are INTERNET, + NON_INTERNET, VPC_NETWORKS and INTRA_VPC. Use empty string to clear the + field. + --src-network-type=SRC_NETWORK_TYPE Use this flag to indicate that the rule should match internet, non-internet traffic or traffic coming from the network specified by diff --git a/gcloud/beta/compute/networks/peerings/cancel-request-delete b/gcloud/beta/compute/networks/peerings/cancel-request-delete new file mode 100644 index 000000000..cfb85ba2d --- /dev/null +++ b/gcloud/beta/compute/networks/peerings/cancel-request-delete @@ -0,0 +1,51 @@ +NAME + gcloud beta compute networks peerings cancel-request-delete - cancel + deletion request of a Compute Engine network peering + +SYNOPSIS + gcloud beta compute networks peerings cancel-request-delete NAME + --network=NETWORK [--async] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) gcloud beta compute networks peerings cancel-request-delete is used + to cancel a pending request to delete a consensus peering between two + networks. + +EXAMPLES + To cancel a request to delete a consensus peering with the name + 'peering-name' between the network 'local-network' and the network + 'peer-network', run: + + $ gcloud beta compute networks peerings cancel-request-delete \ + peering-name --network=local-network + + $ gcloud beta compute networks peerings cancel-request-delete \ + peering-name --network=peer-network + +POSITIONAL ARGUMENTS + NAME + The name of the peering. + +REQUIRED FLAGS + --network=NETWORK + The name of the network in the current project containing the peering. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha compute networks peerings cancel-request-delete + diff --git a/gcloud/beta/compute/networks/peerings/help b/gcloud/beta/compute/networks/peerings/help index 06ef355ea..e3ba7bf8a 100644 --- a/gcloud/beta/compute/networks/peerings/help +++ b/gcloud/beta/compute/networks/peerings/help @@ -22,6 +22,9 @@ GCLOUD WIDE FLAGS COMMANDS COMMAND is one of the following: + cancel-request-delete + (BETA) Cancel deletion request of a Compute Engine network peering. + create (BETA) Create a Compute Engine network peering. diff --git a/gcloud/beta/compute/project-info/help b/gcloud/beta/compute/project-info/help index 560e536f5..afb0246da 100644 --- a/gcloud/beta/compute/project-info/help +++ b/gcloud/beta/compute/project-info/help @@ -39,7 +39,7 @@ COMMANDS (BETA) Remove project-wide metadata entries. set-usage-bucket - (BETA) Set usage reporting bucket for a project. + (BETA) (DEPRECATED) Set usage reporting bucket for a project. update (BETA) Update a Compute Engine project resource. diff --git a/gcloud/beta/compute/project-info/set-usage-bucket b/gcloud/beta/compute/project-info/set-usage-bucket index bd904b668..ac669129b 100644 --- a/gcloud/beta/compute/project-info/set-usage-bucket +++ b/gcloud/beta/compute/project-info/set-usage-bucket @@ -8,7 +8,12 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) gcloud beta compute project-info set-usage-bucket configures usage + (BETA) (DEPRECATED) Set usage reporting bucket for a project. + + This command is deprecated. Please onboard with BigQuery Export instead. + https://docs.cloud.google.com/billing/docs/how-to/export-data-bigquery + + gcloud beta compute project-info set-usage-bucket configures usage reporting for projects. Setting usage reporting will cause a log of usage per resource to be diff --git a/gcloud/beta/compute/resource-policies/create/group-placement b/gcloud/beta/compute/resource-policies/create/group-placement index 02627c9c5..03e9ec5fe 100644 --- a/gcloud/beta/compute/resource-policies/create/group-placement +++ b/gcloud/beta/compute/resource-policies/create/group-placement @@ -4,6 +4,7 @@ NAME SYNOPSIS gcloud beta compute resource-policies create group-placement NAME + [--accelerator-topology-mode=ACCELERATOR_TOPOLOGY_MODE] [--availability-domain-count=AVAILABILITY_DOMAIN_COUNT] [--collocation=COLLOCATION] [--description=DESCRIPTION] [--gpu-topology=GPU_TOPOLOGY] [--max-distance=MAX_DISTANCE] @@ -22,6 +23,16 @@ POSITIONAL ARGUMENTS Name of the resource policy to operate on. FLAGS + --accelerator-topology-mode=ACCELERATOR_TOPOLOGY_MODE + Defines the accelerator connection strategy for accelerator machine + types like TPUs. ACCELERATOR_TOPOLOGY_MODE must be one of: + + AUTO_CONNECT + This creates a static, pre-formed accelerator topology. + PROVISION_ONLY + The interconnected chips are connected on demand. At the time of VM + creation, the chips are not connected. + --availability-domain-count=AVAILABILITY_DOMAIN_COUNT Number of availability domain in the group placement policy. diff --git a/gcloud/beta/compute/resource-policies/create/workload-policy b/gcloud/beta/compute/resource-policies/create/workload-policy index 8b1730ec9..a54e7f935 100644 --- a/gcloud/beta/compute/resource-policies/create/workload-policy +++ b/gcloud/beta/compute/resource-policies/create/workload-policy @@ -4,7 +4,8 @@ NAME SYNOPSIS gcloud beta compute resource-policies create workload-policy NAME - --type=TYPE [--description=DESCRIPTION] [--region=REGION] + --type=TYPE [--accelerator-topology-mode=ACCELERATOR_TOPOLOGY_MODE] + [--description=DESCRIPTION] [--region=REGION] [--accelerator-topology=ACCELERATOR_TOPOLOGY | --max-topology-distance=MAX_TOPOLOGY_DISTANCE] [GCLOUD_WIDE_FLAG ...] @@ -38,6 +39,16 @@ REQUIRED FLAGS latency between VMs. OPTIONAL FLAGS + --accelerator-topology-mode=ACCELERATOR_TOPOLOGY_MODE + Defines the accelerator connection strategy for accelerator machine + types like TPUs. ACCELERATOR_TOPOLOGY_MODE must be one of: + + AUTO_CONNECT + This creates a static, pre-formed accelerator topology. + PROVISION_ONLY + The interconnected chips are connected on demand. At the time of VM + creation, the chips are not connected. + --description=DESCRIPTION An optional, textual description for the backend. diff --git a/gcloud/beta/compute/target-http-proxies/import b/gcloud/beta/compute/target-http-proxies/import index 25db59e2d..a6373d20d 100644 --- a/gcloud/beta/compute/target-http-proxies/import +++ b/gcloud/beta/compute/target-http-proxies/import @@ -21,8 +21,8 @@ POSITIONAL ARGUMENTS FLAGS --source=SOURCE Path to a YAML file containing configuration export data. - Alternatively, you may omit this flag to read from standard input.For a - schema describing the export/import format, see: + Alternatively, you may omit this flag to read from standard input. For + a schema describing the export/import format, see: $CLOUDSDKROOT/lib/googlecloudsdk/schemas/compute/beta/TargetHttpProxy.yaml. Note: $CLOUDSDKROOT represents the Google Cloud CLI's installation directory. diff --git a/gcloud/beta/compute/target-https-proxies/import b/gcloud/beta/compute/target-https-proxies/import index 476738d3a..af8226987 100644 --- a/gcloud/beta/compute/target-https-proxies/import +++ b/gcloud/beta/compute/target-https-proxies/import @@ -27,8 +27,8 @@ POSITIONAL ARGUMENTS FLAGS --source=SOURCE Path to a YAML file containing configuration export data. - Alternatively, you may omit this flag to read from standard input.For a - schema describing the export/import format, see: + Alternatively, you may omit this flag to read from standard input. For + a schema describing the export/import format, see: $CLOUDSDKROOT/lib/googlecloudsdk/schemas/compute/beta/TargetHttpsProxy.yaml. Note: $CLOUDSDKROOT represents the Google Cloud CLI's installation directory. diff --git a/gcloud/beta/compute/url-maps/import b/gcloud/beta/compute/url-maps/import index ccbbee7d1..f62dafb64 100644 --- a/gcloud/beta/compute/url-maps/import +++ b/gcloud/beta/compute/url-maps/import @@ -20,8 +20,8 @@ POSITIONAL ARGUMENTS FLAGS --source=SOURCE Path to a YAML file containing configuration export data. - Alternatively, you may omit this flag to read from standard input.For a - schema describing the export/import format, see: + Alternatively, you may omit this flag to read from standard input. For + a schema describing the export/import format, see: $CLOUDSDKROOT/lib/googlecloudsdk/schemas/compute/beta/UrlMap.yaml. Note: $CLOUDSDKROOT represents the Google Cloud CLI's installation directory. diff --git a/gcloud/beta/config/get b/gcloud/beta/config/get index c7acdd24b..425772f0b 100644 --- a/gcloud/beta/config/get +++ b/gcloud/beta/config/get @@ -232,6 +232,10 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud certificate-manager command group. Defaults to https://certificatemanager.googleapis.com/ + cloudapiregistry + Overrides API endpoint for gcloud api-registry command group. + Defaults to https://cloudapiregistry.googleapis.com/ + cloudasset Overrides API endpoint for gcloud asset command group. Defaults to https://cloudasset.googleapis.com/ diff --git a/gcloud/beta/config/help b/gcloud/beta/config/help index f4f5050e5..8cea1e944 100644 --- a/gcloud/beta/config/help +++ b/gcloud/beta/config/help @@ -264,6 +264,10 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud certificate-manager command group. Defaults to https://certificatemanager.googleapis.com/ + cloudapiregistry + Overrides API endpoint for gcloud api-registry command group. + Defaults to https://cloudapiregistry.googleapis.com/ + cloudasset Overrides API endpoint for gcloud asset command group. Defaults to https://cloudasset.googleapis.com/ diff --git a/gcloud/beta/config/list b/gcloud/beta/config/list index 96c483d4a..53fbe4020 100644 --- a/gcloud/beta/config/list +++ b/gcloud/beta/config/list @@ -276,6 +276,10 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud certificate-manager command group. Defaults to https://certificatemanager.googleapis.com/ + cloudapiregistry + Overrides API endpoint for gcloud api-registry command group. + Defaults to https://cloudapiregistry.googleapis.com/ + cloudasset Overrides API endpoint for gcloud asset command group. Defaults to https://cloudasset.googleapis.com/ diff --git a/gcloud/beta/config/set b/gcloud/beta/config/set index 26ed3dbe4..39948ba39 100644 --- a/gcloud/beta/config/set +++ b/gcloud/beta/config/set @@ -279,6 +279,10 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud certificate-manager command group. Defaults to https://certificatemanager.googleapis.com/ + cloudapiregistry + Overrides API endpoint for gcloud api-registry command group. + Defaults to https://cloudapiregistry.googleapis.com/ + cloudasset Overrides API endpoint for gcloud asset command group. Defaults to https://cloudasset.googleapis.com/ diff --git a/gcloud/beta/config/unset b/gcloud/beta/config/unset index d8dded572..7b2f1723c 100644 --- a/gcloud/beta/config/unset +++ b/gcloud/beta/config/unset @@ -240,6 +240,10 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud certificate-manager command group. Defaults to https://certificatemanager.googleapis.com/ + cloudapiregistry + Overrides API endpoint for gcloud api-registry command group. + Defaults to https://cloudapiregistry.googleapis.com/ + cloudasset Overrides API endpoint for gcloud asset command group. Defaults to https://cloudasset.googleapis.com/ diff --git a/gcloud/beta/container/clusters/create b/gcloud/beta/container/clusters/create index 697213b11..f4e07ee6d 100644 --- a/gcloud/beta/container/clusters/create +++ b/gcloud/beta/container/clusters/create @@ -66,6 +66,7 @@ SYNOPSIS [--local-ssd-encryption-mode=LOCAL_SSD_ENCRYPTION_MODE] [--logging=[COMPONENT,...]] [--logging-variant=LOGGING_VARIANT] [--machine-type=MACHINE_TYPE, -m MACHINE_TYPE] + [--managed-otel-scope=MANAGED_OTEL_SCOPE] [--max-nodes-per-pool=MAX_NODES_PER_POOL] [--max-pods-per-node=MAX_PODS_PER_NODE] [--max-surge-upgrade=MAX_SURGE_UPGRADE; default=1] @@ -231,7 +232,7 @@ FLAGS KubernetesDashboard, NetworkPolicy, NodeLocalDNS, ConfigConnector, GcePersistentDiskCsiDriver, GcpFilestoreCsiDriver, BackupRestore, GcsFuseCsiDriver, ParallelstoreCsiDriver, HighScaleCheckpointing, - LustreCsiDriver, RayOperator, Istio, CloudRun. + LustreCsiDriver, RayOperator, SlurmOperator, Istio, CloudRun. --allow-route-overlap Allows the provided cluster CIDRs to overlap with existing routes that @@ -400,7 +401,7 @@ FLAGS --confidential-node-type=CONFIDENTIAL_NODE_TYPE Enable confidential nodes for the cluster. Enabling Confidential Nodes will create nodes using Confidential VM - https://cloud.google.com/compute/confidential-vm/docs/about-cvm. + https://docs.cloud.google.com/compute/docs/about-confidential-vm. CONFIDENTIAL_NODE_TYPE must be one of: sev, sev_snp, tdx. --containerd-config-from-file=PATH_TO_FILE @@ -585,7 +586,7 @@ FLAGS --enable-confidential-nodes Enable confidential nodes for the cluster. Enabling Confidential Nodes will create nodes using Confidential VM - https://cloud.google.com/compute/confidential-vm/docs/about-cvm. + https://docs.cloud.google.com/compute/docs/about-confidential-vm. --enable-confidential-storage Enable confidential storage for the cluster. Enabling Confidential @@ -962,6 +963,17 @@ FLAGS $ gcloud beta container clusters create high-mem-pool \ --machine-type=custom-2-12288 + --managed-otel-scope=MANAGED_OTEL_SCOPE + Specifies the scope of Managed OpenTelemetry within the cluster. + + COLLECTION_AND_INSTRUMENTATION_COMPONENTS: Enables GKE Managed + OpenTelemetry Collector and other Instrumentations components like + Instrumentation CRD within the cluster. NONE: Disables the GKE Managed + OpenTelemetry. + + MANAGED_OTEL_SCOPE must be one of: + COLLECTION_AND_INSTRUMENTATION_COMPONENTS, NONE. + --max-nodes-per-pool=MAX_NODES_PER_POOL The maximum number of nodes to allocate per default initial node pool. Kubernetes Engine will automatically create enough nodes pools such @@ -1697,7 +1709,10 @@ FLAGS [65536, 2147483647] vm.overcommit_memory Must be one of {0, - 1, 2} + 1, 2}. Not + supported on + machines with less + than 15 GB memory. vm.overcommit_ratio Must be between [0, 100] vm.vfs_cache_pressure Must be between @@ -1755,9 +1770,15 @@ FLAGS KEY VALUE diskCount integer - Allocated hugepage size should not exceed 60% of available memory on - the node. For example, c2d-highcpu-4 has 8GB memory, total allocated - hugepage of 2m and 1g should not exceed 8GB * 0.6 = 4.8GB. + The upper limit for total allocated hugepage size differs based upon + machine size. + + ◆ On machines with less than 30 GB memory: 60% of the total memory. + For example, on e2-standard-2 machine with 8 GB of memory, you can't + allocate more than 4.8 GB for hugepages. + ◆ On machines with more than 30 GB memory: 80% of the total memory. + For example, on c4a-standard-8 machines with 32 GB of memory, + hugepages cannot exceed 25.6 GB. 1G hugepages are only available in following machine familes: c3, m2, c2d, c3d, h3, m3, a2, a3, g2. diff --git a/gcloud/beta/container/clusters/create-auto b/gcloud/beta/container/clusters/create-auto index c9083279e..db5a1f6cf 100644 --- a/gcloud/beta/container/clusters/create-auto +++ b/gcloud/beta/container/clusters/create-auto @@ -30,13 +30,13 @@ SYNOPSIS [--enable-ray-cluster-logging] [--enable-ray-cluster-monitoring] [--enable-ray-operator] [--fleet-project=PROJECT_ID_OR_NUMBER] [--hpa-profile=HPA_PROFILE] [--labels=[KEY=VALUE,...]] - [--logging=[COMPONENT,...]] [--membership-type=MEMBERSHIP_TYPE] - [--monitoring=[COMPONENT,...]] [--network=NETWORK] - [--private-endpoint-subnetwork=NAME] [--release-channel=CHANNEL] - [--security-group=SECURITY_GROUP] [--security-posture=SECURITY_POSTURE] - [--services-ipv4-cidr=CIDR] [--services-secondary-range-name=NAME] - [--subnetwork=SUBNETWORK] [--tier=TIER] - [--workload-policies=WORKLOAD_POLICIES] + [--logging=[COMPONENT,...]] [--managed-otel-scope=MANAGED_OTEL_SCOPE] + [--membership-type=MEMBERSHIP_TYPE] [--monitoring=[COMPONENT,...]] + [--network=NETWORK] [--private-endpoint-subnetwork=NAME] + [--release-channel=CHANNEL] [--security-group=SECURITY_GROUP] + [--security-posture=SECURITY_POSTURE] [--services-ipv4-cidr=CIDR] + [--services-secondary-range-name=NAME] [--subnetwork=SUBNETWORK] + [--tier=TIER] [--workload-policies=WORKLOAD_POLICIES] [--workload-vulnerability-scanning=WORKLOAD_VULNERABILITY_SCANNING] [--additive-vpc-scope-dns-domain=ADDITIVE_VPC_SCOPE_DNS_DOMAIN | --disable-additive-vpc-scope] @@ -286,7 +286,7 @@ FLAGS --enable-confidential-nodes Enable confidential nodes for the cluster. Enabling Confidential Nodes will create nodes using Confidential VM - https://cloud.google.com/compute/confidential-vm/docs/about-cvm. + https://docs.cloud.google.com/compute/docs/about-confidential-vm. --enable-default-compute-class Enable the default compute class to use for the cluster. @@ -408,6 +408,17 @@ FLAGS --logging=SYSTEM,WORKLOAD,API_SERVER,CONTROLLER_MANAGER,\ SCHEDULER + --managed-otel-scope=MANAGED_OTEL_SCOPE + Specifies the scope of Managed OpenTelemetry within the cluster. + + COLLECTION_AND_INSTRUMENTATION_COMPONENTS: Enables GKE Managed + OpenTelemetry Collector and other Instrumentations components like + Instrumentation CRD within the cluster. NONE: Disables the GKE Managed + OpenTelemetry. + + MANAGED_OTEL_SCOPE must be one of: + COLLECTION_AND_INSTRUMENTATION_COMPONENTS, NONE. + --membership-type=MEMBERSHIP_TYPE Specify a membership type for the cluster's fleet membership. Example: $ gcloud beta container clusters create-auto \ diff --git a/gcloud/beta/container/clusters/update b/gcloud/beta/container/clusters/update index 80e8ed918..e23e4c082 100644 --- a/gcloud/beta/container/clusters/update +++ b/gcloud/beta/container/clusters/update @@ -62,7 +62,7 @@ SYNOPSIS --remove-additional-pod-ipv4-ranges=NAME,[NAME,...] | --additional-zones=[ZONE,...] | --node-locations=ZONE,[ZONE,...] | --auto-monitoring-scope=AUTO_MONITORING_SCOPE - --logging=[COMPONENT,...] + --logging=[COMPONENT,...] --managed-otel-scope=MANAGED_OTEL_SCOPE --monitoring=[COMPONENT,...] --disable-managed-prometheus | --enable-managed-prometheus | --binauthz-policy-bindings=[name=BINAUTHZ_POLICY] @@ -996,6 +996,17 @@ REQUIRED FLAGS --logging=SYSTEM,API_SERVER,WORKLOAD $ gcloud beta container clusters update --logging=NONE + --managed-otel-scope=MANAGED_OTEL_SCOPE + Specifies the scope of Managed OpenTelemetry within the cluster. + + COLLECTION_AND_INSTRUMENTATION_COMPONENTS: Enables GKE Managed + OpenTelemetry Collector and other Instrumentations components like + Instrumentation CRD within the cluster. NONE: Disables the GKE + Managed OpenTelemetry. + + MANAGED_OTEL_SCOPE must be one of: + COLLECTION_AND_INSTRUMENTATION_COMPONENTS, NONE. + --monitoring=[COMPONENT,...] Set the components that have monitoring enabled. Valid component values are: SYSTEM, WORKLOAD (Deprecated), NONE, API_SERVER, diff --git a/gcloud/beta/container/node-pools/create b/gcloud/beta/container/node-pools/create index 7189d33d0..a1d2bd8f3 100644 --- a/gcloud/beta/container/node-pools/create +++ b/gcloud/beta/container/node-pools/create @@ -78,6 +78,9 @@ SYNOPSIS | --local-nvme-ssd-block[=[count=COUNT]] | --local-ssd-count=LOCAL_SSD_COUNT] [--location=LOCATION | --region=REGION | --zone=ZONE, -z ZONE] + [--node-drain-grace-period-seconds=NODE_DRAIN_GRACE_PERIOD_SECONDS + --node-drain-pdb-timeout-seconds=NODE_DRAIN_PDB_TIMEOUT_SECONDS + --respect-pdb-during-node-pool-deletion] [--reservation=RESERVATION --reservation-affinity=RESERVATION_AFFINITY] [--scopes=[SCOPE,...]; default="gke-default" --service-account=SERVICE_ACCOUNT] @@ -233,7 +236,7 @@ FLAGS --confidential-node-type=CONFIDENTIAL_NODE_TYPE Enable confidential nodes for the node pool. Enabling Confidential Nodes will create nodes using Confidential VM - https://cloud.google.com/compute/confidential-vm/docs/about-cvm. + https://docs.cloud.google.com/compute/docs/about-confidential-vm. CONFIDENTIAL_NODE_TYPE must be one of: sev, sev_snp, tdx, disabled. --containerd-config-from-file=PATH_TO_FILE @@ -305,7 +308,7 @@ FLAGS --enable-confidential-nodes Enable confidential nodes for the node pool. Enabling Confidential Nodes will create nodes using Confidential VM - https://cloud.google.com/compute/confidential-vm/docs/about-cvm. + https://docs.cloud.google.com/compute/docs/about-confidential-vm. --enable-confidential-storage Enable confidential storage for the node pool. Enabling Confidential @@ -1085,7 +1088,10 @@ FLAGS [65536, 2147483647] vm.overcommit_memory Must be one of {0, - 1, 2} + 1, 2}. Not + supported on + machines with less + than 15 GB memory. vm.overcommit_ratio Must be between [0, 100] vm.vfs_cache_pressure Must be between @@ -1143,9 +1149,15 @@ FLAGS KEY VALUE diskCount integer - Allocated hugepage size should not exceed 60% of available memory on - the node. For example, c2d-highcpu-4 has 8GB memory, total allocated - hugepage of 2m and 1g should not exceed 8GB * 0.6 = 4.8GB. + The upper limit for total allocated hugepage size differs based upon + machine size. + + ◆ On machines with less than 30 GB memory: 60% of the total memory. + For example, on e2-standard-2 machine with 8 GB of memory, you can't + allocate more than 4.8 GB for hugepages. + ◆ On machines with more than 30 GB memory: 80% of the total memory. + For example, on c4a-standard-8 machines with 32 GB of memory, + hugepages cannot exceed 25.6 GB. 1G hugepages are only available in following machine familes: c3, m2, c2d, c3d, h3, m3, a2, a3, g2. @@ -1470,6 +1482,18 @@ FLAGS Compute zone (e.g. us-central1-a) for a zonal cluster. Overrides the default compute/zone property value for this command invocation. + Node drain settings + + --node-drain-grace-period-seconds=NODE_DRAIN_GRACE_PERIOD_SECONDS + The grace period in seconds for nodes to drain before being + forcefully removed. + + --node-drain-pdb-timeout-seconds=NODE_DRAIN_PDB_TIMEOUT_SECONDS + The timeout in seconds for the node pool to be drained. + + --respect-pdb-during-node-pool-deletion + Whether to respect PDBs when deleting nodes in the node pool. + Specifies the reservation for the node pool. --reservation=RESERVATION diff --git a/gcloud/beta/container/node-pools/update b/gcloud/beta/container/node-pools/update index 526dd2aeb..e9e3c8a61 100644 --- a/gcloud/beta/container/node-pools/update +++ b/gcloud/beta/container/node-pools/update @@ -37,7 +37,10 @@ SYNOPSIS --location-policy=LOCATION_POLICY --max-nodes=MAX_NODES --min-nodes=MIN_NODES --total-max-nodes=TOTAL_MAX_NODES --total-min-nodes=TOTAL_MIN_NODES - | --enable-autorepair --enable-autoupgrade) [--async] + | --enable-autorepair --enable-autoupgrade + | --node-drain-grace-period-seconds=NODE_DRAIN_GRACE_PERIOD_SECONDS + --node-drain-pdb-timeout-seconds=NODE_DRAIN_PDB_TIMEOUT_SECONDS + --respect-pdb-during-node-pool-deletion) [--async] [--cluster=CLUSTER] [--location=LOCATION | --region=REGION | --zone=ZONE, -z ZONE] [GCLOUD_WIDE_FLAG ...] @@ -104,7 +107,7 @@ REQUIRED FLAGS --confidential-node-type=CONFIDENTIAL_NODE_TYPE Recreate all the nodes in the node pool to be confidential VM - https://cloud.google.com/compute/confidential-vm/docs/about-cvm. + https://docs.cloud.google.com/compute/docs/about-confidential-vm. CONFIDENTIAL_NODE_TYPE must be one of: sev, sev_snp, tdx, disabled. --containerd-config-from-file=PATH_TO_FILE @@ -123,7 +126,7 @@ REQUIRED FLAGS --enable-confidential-nodes Recreate all the nodes in the node pool to be confidential VM - https://cloud.google.com/compute/confidential-vm/docs/about-cvm. + https://docs.cloud.google.com/compute/docs/about-confidential-vm. --enable-gvnic Enable the use of GVNIC for this cluster. Requires re-creation of @@ -608,7 +611,11 @@ REQUIRED FLAGS [65536, 2147483647] vm.overcommit_memory Must be one of - {0, 1, 2} + {0, 1, 2}. Not + supported on + machines with + less than 15 GB + memory. vm.overcommit_ratio Must be between [0, 100] vm.vfs_cache_pressure Must be between @@ -666,9 +673,15 @@ REQUIRED FLAGS KEY VALUE diskCount integer - Allocated hugepage size should not exceed 60% of available memory on - the node. For example, c2d-highcpu-4 has 8GB memory, total allocated - hugepage of 2m and 1g should not exceed 8GB * 0.6 = 4.8GB. + The upper limit for total allocated hugepage size differs based upon + machine size. + + ▸ On machines with less than 30 GB memory: 60% of the total memory. + For example, on e2-standard-2 machine with 8 GB of memory, you + can't allocate more than 4.8 GB for hugepages. + ▸ On machines with more than 30 GB memory: 80% of the total memory. + For example, on c4a-standard-8 machines with 32 GB of memory, + hugepages cannot exceed 25.6 GB. 1G hugepages are only available in following machine familes: c3, m2, c2d, c3d, h3, m3, a2, a3, g2. @@ -982,6 +995,18 @@ REQUIRED FLAGS https://cloud.google.com/kubernetes-engine/docs/node-auto-upgrades for more info. + Node drain settings + + --node-drain-grace-period-seconds=NODE_DRAIN_GRACE_PERIOD_SECONDS + The grace period in seconds for nodes to drain before being + forcefully removed. + + --node-drain-pdb-timeout-seconds=NODE_DRAIN_PDB_TIMEOUT_SECONDS + The timeout in seconds for the node pool to be drained. + + --respect-pdb-during-node-pool-deletion + Whether to respect PDBs when deleting nodes in the node pool. + OPTIONAL FLAGS --async Return immediately, without waiting for the operation in progress to diff --git a/gcloud/beta/datastream/connection-profiles/create b/gcloud/beta/datastream/connection-profiles/create index 48dace09b..d00453674 100644 --- a/gcloud/beta/datastream/connection-profiles/create +++ b/gcloud/beta/datastream/connection-profiles/create @@ -14,7 +14,14 @@ SYNOPSIS | --oracle-secret-manager-stored-password=ORACLE_SECRET_MANAGER_STORED_PASSWORD) : --oracle-ca-certificate=ORACLE_CA_CERTIFICATE --oracle-server-certificate-distinguished-name=ORACLE_SERVER_CERTIFICATE_DISTINGUISHED_NAME] | [--mongodb-host-addresses=IPv4_ADDRESS_OR_HOSTNAME:PORT, [...] --mongodb-username=MONGODB_USERNAME (--mongodb-password=MONGODB_PASSWORD | --mongodb-prompt-for-password - | --mongodb-secret-manager-stored-password=MONGODB_SECRET_MANAGER_STORED_PASSWORD) (--mongodb-srv-connection-format | --mongodb-standard-connection-format) : --mongodb-direct-connection --mongodb-replica-set=MONGODB_REPLICA_SET --mongodb-ca-certificate=MONGODB_CA_CERTIFICATE --mongodb-tls] | [--mysql-hostname=MYSQL_HOSTNAME --mysql-port=MYSQL_PORT --mysql-username=MYSQL_USERNAME (--mysql-password=MYSQL_PASSWORD | --mysql-prompt-for-password | --mysql-secret-manager-stored-password=MYSQL_SECRET_MANAGER_STORED_PASSWORD) : --ca-certificate=CA_CERTIFICATE --client-certificate=CLIENT_CERTIFICATE --client-key=CLIENT_KEY] | [--postgresql-database=POSTGRESQL_DATABASE --postgresql-hostname=POSTGRESQL_HOSTNAME --postgresql-port=POSTGRESQL_PORT --postgresql-username=POSTGRESQL_USERNAME (--postgresql-password=POSTGRESQL_PASSWORD | --postgresql-prompt-for-password | --postgresql-secret-manager-stored-password=POSTGRESQL_SECRET_MANAGER_STORED_PASSWORD) : [--postgresql-ca-certificate=POSTGRESQL_CA_CERTIFICATE : --postgresql-server-certificate-hostname=POSTGRESQL_SERVER_CERTIFICATE_HOSTNAME --postgresql-client-certificate=POSTGRESQL_CLIENT_CERTIFICATE --postgresql-client-key=POSTGRESQL_CLIENT_KEY]] | --salesforce-domain=SALESFORCE_DOMAIN (--salesforce-oauth2-client-id=SALESFORCE_OAUTH2_CLIENT_ID (--salesforce-oauth2-client-secret=SALESFORCE_OAUTH2_CLIENT_SECRET | --salesforce-prompt-for-oauth2-client-secret | --salesforce-secret-manager-stored-oauth2-client-secret=SALESFORCE_SECRET_MANAGER_STORED_OAUTH2_CLIENT_SECRET) | --salesforce-username=SALESFORCE_USERNAME (--salesforce-password=SALESFORCE_PASSWORD | --salesforce-prompt-for-password | --salesforce-secret-manager-stored-password=SALESFORCE_SECRET_MANAGER_STORED_PASSWORD) (--salesforce-prompt-for-security-token | --salesforce-secret-manager-stored-security-token=SALESFORCE_SECRET_MANAGER_STORED_SECURITY_TOKEN | --salesforce-security-token=SALESFORCE_SECURITY_TOKEN)) | --sqlserver-database=SQLSERVER_DATABASE --sqlserver-hostname=SQLSERVER_HOSTNAME --sqlserver-port=SQLSERVER_PORT --sqlserver-username=SQLSERVER_USERNAME (--sqlserver-password=SQLSERVER_PASSWORD | --sqlserver-prompt-for-password | --sqlserver-secret-manager-stored-password=SQLSERVER_SECRET_MANAGER_STORED_PASSWORD)] + | --mongodb-secret-manager-stored-password=MONGODB_SECRET_MANAGER_STORED_PASSWORD) (--mongodb-srv-connection-format | --mongodb-standard-connection-format) : --mongodb-additional-options=[MONGODB_PROFILE_ADDITIONAL_OPTIONS, + ...] --mongodb-direct-connection + --mongodb-replica-set=MONGODB_REPLICA_SET + --mongodb-ca-certificate=MONGODB_CA_CERTIFICATE --mongodb-tls] + | [--mysql-hostname=MYSQL_HOSTNAME --mysql-port=MYSQL_PORT + --mysql-username=MYSQL_USERNAME (--mysql-password=MYSQL_PASSWORD + | --mysql-prompt-for-password + | --mysql-secret-manager-stored-password=MYSQL_SECRET_MANAGER_STORED_PASSWORD) : --ca-certificate=CA_CERTIFICATE --client-certificate=CLIENT_CERTIFICATE --client-key=CLIENT_KEY] | [--postgresql-database=POSTGRESQL_DATABASE --postgresql-hostname=POSTGRESQL_HOSTNAME --postgresql-port=POSTGRESQL_PORT --postgresql-username=POSTGRESQL_USERNAME (--postgresql-password=POSTGRESQL_PASSWORD | --postgresql-prompt-for-password | --postgresql-secret-manager-stored-password=POSTGRESQL_SECRET_MANAGER_STORED_PASSWORD) : [--postgresql-ca-certificate=POSTGRESQL_CA_CERTIFICATE : --postgresql-server-certificate-hostname=POSTGRESQL_SERVER_CERTIFICATE_HOSTNAME --postgresql-client-certificate=POSTGRESQL_CLIENT_CERTIFICATE --postgresql-client-key=POSTGRESQL_CLIENT_KEY]] | --salesforce-domain=SALESFORCE_DOMAIN (--salesforce-oauth2-client-id=SALESFORCE_OAUTH2_CLIENT_ID (--salesforce-oauth2-client-secret=SALESFORCE_OAUTH2_CLIENT_SECRET | --salesforce-prompt-for-oauth2-client-secret | --salesforce-secret-manager-stored-oauth2-client-secret=SALESFORCE_SECRET_MANAGER_STORED_OAUTH2_CLIENT_SECRET) | --salesforce-username=SALESFORCE_USERNAME (--salesforce-password=SALESFORCE_PASSWORD | --salesforce-prompt-for-password | --salesforce-secret-manager-stored-password=SALESFORCE_SECRET_MANAGER_STORED_PASSWORD) (--salesforce-prompt-for-security-token | --salesforce-secret-manager-stored-security-token=SALESFORCE_SECRET_MANAGER_STORED_SECURITY_TOKEN | --salesforce-security-token=SALESFORCE_SECURITY_TOKEN)) | --sqlserver-database=SQLSERVER_DATABASE --sqlserver-hostname=SQLSERVER_HOSTNAME --sqlserver-port=SQLSERVER_PORT --sqlserver-username=SQLSERVER_USERNAME (--sqlserver-password=SQLSERVER_PASSWORD | --sqlserver-prompt-for-password | --sqlserver-secret-manager-stored-password=SQLSERVER_SECRET_MANAGER_STORED_PASSWORD)] [--no-connectivity | --private-connection-name=PRIVATE_CONNECTION_NAME | --static-ip-connectivity | [--forward-ssh-hostname=FORWARD_SSH_HOSTNAME @@ -176,6 +183,9 @@ OPTIONAL FLAGS This flag argument must be specified if any of the other arguments in this group are specified. + --mongodb-additional-options=[MONGODB_PROFILE_ADDITIONAL_OPTIONS,...] + Specifies additional options for the MongoDB connection. + --mongodb-direct-connection Connect to the mongodb hosts directly and do not try to resolve any of the replicas from the replica set. diff --git a/gcloud/beta/datastream/connection-profiles/update b/gcloud/beta/datastream/connection-profiles/update index c0c8399cb..5d6e37755 100644 --- a/gcloud/beta/datastream/connection-profiles/update +++ b/gcloud/beta/datastream/connection-profiles/update @@ -11,8 +11,10 @@ SYNOPSIS --oracle-hostname=ORACLE_HOSTNAME --oracle-port=ORACLE_PORT --oracle-username=ORACLE_USERNAME --oracle-ca-certificate=ORACLE_CA_CERTIFICATE - --oracle-server-certificate-distinguished-name=ORACLE_SERVER_CERTIFICATE_DISTINGUISHED_NAME --oracle-password=ORACLE_PASSWORD | --oracle-prompt-for-password | --oracle-secret-manager-stored-password=ORACLE_SECRET_MANAGER_STORED_PASSWORD | --mongodb-direct-connection --mongodb-host-addresses=IPv4_ADDRESS_OR_HOSTNAME:PORT, - [...] --mongodb-replica-set=MONGODB_REPLICA_SET + --oracle-server-certificate-distinguished-name=ORACLE_SERVER_CERTIFICATE_DISTINGUISHED_NAME --oracle-password=ORACLE_PASSWORD | --oracle-prompt-for-password | --oracle-secret-manager-stored-password=ORACLE_SECRET_MANAGER_STORED_PASSWORD | --mongodb-additional-options=[MONGODB_PROFILE_ADDITIONAL_OPTIONS, + ...] --mongodb-direct-connection + --mongodb-host-addresses=IPv4_ADDRESS_OR_HOSTNAME:PORT,[...] + --mongodb-replica-set=MONGODB_REPLICA_SET --mongodb-username=MONGODB_USERNAME --mongodb-ca-certificate=MONGODB_CA_CERTIFICATE --mongodb-tls --mongodb-password=MONGODB_PASSWORD @@ -154,6 +156,9 @@ OPTIONAL FLAGS Path to secret manager, storing the password for the user used to connect to the database. + --mongodb-additional-options=[MONGODB_PROFILE_ADDITIONAL_OPTIONS,...] + Specifies additional options for the MongoDB connection. + --mongodb-direct-connection Connect to the mongodb hosts directly and do not try to resolve any of the replicas from the replica set. diff --git a/gcloud/beta/developer-connect/connections/create b/gcloud/beta/developer-connect/connections/create index ab113de48..d62c3dd0e 100644 --- a/gcloud/beta/developer-connect/connections/create +++ b/gcloud/beta/developer-connect/connections/create @@ -8,7 +8,7 @@ SYNOPSIS [--git-proxy-config-enabled] [--labels=[LABELS,...]] [--location=LOCATION] [--namespace=NAMESPACE] [--request-id=REQUEST_ID] [--secret=SECRET] [--validate-only] - [--bitbucket-cloud-config-authorizer-credential-user-token-secret-version=BITBUCKET_CLOUD_CONFIG_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --bitbucket-cloud-config-read-authorizer-credential-user-token-secret-version=BITBUCKET_CLOUD_CONFIG_READ_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --bitbucket-cloud-config-webhook-secret-version=BITBUCKET_CLOUD_CONFIG_WEBHOOK_SECRET_VERSION --bitbucket-cloud-config-workspace=BITBUCKET_CLOUD_CONFIG_WORKSPACE | [--bitbucket-data-center-config-authorizer-credential-user-token-secret-version=BITBUCKET_DATA_CENTER_CONFIG_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --bitbucket-data-center-config-host-uri=BITBUCKET_DATA_CENTER_CONFIG_HOST_URI --bitbucket-data-center-config-read-authorizer-credential-user-token-secret-version=BITBUCKET_DATA_CENTER_CONFIG_READ_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --bitbucket-data-center-config-webhook-secret-version=BITBUCKET_DATA_CENTER_CONFIG_WEBHOOK_SECRET_VERSION : --bitbucket-data-center-config-service-directory=BITBUCKET_DATA_CENTER_CONFIG_SERVICE_DIRECTORY --bitbucket-data-center-config-ssl-ca-certificate=BITBUCKET_DATA_CENTER_CONFIG_SSL_CA_CERTIFICATE] | [--github-config-app=GITHUB_CONFIG_APP : --github-config-app-installation-id=GITHUB_CONFIG_APP_INSTALLATION_ID --github-config-authorizer-credential-oauth-token-secret-version=GITHUB_CONFIG_AUTHORIZER_CREDENTIAL_OAUTH_TOKEN_SECRET_VERSION] | [--github-enterprise-config-host-uri=GITHUB_ENTERPRISE_CONFIG_HOST_URI : --github-enterprise-config-app-id=GITHUB_ENTERPRISE_CONFIG_APP_ID --github-enterprise-config-app-installation-id=GITHUB_ENTERPRISE_CONFIG_APP_INSTALLATION_ID --github-enterprise-config-private-key-secret-version=GITHUB_ENTERPRISE_CONFIG_PRIVATE_KEY_SECRET_VERSION --github-enterprise-config-service-directory=GITHUB_ENTERPRISE_CONFIG_SERVICE_DIRECTORY --github-enterprise-config-ssl-ca-certificate=GITHUB_ENTERPRISE_CONFIG_SSL_CA_CERTIFICATE --github-enterprise-config-webhook-secret-version=GITHUB_ENTERPRISE_CONFIG_WEBHOOK_SECRET_VERSION] | --gitlab-config-authorizer-credential-user-token-secret-version=GITLAB_CONFIG_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --gitlab-config-read-authorizer-credential-user-token-secret-version=GITLAB_CONFIG_READ_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --gitlab-config-webhook-secret-version=GITLAB_CONFIG_WEBHOOK_SECRET_VERSION | [--gitlab-enterprise-config-authorizer-credential-user-token-secret-version=GITLAB_ENTERPRISE_CONFIG_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --gitlab-enterprise-config-host-uri=GITLAB_ENTERPRISE_CONFIG_HOST_URI --gitlab-enterprise-config-read-authorizer-credential-user-token-secret-version=GITLAB_ENTERPRISE_CONFIG_READ_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --gitlab-enterprise-config-webhook-secret-version=GITLAB_ENTERPRISE_CONFIG_WEBHOOK_SECRET_VERSION : --gitlab-enterprise-config-service-directory=GITLAB_ENTERPRISE_CONFIG_SERVICE_DIRECTORY --gitlab-enterprise-config-ssl-ca-certificate=GITLAB_ENTERPRISE_CONFIG_SSL_CA_CERTIFICATE]] + [--bitbucket-cloud-config-authorizer-credential-user-token-secret-version=BITBUCKET_CLOUD_CONFIG_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --bitbucket-cloud-config-read-authorizer-credential-user-token-secret-version=BITBUCKET_CLOUD_CONFIG_READ_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --bitbucket-cloud-config-webhook-secret-version=BITBUCKET_CLOUD_CONFIG_WEBHOOK_SECRET_VERSION --bitbucket-cloud-config-workspace=BITBUCKET_CLOUD_CONFIG_WORKSPACE | [--bitbucket-data-center-config-authorizer-credential-user-token-secret-version=BITBUCKET_DATA_CENTER_CONFIG_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --bitbucket-data-center-config-host-uri=BITBUCKET_DATA_CENTER_CONFIG_HOST_URI --bitbucket-data-center-config-read-authorizer-credential-user-token-secret-version=BITBUCKET_DATA_CENTER_CONFIG_READ_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --bitbucket-data-center-config-webhook-secret-version=BITBUCKET_DATA_CENTER_CONFIG_WEBHOOK_SECRET_VERSION : --bitbucket-data-center-config-service-directory=BITBUCKET_DATA_CENTER_CONFIG_SERVICE_DIRECTORY --bitbucket-data-center-config-ssl-ca-certificate=BITBUCKET_DATA_CENTER_CONFIG_SSL_CA_CERTIFICATE] | [--github-config-app=GITHUB_CONFIG_APP : --github-config-app-installation-id=GITHUB_CONFIG_APP_INSTALLATION_ID --github-config-authorizer-credential-oauth-token-secret-version=GITHUB_CONFIG_AUTHORIZER_CREDENTIAL_OAUTH_TOKEN_SECRET_VERSION] | [--github-enterprise-config-host-uri=GITHUB_ENTERPRISE_CONFIG_HOST_URI : --github-enterprise-config-app-id=GITHUB_ENTERPRISE_CONFIG_APP_ID --github-enterprise-config-app-installation-id=GITHUB_ENTERPRISE_CONFIG_APP_INSTALLATION_ID --github-enterprise-config-private-key-secret-version=GITHUB_ENTERPRISE_CONFIG_PRIVATE_KEY_SECRET_VERSION --github-enterprise-config-service-directory=GITHUB_ENTERPRISE_CONFIG_SERVICE_DIRECTORY --github-enterprise-config-ssl-ca-certificate=GITHUB_ENTERPRISE_CONFIG_SSL_CA_CERTIFICATE --github-enterprise-config-webhook-secret-version=GITHUB_ENTERPRISE_CONFIG_WEBHOOK_SECRET_VERSION] | --gitlab-config-authorizer-credential-user-token-secret-version=GITLAB_CONFIG_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --gitlab-config-read-authorizer-credential-user-token-secret-version=GITLAB_CONFIG_READ_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --gitlab-config-webhook-secret-version=GITLAB_CONFIG_WEBHOOK_SECRET_VERSION | [--gitlab-enterprise-config-authorizer-credential-user-token-secret-version=GITLAB_ENTERPRISE_CONFIG_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --gitlab-enterprise-config-host-uri=GITLAB_ENTERPRISE_CONFIG_HOST_URI --gitlab-enterprise-config-read-authorizer-credential-user-token-secret-version=GITLAB_ENTERPRISE_CONFIG_READ_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --gitlab-enterprise-config-webhook-secret-version=GITLAB_ENTERPRISE_CONFIG_WEBHOOK_SECRET_VERSION : --gitlab-enterprise-config-service-directory=GITLAB_ENTERPRISE_CONFIG_SERVICE_DIRECTORY --gitlab-enterprise-config-ssl-ca-certificate=GITLAB_ENTERPRISE_CONFIG_SSL_CA_CERTIFICATE] | [--http-config-host-uri=HTTP_CONFIG_HOST_URI : --http-config-service-directory=HTTP_CONFIG_SERVICE_DIRECTORY --http-config-ssl-ca-certificate=HTTP_CONFIG_SSL_CA_CERTIFICATE --http-config-bearer-token-authentication-secret-version=HTTP_CONFIG_BEARER_TOKEN_AUTHENTICATION_SECRET_VERSION | [--http-config-basic-authentication-username=HTTP_CONFIG_BASIC_AUTHENTICATION_USERNAME : --http-config-basic-authentication-password-secret-version=HTTP_CONFIG_BASIC_AUTHENTICATION_PASSWORD_SECRET_VERSION]]] [(--crypto-key-config-reference=CRYPTO_KEY_CONFIG_REFERENCE : --key-ring=KEY_RING)] [GCLOUD_WIDE_FLAG ...] @@ -1019,6 +1019,142 @@ FLAGS SSL Certificate Authority certificate to use for requests to GitLab Enterprise instance. + Configuration for connections to an HTTP service provider. + + --http-config-host-uri=HTTP_CONFIG_HOST_URI + The service provider's https endpoint. + + This flag argument must be specified if any of the other arguments + in this group are specified. + + ServiceDirectoryConfig represents Service Directory configuration for + a connection. + + Service resource - The Service Directory service name. Format: + projects/{project}/locations/{location}/namespaces/{namespace}/services/{service}. + 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 --http-config-service-directory on the + command line with a fully specified name; + ◇ provide the argument --project on the command line; + ◇ set the property core/project. + + To set the location attribute: + ◇ provide the argument --http-config-service-directory on the + command line with a fully specified name; + ◇ provide the argument --location on the command line. + + To set the namespace attribute: + ◇ provide the argument --http-config-service-directory on the + command line with a fully specified name; + ◇ provide the argument --namespace on the command line. + + This must be specified. + + --http-config-service-directory=HTTP_CONFIG_SERVICE_DIRECTORY + ID of the service or fully qualified identifier for the + service. + + To set the service attribute: + ▹ provide the argument --http-config-service-directory on the + command line. + + --http-config-ssl-ca-certificate=HTTP_CONFIG_SSL_CA_CERTIFICATE + The SSL certificate to use for requests to the HTTP service + provider. + + Arguments for the authentication. + + At most one of these can be specified: + + Bearer token authentication with a token. + + Arguments for the token. + + SecretVersion resource - The token SecretManager secret version + to authenticate as. 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 + --http-config-bearer-token-authentication-secret-version on + the command line with a fully specified name; + ▪ provide the argument --project on the command line; + ▪ set the property core/project. + + To set the location attribute: + ▪ provide the argument + --http-config-bearer-token-authentication-secret-version on + the command line with a fully specified name; + ▪ provide the argument --location on the command line. + + To set the secret attribute: + ▪ provide the argument + --http-config-bearer-token-authentication-secret-version on + the command line with a fully specified name; + ▪ provide the argument --secret on the command line. This + resource can be one of the following types: + [developerconnect.projects.locations.secrets.versions, + developerconnect.projects.secrets.versions]. + + --http-config-bearer-token-authentication-secret-version=HTTP_CONFIG_BEARER_TOKEN_AUTHENTICATION_SECRET_VERSION + ID of the secretVersion or fully qualified identifier for + the secretVersion. + + To set the secret_version attribute: + ◆ provide the argument + --http-config-bearer-token-authentication-secret-version + on the command line. + + Basic authentication with username and password. + + --http-config-basic-authentication-username=HTTP_CONFIG_BASIC_AUTHENTICATION_USERNAME + The username to authenticate as. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + Arguments for the password. + + SecretVersion resource - The password SecretManager secret + version to authenticate as. 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 + --http-config-basic-authentication-password-secret-version on + the command line with a fully specified name; + ▪ provide the argument --project on the command line; + ▪ set the property core/project. + + To set the location attribute: + ▪ provide the argument + --http-config-basic-authentication-password-secret-version on + the command line with a fully specified name; + ▪ provide the argument --location on the command line. + + To set the secret attribute: + ▪ provide the argument + --http-config-basic-authentication-password-secret-version on + the command line with a fully specified name; + ▪ provide the argument --secret on the command line. This + resource can be one of the following types: + [developerconnect.projects.locations.secrets.versions, + developerconnect.projects.secrets.versions]. + + --http-config-basic-authentication-password-secret-version=HTTP_CONFIG_BASIC_AUTHENTICATION_PASSWORD_SECRET_VERSION + ID of the secretVersion or fully qualified identifier for + the secretVersion. + + To set the secret_version attribute: + ◆ provide the argument + --http-config-basic-authentication-password-secret-version + on the command line. + The crypto key configuration. This field is used by the Customer-managed encryption keys (CMEK) feature. diff --git a/gcloud/beta/developer-connect/connections/update b/gcloud/beta/developer-connect/connections/update index a36dab1cf..f97143591 100644 --- a/gcloud/beta/developer-connect/connections/update +++ b/gcloud/beta/developer-connect/connections/update @@ -10,7 +10,7 @@ SYNOPSIS [--annotations=[ANNOTATIONS,...] | --update-annotations=[UPDATE_ANNOTATIONS,...] --clear-annotations | --remove-annotations=REMOVE_ANNOTATIONS] - [--bitbucket-cloud-config-authorizer-credential-user-token-secret-version=BITBUCKET_CLOUD_CONFIG_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --bitbucket-cloud-config-read-authorizer-credential-user-token-secret-version=BITBUCKET_CLOUD_CONFIG_READ_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --bitbucket-cloud-config-workspace=BITBUCKET_CLOUD_CONFIG_WORKSPACE --clear-bitbucket-cloud-config | --bitbucket-data-center-config-authorizer-credential-user-token-secret-version=BITBUCKET_DATA_CENTER_CONFIG_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --bitbucket-data-center-config-host-uri=BITBUCKET_DATA_CENTER_CONFIG_HOST_URI --bitbucket-data-center-config-read-authorizer-credential-user-token-secret-version=BITBUCKET_DATA_CENTER_CONFIG_READ_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --bitbucket-data-center-config-service-directory=BITBUCKET_DATA_CENTER_CONFIG_SERVICE_DIRECTORY --bitbucket-data-center-config-ssl-ca-certificate=BITBUCKET_DATA_CENTER_CONFIG_SSL_CA_CERTIFICATE --clear-bitbucket-data-center-config | --clear-github-config --github-config-app-installation-id=GITHUB_CONFIG_APP_INSTALLATION_ID --github-config-authorizer-credential-oauth-token-secret-version=GITHUB_CONFIG_AUTHORIZER_CREDENTIAL_OAUTH_TOKEN_SECRET_VERSION | --clear-github-enterprise-config --github-enterprise-config-app-id=GITHUB_ENTERPRISE_CONFIG_APP_ID --github-enterprise-config-app-installation-id=GITHUB_ENTERPRISE_CONFIG_APP_INSTALLATION_ID --github-enterprise-config-host-uri=GITHUB_ENTERPRISE_CONFIG_HOST_URI --github-enterprise-config-service-directory=GITHUB_ENTERPRISE_CONFIG_SERVICE_DIRECTORY --github-enterprise-config-ssl-ca-certificate=GITHUB_ENTERPRISE_CONFIG_SSL_CA_CERTIFICATE --clear-github-enterprise-config-private-key-secret-version | --github-enterprise-config-private-key-secret-version=GITHUB_ENTERPRISE_CONFIG_PRIVATE_KEY_SECRET_VERSION --clear-github-enterprise-config-webhook-secret-version | --github-enterprise-config-webhook-secret-version=GITHUB_ENTERPRISE_CONFIG_WEBHOOK_SECRET_VERSION | --clear-gitlab-config --gitlab-config-authorizer-credential-user-token-secret-version=GITLAB_CONFIG_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --gitlab-config-read-authorizer-credential-user-token-secret-version=GITLAB_CONFIG_READ_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION | --clear-gitlab-enterprise-config --gitlab-enterprise-config-authorizer-credential-user-token-secret-version=GITLAB_ENTERPRISE_CONFIG_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --gitlab-enterprise-config-host-uri=GITLAB_ENTERPRISE_CONFIG_HOST_URI --gitlab-enterprise-config-read-authorizer-credential-user-token-secret-version=GITLAB_ENTERPRISE_CONFIG_READ_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --gitlab-enterprise-config-service-directory=GITLAB_ENTERPRISE_CONFIG_SERVICE_DIRECTORY --gitlab-enterprise-config-ssl-ca-certificate=GITLAB_ENTERPRISE_CONFIG_SSL_CA_CERTIFICATE] + [--bitbucket-cloud-config-authorizer-credential-user-token-secret-version=BITBUCKET_CLOUD_CONFIG_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --bitbucket-cloud-config-read-authorizer-credential-user-token-secret-version=BITBUCKET_CLOUD_CONFIG_READ_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --bitbucket-cloud-config-workspace=BITBUCKET_CLOUD_CONFIG_WORKSPACE --clear-bitbucket-cloud-config | --bitbucket-data-center-config-authorizer-credential-user-token-secret-version=BITBUCKET_DATA_CENTER_CONFIG_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --bitbucket-data-center-config-host-uri=BITBUCKET_DATA_CENTER_CONFIG_HOST_URI --bitbucket-data-center-config-read-authorizer-credential-user-token-secret-version=BITBUCKET_DATA_CENTER_CONFIG_READ_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --bitbucket-data-center-config-service-directory=BITBUCKET_DATA_CENTER_CONFIG_SERVICE_DIRECTORY --bitbucket-data-center-config-ssl-ca-certificate=BITBUCKET_DATA_CENTER_CONFIG_SSL_CA_CERTIFICATE --clear-bitbucket-data-center-config | --clear-github-config --github-config-app-installation-id=GITHUB_CONFIG_APP_INSTALLATION_ID --github-config-authorizer-credential-oauth-token-secret-version=GITHUB_CONFIG_AUTHORIZER_CREDENTIAL_OAUTH_TOKEN_SECRET_VERSION | --clear-github-enterprise-config --github-enterprise-config-app-id=GITHUB_ENTERPRISE_CONFIG_APP_ID --github-enterprise-config-app-installation-id=GITHUB_ENTERPRISE_CONFIG_APP_INSTALLATION_ID --github-enterprise-config-host-uri=GITHUB_ENTERPRISE_CONFIG_HOST_URI --github-enterprise-config-service-directory=GITHUB_ENTERPRISE_CONFIG_SERVICE_DIRECTORY --github-enterprise-config-ssl-ca-certificate=GITHUB_ENTERPRISE_CONFIG_SSL_CA_CERTIFICATE --clear-github-enterprise-config-private-key-secret-version | --github-enterprise-config-private-key-secret-version=GITHUB_ENTERPRISE_CONFIG_PRIVATE_KEY_SECRET_VERSION --clear-github-enterprise-config-webhook-secret-version | --github-enterprise-config-webhook-secret-version=GITHUB_ENTERPRISE_CONFIG_WEBHOOK_SECRET_VERSION | --clear-gitlab-config --gitlab-config-authorizer-credential-user-token-secret-version=GITLAB_CONFIG_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --gitlab-config-read-authorizer-credential-user-token-secret-version=GITLAB_CONFIG_READ_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION | --clear-gitlab-enterprise-config --gitlab-enterprise-config-authorizer-credential-user-token-secret-version=GITLAB_ENTERPRISE_CONFIG_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --gitlab-enterprise-config-host-uri=GITLAB_ENTERPRISE_CONFIG_HOST_URI --gitlab-enterprise-config-read-authorizer-credential-user-token-secret-version=GITLAB_ENTERPRISE_CONFIG_READ_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --gitlab-enterprise-config-service-directory=GITLAB_ENTERPRISE_CONFIG_SERVICE_DIRECTORY --gitlab-enterprise-config-ssl-ca-certificate=GITLAB_ENTERPRISE_CONFIG_SSL_CA_CERTIFICATE | --clear-http-config --http-config-service-directory=HTTP_CONFIG_SERVICE_DIRECTORY --http-config-ssl-ca-certificate=HTTP_CONFIG_SSL_CA_CERTIFICATE --clear-http-config-bearer-token-authentication-secret-version | --http-config-bearer-token-authentication-secret-version=HTTP_CONFIG_BEARER_TOKEN_AUTHENTICATION_SECRET_VERSION | --http-config-basic-authentication-username=HTTP_CONFIG_BASIC_AUTHENTICATION_USERNAME --clear-http-config-basic-authentication-password-secret-version | --http-config-basic-authentication-password-secret-version=HTTP_CONFIG_BASIC_AUTHENTICATION_PASSWORD_SECRET_VERSION] [--clear-crypto-key-config [--crypto-key-config-reference=CRYPTO_KEY_CONFIG_REFERENCE : --key-ring=KEY_RING]] @@ -868,6 +868,160 @@ FLAGS SSL Certificate Authority certificate to use for requests to GitLab Enterprise instance. + Configuration for connections to an HTTP service provider. + + --clear-http-config + Set connection.httpConfig back to default value. + + ServiceDirectoryConfig represents Service Directory configuration for + a connection. + + Service resource - The Service Directory service name. Format: + projects/{project}/locations/{location}/namespaces/{namespace}/services/{service}. + 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 --http-config-service-directory on the + command line with a fully specified name; + ◇ provide the argument --project on the command line; + ◇ set the property core/project. + + To set the location attribute: + ◇ provide the argument --http-config-service-directory on the + command line with a fully specified name; + ◇ provide the argument --location on the command line. + + To set the namespace attribute: + ◇ provide the argument --http-config-service-directory on the + command line with a fully specified name; + ◇ provide the argument --namespace on the command line. + + --http-config-service-directory=HTTP_CONFIG_SERVICE_DIRECTORY + ID of the service or fully qualified identifier for the + service. + + To set the service attribute: + ▹ provide the argument --http-config-service-directory on the + command line. + + --http-config-ssl-ca-certificate=HTTP_CONFIG_SSL_CA_CERTIFICATE + The SSL certificate to use for requests to the HTTP service + provider. + + Arguments for the authentication. + + At most one of these can be specified: + + Bearer token authentication with a token. + + Arguments for the token. + + Update http_config_bearer_token_authentication_secret_version. + + At most one of these can be specified: + + --clear-http-config-bearer-token-authentication-secret-version + Clear + http_config_bearer_token_authentication_secret_version + value and set to null. + + SecretVersion resource - Set + http_config_bearer_token_authentication_secret_version to new + value. + + The token SecretManager secret version to authenticate as. + 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 + --http-config-bearer-token-authentication-secret-version on + the command line with a fully specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + To set the location attribute: + ◆ provide the argument + --http-config-bearer-token-authentication-secret-version on + the command line with a fully specified name; + ◆ provide the argument --location on the command line. + + To set the secret attribute: + ◆ provide the argument + --http-config-bearer-token-authentication-secret-version on + the command line with a fully specified name; + ◆ provide the argument --secret on the command line. This + resource can be one of the following types: + [developerconnect.projects.locations.secrets.versions, + developerconnect.projects.secrets.versions]. + + --http-config-bearer-token-authentication-secret-version=HTTP_CONFIG_BEARER_TOKEN_AUTHENTICATION_SECRET_VERSION + ID of the secretVersion or fully qualified identifier for + the secretVersion. + + To set the secret_version attribute: + ▸ provide the argument + --http-config-bearer-token-authentication-secret-version + on the command line. + + Basic authentication with username and password. + + --http-config-basic-authentication-username=HTTP_CONFIG_BASIC_AUTHENTICATION_USERNAME + The username to authenticate as. + + Arguments for the password. + + Update http_config_basic_authentication_password_secret_version. + + At most one of these can be specified: + + --clear-http-config-basic-authentication-password-secret-version + Clear + http_config_basic_authentication_password_secret_version + value and set to null. + + SecretVersion resource - Set + http_config_basic_authentication_password_secret_version to + new value. + + The password SecretManager secret version to authenticate as. + 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 + --http-config-basic-authentication-password-secret-version + on the command line with a fully specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + To set the location attribute: + ◆ provide the argument + --http-config-basic-authentication-password-secret-version + on the command line with a fully specified name; + ◆ provide the argument --location on the command line. + + To set the secret attribute: + ◆ provide the argument + --http-config-basic-authentication-password-secret-version + on the command line with a fully specified name; + ◆ provide the argument --secret on the command line. This + resource can be one of the following types: + [developerconnect.projects.locations.secrets.versions, + developerconnect.projects.secrets.versions]. + + --http-config-basic-authentication-password-secret-version=HTTP_CONFIG_BASIC_AUTHENTICATION_PASSWORD_SECRET_VERSION + ID of the secretVersion or fully qualified identifier for + the secretVersion. + + To set the secret_version attribute: + ▸ provide the argument + --http-config-basic-authentication-password-secret-version + on the command line. + The crypto key configuration. This field is used by the Customer-managed encryption keys (CMEK) feature. diff --git a/gcloud/beta/firestore/databases/create b/gcloud/beta/firestore/databases/create index 15a4cbab9..1493059ae 100644 --- a/gcloud/beta/firestore/databases/create +++ b/gcloud/beta/firestore/databases/create @@ -5,16 +5,34 @@ NAME SYNOPSIS gcloud beta firestore databases create --location=LOCATION [--database=DATABASE; default="(default)"] [--delete-protection] - [--edition=EDITION; default="standard"] [--enable-pitr] - [--kms-key-name=KMS_KEY_NAME] [--tags=[KEY=VALUE,...]] - [--type=TYPE; default="firestore-native"] [GCLOUD_WIDE_FLAG ...] + [--edition=EDITION; default="standard"] + [--enable-firestore-data-access] + [--enable-mongodb-compatible-data-access] [--enable-pitr] + [--enable-realtime-updates] [--kms-key-name=KMS_KEY_NAME] + [--tags=[KEY=VALUE,...]] [--type=TYPE; default="firestore-native"] + [GCLOUD_WIDE_FLAG ...] EXAMPLES To create a Firestore Enterprise database named foo in nam5 for use with - MongoDB Compatibility. + MongoDB Compatible API with Data Access Mode enabled. $ gcloud beta firestore databases create --database=foo \ - --edition=enterprise --location=nam5 + --edition=enterprise --location=nam5 \ + --enable-mongodb-compatible-data-access + + To create a Firestore Enterprise database named foo in nam5 for use with + Firestore API Data Access Mode enabled and Realtime Updates disabled. + + $ gcloud beta firestore databases create --database=foo \ + --edition=enterprise --location=nam5 \ + --enable-firestore-data-access + + To create a Firestore Enterprise database named foo in nam5 for use with + Firestore API Data Access Mode enabled and Realtime Updates enabled. + + $ gcloud beta firestore databases create --database=foo \ + --edition=enterprise --location=nam5 \ + --enable-firestore-data-access --enable-realtime-updates To create a Firestore Native database in nam5. @@ -88,6 +106,23 @@ OPTIONAL FLAGS The edition of the database. EDITION must be one of: standard, enterprise. + --enable-firestore-data-access + Whether to enable Firestore API Data Access on the created database. + + If set to true, Firestore API Data Access on the new database will be + enabled. By default, this feature is disabled for Enterprise edition + databases. To explicitly disable, use + --no-enable-firestore-data-access. + + --enable-mongodb-compatible-data-access + Whether to enable MongoDB Compatible API Data Access on the created + database. + + If set to true, MongoDB Compatible API Data Access on the new database + will be enabled. By default, this feature is enabled for Enterprise + edition databases. To disable, use + --no-enable-mongodb-compatible-data-access. + --enable-pitr Whether to enable Point In Time Recovery (PITR) on the created database. @@ -95,6 +130,13 @@ OPTIONAL FLAGS If set to true, PITR on the new database will be enabled. By default, this feature is not enabled. + --enable-realtime-updates + Whether to enable Realtime Updates feature on the created database. + + If set to true, Realtime Updates feature on the new database will be + enabled. By default, this feature is disabled for Enterprise edition + databases. To explicitly disable, use --no-enable-realtime-updates. + --kms-key-name=KMS_KEY_NAME The resource ID of a Cloud KMS key. If set, the database created will be a Customer-Managed Encryption Key (CMEK) database encrypted with diff --git a/gcloud/beta/functions/deploy b/gcloud/beta/functions/deploy index 125f6d19c..1c65834c4 100644 --- a/gcloud/beta/functions/deploy +++ b/gcloud/beta/functions/deploy @@ -4,6 +4,7 @@ NAME SYNOPSIS gcloud beta functions deploy (NAME : --region=REGION) [--[no-]allow-unauthenticated] [--concurrency=CONCURRENCY] + [--direct-vpc-egress=DIRECT_VPC_EGRESS] [--docker-registry=DOCKER_REGISTRY] [--egress-settings=EGRESS_SETTINGS] [--entry-point=ENTRY_POINT] [--gen2] [--ignore-file=IGNORE_FILE] [--ingress-settings=INGRESS_SETTINGS] [--retry] @@ -33,6 +34,9 @@ SYNOPSIS [--clear-labels | --remove-labels=[KEY,...]] [--clear-max-instances | --max-instances=MAX_INSTANCES] [--clear-min-instances | --min-instances=MIN_INSTANCES] + [--clear-network + | --network=NETWORK --subnet=SUBNET --clear-network-tags + | --network-tags=[TAGS,...]] [--clear-secrets | --set-secrets=[SECRET_ENV_VAR=SECRET_VALUE_REF, /secret_path=SECRET_VALUE_REF, @@ -111,6 +115,11 @@ FLAGS instance. Leave concurrency unspecified to receive the server default value. + --direct-vpc-egress=DIRECT_VPC_EGRESS + Specify which of the outbound traffic to send through Direct VPC + egress. Configuring Direct VPC network is required to use this flag. + DIRECT_VPC_EGRESS must be one of: private-ranges-only, all. + --docker-registry=DOCKER_REGISTRY (DEPRECATED) Docker Registry to use for storing the function's Docker images. The option artifact-registry is used by default. @@ -481,6 +490,37 @@ FLAGS Sets the minimum number of instances for the function. This is helpful for reducing cold start times. Defaults to zero. + At most one of these can be specified: + + --clear-network + Disconnect this Cloud Function from the Direct VPC network it is + connected to. + + Direct VPC egress setting flags group. + + --network=NETWORK + The VPC network that the Cloud Function will be able to send + traffic to. If --subnet is also specified, subnet must be a + subnetwork of the network specified by this --network flag. To + clear existing VPC network settings, use --clear-network. + + --subnet=SUBNET + The VPC subnetwork that the Cloud Function will get IPs from. The + subnetwork must be /26 or larger. If --network is also specified, + subnet must be a subnetwork of the network specified by the + --network flag. If --network is not specified, network will be + looked up from this subnetwork. To clear existing VPC network + settings, use --clear-network. + + At most one of these can be specified: + + --clear-network-tags + Clears all existing network tags from the Cloud Function. + + --network-tags=[TAGS,...] + Applies the given network tags (comma separated) to the Cloud + Function. To clear existing tags, use --clear-network-tags. + At most one of these can be specified: --clear-secrets diff --git a/gcloud/beta/gemini/cloud-assist/help b/gcloud/beta/gemini/cloud-assist/help new file mode 100644 index 000000000..810a856ae --- /dev/null +++ b/gcloud/beta/gemini/cloud-assist/help @@ -0,0 +1,23 @@ +NAME + gcloud beta gemini cloud-assist - manage Gemini Cloud Assist + +SYNOPSIS + gcloud beta gemini cloud-assist GROUP [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Manage Gemini Cloud Assist. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +GROUPS + GROUP is one of the following: + + investigations + (BETA) Create and manage Gemini Cloud Assist investigations. + +NOTES + This command is currently in beta and might change without notice. + diff --git a/gcloud/beta/gemini/cloud-assist/investigations/add-iam-policy-binding b/gcloud/beta/gemini/cloud-assist/investigations/add-iam-policy-binding new file mode 100644 index 000000000..70047e727 --- /dev/null +++ b/gcloud/beta/gemini/cloud-assist/investigations/add-iam-policy-binding @@ -0,0 +1,84 @@ +NAME + gcloud beta gemini cloud-assist investigations add-iam-policy-binding - + adds an IAM policy binding for an investigation + +SYNOPSIS + gcloud beta gemini cloud-assist investigations add-iam-policy-binding + INVESTIGATION --member=PRINCIPAL --role=ROLE [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Adds an IAM policy binding for an investigation. + +EXAMPLES + To add an IAM policy binding for the role of + 'roles/geminicloudassist.investigationViewer' for the user + 'test-user@gmail.com' on the investigation + 'project/my-project/locations/my-location/investigations/my-investigation', + run: + + $ gcloud beta gemini cloud-assist investigations \ + add-iam-policy-binding \ + project/my-project/locations/my-location/investigations/\ + my-investigation --member='user:test-user@gmail.com' \ + --role='roles/geminicloudassist.investigationViewer' + + See https://cloud.google.com/iam/docs/managing-policies for details of + policy role and member types. + +POSITIONAL ARGUMENTS + Investigation resource - The investigation name to add IAM policy binding + for. This represents a Cloud resource. (NOTE) Some attributes are not + given arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument investigation on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + To set the location attribute: + ◆ provide the argument investigation on the command line with a fully + specified name; + ◆ The default is global. + + This must be specified. + + INVESTIGATION + ID of the investigation or fully qualified identifier for the + investigation. + + To set the investigation attribute: + ▸ provide the argument investigation on the command line. + +REQUIRED FLAGS + --member=PRINCIPAL + The principal to add the binding for. Should be of the form + user|group|serviceAccount:email or domain:domain. + + Examples: user:test-user@gmail.com, group:admins@example.com, + serviceAccount:test123@example.domain.com, or + domain:example.domain.com. + + Some resources also accept the following special values: + ◆ allUsers - Special identifier that represents anyone who is on the + internet, with or without a Google account. + ◆ allAuthenticatedUsers - Special identifier that represents anyone + who is authenticated with a Google account or a service account. + + --role=ROLE + Role name to assign to the principal. The role name is the complete + path of a predefined role, such as roles/logging.viewer, or the role ID + for a custom role, such as + organizations/{ORGANIZATION_ID}/roles/logging.viewer. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. + diff --git a/gcloud/beta/gemini/cloud-assist/investigations/create b/gcloud/beta/gemini/cloud-assist/investigations/create new file mode 100644 index 000000000..cd5557c08 --- /dev/null +++ b/gcloud/beta/gemini/cloud-assist/investigations/create @@ -0,0 +1,79 @@ +NAME + gcloud beta gemini cloud-assist investigations create - create a new + investigation + +SYNOPSIS + gcloud beta gemini cloud-assist investigations create [INVESTIGATION] + --issue=ISSUE [--end-time=END_TIME] [--resources=[RESOURCE,...]] + [--start-time=START_TIME] [--title=TITLE] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Shows metadata for the newly created investigation after creation. + + This command can fail for the following reasons: + ▪ The chosen investigation ID, if specified, already exists. + ▪ The active account does not have permission to create investigations + in the project. + +EXAMPLES + The following command creates a new investigation with the ID and some + basic information example-foo-bar-1: + + $ gcloud beta gemini cloud-assist investigations create \ + example-foo-bar-1 --title="Example Investigation" --issue="I + have a problem" --start-time=2025-07-10 + +POSITIONAL ARGUMENTS + Investigation resource - The investigation name to create. This represents + a Cloud resource. (NOTE) Some attributes are not given arguments in this + group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument investigation on the command line with a fully + specified name; + ◆ The default is - with a fully specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + To set the location attribute: + ◆ provide the argument investigation on the command line with a fully + specified name; + ◆ The default is - with a fully specified name; + ◆ The default is global. + + [INVESTIGATION] + ID of the investigation or fully qualified identifier for the + investigation. + + To set the investigation attribute: + ▸ provide the argument investigation on the command line; + ▸ The default is -. + +REQUIRED FLAGS + --issue=ISSUE + A description of the issue you are investigating, or an error log. + +OPTIONAL FLAGS + --end-time=END_TIME + The estimated end time of the issue you are investigating. + + --resources=[RESOURCE,...] + A list of resources relevant to the investigation + + --start-time=START_TIME + The estimated start time of the issue you are investigating. + + --title=TITLE + The desired title of the resulting investigation. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. + diff --git a/gcloud/beta/gemini/cloud-assist/investigations/delete b/gcloud/beta/gemini/cloud-assist/investigations/delete new file mode 100644 index 000000000..373388671 --- /dev/null +++ b/gcloud/beta/gemini/cloud-assist/investigations/delete @@ -0,0 +1,64 @@ +NAME + gcloud beta gemini cloud-assist investigations delete - delete an + Investigation + +SYNOPSIS + gcloud beta gemini cloud-assist investigations delete + (INVESTIGATION : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Delete a Gemini Cloud Assist Investigation. + +EXAMPLES + The following command deletes an Investigation with ID foo-bar-1 + + $ gcloud beta gemini cloud-assist investigations delete foo-bar-1 + +POSITIONAL ARGUMENTS + Investigation resource - The investigation 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 investigation 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. + + INVESTIGATION + ID of the investigation or fully qualified identifier for the + investigation. + + To set the investigation attribute: + ▸ provide the argument investigation on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + ID of the location of the Gemini Cloud Assist resource. + + To set the location attribute: + ▸ provide the argument investigation on the command line with a + fully specified name; + ▸ provide the argument --location on the command line; + ▸ The default is global. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the geminicloudassist/v1 API. The full documentation for + this API can be found at: https://cloud.google.com/gemini + +NOTES + This command is currently in beta and might change without notice. + diff --git a/gcloud/beta/gemini/cloud-assist/investigations/describe b/gcloud/beta/gemini/cloud-assist/investigations/describe new file mode 100644 index 000000000..06c0a8da3 --- /dev/null +++ b/gcloud/beta/gemini/cloud-assist/investigations/describe @@ -0,0 +1,67 @@ +NAME + gcloud beta gemini cloud-assist investigations describe - show metadata for + an investigation + +SYNOPSIS + gcloud beta gemini cloud-assist investigations describe INVESTIGATION + [--detail] [--raw] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Shows metadata for an investigation given a valid investigation ID. + + This command can fail for the following reasons: + ▪ The investigation specified does not exist. + ▪ The active account does not have permission to access the given + investigation. + +EXAMPLES + The following command prints metadata for an investigation with the ID + example-foo-bar-1: + + $ gcloud beta gemini cloud-assist investigations describe \ + example-foo-bar-1 + +POSITIONAL ARGUMENTS + Investigation resource - The investigation name to describe. This + represents a Cloud resource. (NOTE) Some attributes are not given + arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument investigation on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + To set the location attribute: + ◆ provide the argument investigation on the command line with a fully + specified name; + ◆ The default is global. + + This must be specified. + + INVESTIGATION + ID of the investigation or fully qualified identifier for the + investigation. + + To set the investigation attribute: + ▸ provide the argument investigation on the command line. + +FLAGS + --detail + Include extra information in the default output. + + --raw + Return the full, unaltered API response instead of the version + formatted for human consumption. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. + diff --git a/gcloud/beta/gemini/cloud-assist/investigations/get-iam-policy b/gcloud/beta/gemini/cloud-assist/investigations/get-iam-policy new file mode 100644 index 000000000..22e31da2b --- /dev/null +++ b/gcloud/beta/gemini/cloud-assist/investigations/get-iam-policy @@ -0,0 +1,56 @@ +NAME + gcloud beta gemini cloud-assist investigations get-iam-policy - get IAM + policy for an investigation + +SYNOPSIS + gcloud beta gemini cloud-assist investigations get-iam-policy INVESTIGATION + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Get IAM policy for an investigation. + +EXAMPLES + To get the IAM policy a the investigation + 'project/my-project/locations/my-location/investigations/my-investigation', + run: + + $ gcloud beta gemini cloud-assist investigations get-iam-policy \ + project/my-project/locations/my-location/investigations/\ + my-investigation + +POSITIONAL ARGUMENTS + Investigation resource - The investigation name to get IAM policy for. + This represents a Cloud resource. (NOTE) Some attributes are not given + arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument investigation on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + To set the location attribute: + ◆ provide the argument investigation on the command line with a fully + specified name; + ◆ The default is global. + + This must be specified. + + INVESTIGATION + ID of the investigation or fully qualified identifier for the + investigation. + + To set the investigation attribute: + ▸ provide the argument investigation on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. + diff --git a/gcloud/beta/gemini/cloud-assist/investigations/help b/gcloud/beta/gemini/cloud-assist/investigations/help new file mode 100644 index 000000000..7e18bc37a --- /dev/null +++ b/gcloud/beta/gemini/cloud-assist/investigations/help @@ -0,0 +1,49 @@ +NAME + gcloud beta gemini cloud-assist investigations - create and manage Gemini + Cloud Assist investigations + +SYNOPSIS + gcloud beta gemini cloud-assist investigations COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Create and manage Gemini Cloud Assist investigations. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + add-iam-policy-binding + (BETA) Adds an IAM policy binding for an investigation. + + create + (BETA) Create a new investigation. + + delete + (BETA) Delete an Investigation. + + describe + (BETA) Show metadata for an investigation. + + get-iam-policy + (BETA) Get IAM policy for an investigation. + + list + (BETA) List Gemini Cloud Assist Investigations. + + remove-iam-policy-binding + (BETA) Removes an IAM policy binding from an investigation. + + set-iam-policy + (BETA) Sets IAM policy for an investigation. + + update + (BETA) Update an existing investigation. + +NOTES + This command is currently in beta and might change without notice. + diff --git a/gcloud/beta/gemini/cloud-assist/investigations/list b/gcloud/beta/gemini/cloud-assist/investigations/list new file mode 100644 index 000000000..0f40990d6 --- /dev/null +++ b/gcloud/beta/gemini/cloud-assist/investigations/list @@ -0,0 +1,77 @@ +NAME + gcloud beta gemini cloud-assist investigations list - list Gemini Cloud + Assist Investigations + +SYNOPSIS + gcloud beta gemini cloud-assist investigations list [--location=LOCATION] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) List Gemini Cloud Assist Investigations. + +EXAMPLES + To list Gemini Cloud Assist Investigations, run: + + $ gcloud beta gemini cloud-assist investigations list + +FLAGS + Location resource - Location to list investigations for. This represents a + Cloud resource. (NOTE) Some attributes are not given arguments in this + group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument --location on the command line with a fully + specified name; + ◆ The default is global with a fully specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + --location=LOCATION + ID of the location or fully qualified identifier for the location. + + To set the location attribute: + ▸ provide the argument --location on the command line; + ▸ The default is global. + +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 geminicloudassist/v1 API. The full documentation for + this API can be found at: https://cloud.google.com/gemini + +NOTES + This command is currently in beta and might change without notice. + diff --git a/gcloud/beta/gemini/cloud-assist/investigations/remove-iam-policy-binding b/gcloud/beta/gemini/cloud-assist/investigations/remove-iam-policy-binding new file mode 100644 index 000000000..366176706 --- /dev/null +++ b/gcloud/beta/gemini/cloud-assist/investigations/remove-iam-policy-binding @@ -0,0 +1,84 @@ +NAME + gcloud beta gemini cloud-assist investigations remove-iam-policy-binding - + removes an IAM policy binding from an investigation + +SYNOPSIS + gcloud beta gemini cloud-assist investigations remove-iam-policy-binding + INVESTIGATION --member=PRINCIPAL --role=ROLE [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Removes an IAM policy binding from an investigation. + +EXAMPLES + To remove an IAM policy binding for the role of + 'roles/geminicloudassist.investigationUser' for the user + 'test-user@gmail.com' from the investigation + 'project/my-project/locations/my-location/investigations/my-investigation', + run: + + $ gcloud beta gemini cloud-assist investigations \ + remove-iam-policy-binding \ + project/my-project/locations/my-location/investigations/\ + my-investigation --member='user:test-user@gmail.com' \ + --role='roles/geminicloudassist.investigations.user' + + See https://cloud.google.com/iam/docs/managing-policies for details of + policy role and member types. + +POSITIONAL ARGUMENTS + Investigation resource - The investigation name to remove IAM policy + binding from. 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 investigation on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + To set the location attribute: + ◆ provide the argument investigation on the command line with a fully + specified name; + ◆ The default is global. + + This must be specified. + + INVESTIGATION + ID of the investigation or fully qualified identifier for the + investigation. + + To set the investigation attribute: + ▸ provide the argument investigation on the command line. + +REQUIRED FLAGS + --member=PRINCIPAL + The principal to add the binding for. Should be of the form + user|group|serviceAccount:email or domain:domain. + + Examples: user:test-user@gmail.com, group:admins@example.com, + serviceAccount:test123@example.domain.com, or + domain:example.domain.com. + + Some resources also accept the following special values: + ◆ allUsers - Special identifier that represents anyone who is on the + internet, with or without a Google account. + ◆ allAuthenticatedUsers - Special identifier that represents anyone + who is authenticated with a Google account or a service account. + + --role=ROLE + Role name to assign to the principal. The role name is the complete + path of a predefined role, such as roles/logging.viewer, or the role ID + for a custom role, such as + organizations/{ORGANIZATION_ID}/roles/logging.viewer. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. + diff --git a/gcloud/beta/gemini/cloud-assist/investigations/set-iam-policy b/gcloud/beta/gemini/cloud-assist/investigations/set-iam-policy new file mode 100644 index 000000000..87c53d279 --- /dev/null +++ b/gcloud/beta/gemini/cloud-assist/investigations/set-iam-policy @@ -0,0 +1,59 @@ +NAME + gcloud beta gemini cloud-assist investigations set-iam-policy - sets IAM + policy for an investigation + +SYNOPSIS + gcloud beta gemini cloud-assist investigations set-iam-policy INVESTIGATION + POLICY_FILE [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Sets IAM policy for an investigation. + +EXAMPLES + To set IAM policy for theinvestigation + project/my-project/locations/my-location/investigations/my-investigation + defined in POLICY-FILE-1', run: + + $ gcloud beta gemini cloud-assist investigations set-iam-policy \ + project/my-project/locations/my-location/investigations/\ + my-investigation POLICY-FILE-1 + +POSITIONAL ARGUMENTS + Investigation resource - The investigation name to remove IAM policy + binding from. 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 investigation on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + To set the location attribute: + ◆ provide the argument investigation on the command line with a fully + specified name; + ◆ The default is global. + + This must be specified. + + INVESTIGATION + ID of the investigation or fully qualified identifier for the + investigation. + + To set the investigation attribute: + ▸ provide the argument investigation on the command line. + + POLICY_FILE + Path to a local JSON or YAML formatted file containing a valid policy. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. + diff --git a/gcloud/beta/gemini/cloud-assist/investigations/update b/gcloud/beta/gemini/cloud-assist/investigations/update new file mode 100644 index 000000000..b81287809 --- /dev/null +++ b/gcloud/beta/gemini/cloud-assist/investigations/update @@ -0,0 +1,100 @@ +NAME + gcloud beta gemini cloud-assist investigations update - update an existing + investigation + +SYNOPSIS + gcloud beta gemini cloud-assist investigations update INVESTIGATION + [--issue=ISSUE] [--end-time=END_TIME | --clear-end-time] + [--resources=[RESOURCE,...] | --clear-resources] + [--start-time=START_TIME | --clear-start-time] + [--title=TITLE | --clear-title] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Shows metadata for the investigation after updating. + + This command can fail for the following reasons: + ▪ The investigation ID doesn't exist. + ▪ The active account does not have permission to update the + investigation. + ▪ The investigation is currently running. + +EXAMPLES + The following command updates title, text description, resources, and start + time of the existing investigation with the name`example-foo-bar-1: + + $ gcloud beta gemini cloud-assist investigations update \ + example-foo-bar-1 --title="Example Investigation" \ + --issue="I have a problem" --start-time=2025-07-10 + +POSITIONAL ARGUMENTS + Investigation resource - The investigation name to update. This represents + a Cloud resource. (NOTE) Some attributes are not given arguments in this + group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument investigation on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + To set the location attribute: + ◆ provide the argument investigation on the command line with a fully + specified name; + ◆ The default is global. + + This must be specified. + + INVESTIGATION + ID of the investigation or fully qualified identifier for the + investigation. + + To set the investigation attribute: + ▸ provide the argument investigation on the command line. + +FLAGS + --issue=ISSUE + A description of the issue you are investigating, or an error log. + + At most one of these can be specified: + + --end-time=END_TIME + The estimated end time of the issue you are investigating. + + --clear-end-time + Clear the end time of the investigation. + + At most one of these can be specified: + + --resources=[RESOURCE,...] + A list of resources relevant to the investigation + + --clear-resources + Clear the resources of the investigation. + + At most one of these can be specified: + + --start-time=START_TIME + The estimated start time of the issue you are investigating. + + --clear-start-time + Clear the start time of the investigation. + + At most one of these can be specified: + + --title=TITLE + The desired title of the resulting investigation. + + --clear-title + Clear the title of the investigation. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. + diff --git a/gcloud/beta/gemini/help b/gcloud/beta/gemini/help new file mode 100644 index 000000000..d0ee500f0 --- /dev/null +++ b/gcloud/beta/gemini/help @@ -0,0 +1,28 @@ +NAME + gcloud beta gemini - manage resources associated with Gemini Code Assist + and Gemini Cloud Assist + +SYNOPSIS + gcloud beta gemini GROUP [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) gcloud gemini commands are not associated with Gemini CLI + (https://github.com/google-gemini/gemini-cli). + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +GROUPS + GROUP is one of the following: + + cloud-assist + (BETA) Manage Gemini Cloud Assist. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud gemini + diff --git a/gcloud/beta/redis/clusters/create b/gcloud/beta/redis/clusters/create index 96f62ff1e..6e8ddbbe4 100644 --- a/gcloud/beta/redis/clusters/create +++ b/gcloud/beta/redis/clusters/create @@ -9,7 +9,7 @@ SYNOPSIS [--automated-backup-start-time=AUTOMATED_BACKUP_START_TIME] [--automated-backup-ttl=AUTOMATED_BACKUP_TTL] [--cross-cluster-replication-role=CROSS_CLUSTER_REPLICATION_ROLE] - [--deletion-protection] [--kms-key=KMS_KEY] + [--deletion-protection] [--kms-key=KMS_KEY] [--labels=[KEY=VALUE,...]] [--maintenance-window-day=MAINTENANCE_WINDOW_DAY] [--maintenance-window-hour=MAINTENANCE_WINDOW_HOUR] [--network=NETWORK] [--node-type=NODE_TYPE] [--persistence-mode=PERSISTENCE_MODE] @@ -151,6 +151,14 @@ FLAGS The key must be in the same region as the cluster. Otherwise, the create operation fails. + --labels=[KEY=VALUE,...] + List of label KEY=VALUE pairs to add. + + Keys must start with a lowercase character and contain only hyphens + (-), underscores (_), lowercase characters, and numbers. Values must + contain only hyphens (-), underscores (_), lowercase characters, and + numbers. + --maintenance-window-day=MAINTENANCE_WINDOW_DAY Day of week when the window starts, e.g. sunday. MAINTENANCE_WINDOW_DAY must be one of: friday, monday, saturday, sunday, thursday, tuesday, diff --git a/gcloud/beta/redis/clusters/update b/gcloud/beta/redis/clusters/update index e43f4d991..c71f6d09f 100644 --- a/gcloud/beta/redis/clusters/update +++ b/gcloud/beta/redis/clusters/update @@ -14,7 +14,8 @@ SYNOPSIS [--rdb-snapshot-start-time=RDB_SNAPSHOT_START_TIME] [--remove-redis-config=[KEY,...]] [--replica-count=REPLICA_COUNT] [--shard-count=SHARD_COUNT] [--simulate-maintenance-event] - [--update-redis-config=KEY=VALUE] + [--update-labels=[KEY=VALUE,...]] [--update-redis-config=KEY=VALUE] + [--clear-labels | --remove-labels=[KEY,...]] [--maintenance-window-any | --maintenance-window-day=MAINTENANCE_WINDOW_DAY --maintenance-window-hour=MAINTENANCE_WINDOW_HOUR] @@ -157,11 +158,40 @@ FLAGS --simulate-maintenance-event Trigger a simulation for maintenance event. + --update-labels=[KEY=VALUE,...] + List of label KEY=VALUE pairs to update. If a label exists, its value + is modified. Otherwise, a new label is created. + + Keys must start with a lowercase character and contain only hyphens + (-), underscores (_), lowercase characters, and numbers. Values must + contain only hyphens (-), underscores (_), lowercase characters, and + numbers. + --update-redis-config=KEY=VALUE A list of Redis Cluster config KEY=VALUE pairs to update. If a config parameter is already set, its value is modified; otherwise a new Redis config parameter is added. + At most one of these can be specified: + + --clear-labels + Remove all labels. If --update-labels is also specified then + --clear-labels is applied first. + + For example, to remove all labels: + + $ gcloud beta redis clusters update --clear-labels + + To remove all existing labels and create two new labels, foo and baz: + + $ gcloud beta redis clusters update --clear-labels \ + --update-labels foo=bar,baz=qux + + --remove-labels=[KEY,...] + List of label keys to remove. If a label does not exist it is + silently ignored. If --update-labels is also specified then + --update-labels is applied first. + At most one of these can be specified: --maintenance-window-any diff --git a/gcloud/beta/run/deploy b/gcloud/beta/run/deploy index 371c71fcf..85717c077 100644 --- a/gcloud/beta/run/deploy +++ b/gcloud/beta/run/deploy @@ -263,7 +263,7 @@ FLAGS and resume server-assigned naming. --scaling=SCALING - The scaling mode to use for this resource. Flag value could be either + The scaling mode to use for this service. Flag value could be either "auto" for automatic scaling, or a positive integer to configure manual scaling with the given integer as a fixed instance count. @@ -604,7 +604,8 @@ FLAGS KEY_1: "value1" KEY_2: "value 2" - Example ENV content: + + Example ENV content: KEY_1="value1" KEY_2="value 2" diff --git a/gcloud/beta/run/jobs/create b/gcloud/beta/run/jobs/create index a48f7cc15..912edde13 100644 --- a/gcloud/beta/run/jobs/create +++ b/gcloud/beta/run/jobs/create @@ -291,7 +291,8 @@ FLAGS KEY_1: "value1" KEY_2: "value 2" - Example ENV content: + + Example ENV content: KEY_1="value1" KEY_2="value 2" diff --git a/gcloud/beta/run/jobs/deploy b/gcloud/beta/run/jobs/deploy index 12ddff0e0..33ca5748b 100644 --- a/gcloud/beta/run/jobs/deploy +++ b/gcloud/beta/run/jobs/deploy @@ -293,7 +293,8 @@ FLAGS KEY_1: "value1" KEY_2: "value 2" - Example ENV content: + + Example ENV content: KEY_1="value1" KEY_2="value 2" diff --git a/gcloud/beta/run/jobs/update b/gcloud/beta/run/jobs/update index e693448b4..0c72e21b1 100644 --- a/gcloud/beta/run/jobs/update +++ b/gcloud/beta/run/jobs/update @@ -308,7 +308,8 @@ FLAGS KEY_1: "value1" KEY_2: "value 2" - Example ENV content: + + Example ENV content: KEY_1="value1" KEY_2="value 2" diff --git a/gcloud/beta/run/multi-region-services/update b/gcloud/beta/run/multi-region-services/update index 2ad0b6654..6aee7a4f3 100644 --- a/gcloud/beta/run/multi-region-services/update +++ b/gcloud/beta/run/multi-region-services/update @@ -235,7 +235,7 @@ FLAGS and resume server-assigned naming. --scaling=SCALING - The scaling mode to use for this resource. Flag value could be either + The scaling mode to use for this service. Flag value could be either "auto" for automatic scaling, or a positive integer to configure manual scaling with the given integer as a fixed instance count. @@ -473,7 +473,8 @@ FLAGS KEY_1: "value1" KEY_2: "value 2" - Example ENV content: + + Example ENV content: KEY_1="value1" KEY_2="value 2" diff --git a/gcloud/beta/run/services/update b/gcloud/beta/run/services/update index a6384b5d2..ca0c02799 100644 --- a/gcloud/beta/run/services/update +++ b/gcloud/beta/run/services/update @@ -233,7 +233,7 @@ FLAGS and resume server-assigned naming. --scaling=SCALING - The scaling mode to use for this resource. Flag value could be either + The scaling mode to use for this service. Flag value could be either "auto" for automatic scaling, or a positive integer to configure manual scaling with the given integer as a fixed instance count. @@ -514,7 +514,8 @@ FLAGS KEY_1: "value1" KEY_2: "value 2" - Example ENV content: + + Example ENV content: KEY_1="value1" KEY_2="value 2" diff --git a/gcloud/beta/run/worker-pools/deploy b/gcloud/beta/run/worker-pools/deploy index 09baa2475..526025fae 100644 --- a/gcloud/beta/run/worker-pools/deploy +++ b/gcloud/beta/run/worker-pools/deploy @@ -6,10 +6,10 @@ SYNOPSIS gcloud beta run worker-pools deploy [[WORKER_POOL] --region=REGION] [--async] [--breakglass=JUSTIFICATION] [--container=CONTAINER] [--description=DESCRIPTION] [--gpu-type=GPU_TYPE] - [--[no-]gpu-zonal-redundancy] [--no-promote] + [--[no-]gpu-zonal-redundancy] [--instances=INSTANCES] [--no-promote] [--remove-containers=[CONTAINER,...]] - [--revision-suffix=REVISION_SUFFIX] [--scaling=SCALING] - [--service-account=SERVICE_ACCOUNT] [--vpc-egress=VPC_EGRESS] + [--revision-suffix=REVISION_SUFFIX] [--service-account=SERVICE_ACCOUNT] + [--vpc-egress=VPC_EGRESS] [--add-cloudsql-instances=[CLOUDSQL-INSTANCES,...] | --clear-cloudsql-instances | --remove-cloudsql-instances=[CLOUDSQL-INSTANCES,...] @@ -117,6 +117,11 @@ FLAGS Set GPU zonal redundancy. Use --gpu-zonal-redundancy to enable and --no-gpu-zonal-redundancy to disable. + --instances=INSTANCES + The number of instances to run for this WorkerPool. Flag value should + be a positive integer to configure manual scaling with the given + integer as a fixed instance count. + --no-promote True to avoid assign instances to the worker revision being deployed. Setting this flag assigns any instances assigned to the LATEST revision @@ -139,11 +144,6 @@ FLAGS a revision named 'helloworld-v1'. Set empty string to clear the suffix and resume server-assigned naming. - --scaling=SCALING - The scaling mode to use for this resource. Flag value should be a - positive integer to configure manual scaling with the given integer as - a fixed instance count. - --service-account=SERVICE_ACCOUNT the email address of an IAM service account associated with the revision of the service. The service account represents the identity of @@ -308,7 +308,8 @@ FLAGS KEY_1: "value1" KEY_2: "value 2" - Example ENV content: + + Example ENV content: KEY_1="value1" KEY_2="value 2" diff --git a/gcloud/beta/run/worker-pools/help b/gcloud/beta/run/worker-pools/help index 1b4710688..9d7df96d9 100644 --- a/gcloud/beta/run/worker-pools/help +++ b/gcloud/beta/run/worker-pools/help @@ -21,6 +21,9 @@ GCLOUD WIDE FLAGS GROUPS GROUP is one of the following: + logs + (BETA) Read logs for Cloud Run worker pools. + revisions (BETA) View and manage your Cloud Run WorkerPools revisions. diff --git a/gcloud/beta/run/worker-pools/logs/help b/gcloud/beta/run/worker-pools/logs/help new file mode 100644 index 000000000..68c3ceee5 --- /dev/null +++ b/gcloud/beta/run/worker-pools/logs/help @@ -0,0 +1,44 @@ +NAME + gcloud beta run worker-pools logs - read logs for Cloud Run worker pools + +SYNOPSIS + gcloud beta run worker-pools logs COMMAND [--region=REGION] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Read logs for Cloud Run worker pools. + +EXAMPLES + To tail logs for a worker pool, run: + + $ gcloud beta run worker-pools logs tail my-worker-pool + + To read logs for a worker pool, run: + + $ gcloud beta run worker-pools logs read my-worker-pool + +FLAGS + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + read + (BETA) Read logs for a Cloud Run worker pool. + + tail + (BETA) Tail logs for a Cloud Run worker pool. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha run worker-pools logs + diff --git a/gcloud/beta/run/worker-pools/logs/read b/gcloud/beta/run/worker-pools/logs/read new file mode 100644 index 000000000..98dd834d2 --- /dev/null +++ b/gcloud/beta/run/worker-pools/logs/read @@ -0,0 +1,84 @@ +NAME + gcloud beta run worker-pools logs read - read logs for a Cloud Run worker + pool + +SYNOPSIS + gcloud beta run worker-pools logs read WORKER_POOL + [--freshness=FRESHNESS; default="1d"] [--log-filter=LOG_FILTER] + [--order=ORDER; default="desc"] [--region=REGION] [--limit=LIMIT] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) gcloud beta run worker-pools logs read reads log entries. Log + entries matching --log-filter are returned according to the specified + --order. If the log entries come from multiple logs, then entries from + different logs might be intermingled in the results. + +EXAMPLES + To read log entries from for a Cloud Run Worker Pool, run: + + $ gcloud beta run worker-pools logs read my-worker-pool + + To read log entries with severity ERROR or higher, run: + + $ gcloud beta run worker-pools logs read my-worker-pool \ + --log-filter="severity>=ERROR" + + To read log entries written in a specific time window, run: + + $ gcloud beta run worker-pools logs read my-worker-pool \ + --log-filter='timestamp<="2015-05-31T23:59:59Z" AND + timestamp>="2015-05-31T00:00:00Z"' + + To read up to 10 log entries in your worker pool payloads that include the + word SearchText and format the output in JSON format, run: + + $ gcloud beta run worker-pools logs read my-worker-pool \ + --log-filter="textPayload:SearchText" --limit=10 --format=json + + Detailed information about filters can be found at: + https://cloud.google.com/logging/docs/view/advanced_filters + +POSITIONAL ARGUMENTS + WORKER_POOL + Name for a Cloud Run worker pool. + +FLAGS + --freshness=FRESHNESS; default="1d" + Return entries that are not older than this value. Works only with DESC + ordering and filters without a timestamp. See $ gcloud topic datetimes + for information on duration formats. + + --log-filter=LOG_FILTER + Filter expression that specifies the log entries to return. Detailed + information about filters can be found at: + https://cloud.google.com/logging/docs/view/logging-query-language + + --order=ORDER; default="desc" + Ordering of returned log entries based on timestamp field. ORDER must + be one of: desc, asc. + + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. + +LIST COMMAND FLAGS + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha run worker-pools logs read + diff --git a/gcloud/beta/run/worker-pools/logs/tail b/gcloud/beta/run/worker-pools/logs/tail new file mode 100644 index 000000000..baab980eb --- /dev/null +++ b/gcloud/beta/run/worker-pools/logs/tail @@ -0,0 +1,54 @@ +NAME + gcloud beta run worker-pools logs tail - tail logs for a Cloud Run worker + pool + +SYNOPSIS + gcloud beta run worker-pools logs tail WORKER_POOL + [--log-filter=LOG_FILTER] [--region=REGION] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) gcloud beta run worker-pools logs tail tails log-entries for a + particular Cloud Run worker pool in real time. The log entries are + formatted for consumption in a terminal. + +EXAMPLES + To tail log entries for a Cloud Run Worker Pool, run: + + $ gcloud beta run worker-pools logs tail my-worker-pool + + To tail log entries with severity ERROR or higher, run: + + $ gcloud beta run worker-pools logs tail my-worker-pool \ + --log-filter="severity>=ERROR" + + Detailed information about filters can be found at: + https://cloud.google.com/logging/docs/view/advanced_filters + +POSITIONAL ARGUMENTS + WORKER_POOL + Name for a Cloud Run worker pool. + +FLAGS + --log-filter=LOG_FILTER + Filter expression that specifies the log entries to return. Detailed + information about filters can be found at: + https://cloud.google.com/logging/docs/view/logging-query-language + + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha run worker-pools logs tail + diff --git a/gcloud/beta/run/worker-pools/update b/gcloud/beta/run/worker-pools/update index 827a79ac0..1b7de1163 100644 --- a/gcloud/beta/run/worker-pools/update +++ b/gcloud/beta/run/worker-pools/update @@ -6,10 +6,10 @@ SYNOPSIS gcloud beta run worker-pools update [[WORKER_POOL] --region=REGION] [--async] [--breakglass=JUSTIFICATION] [--container=CONTAINER] [--description=DESCRIPTION] [--gpu-type=GPU_TYPE] - [--[no-]gpu-zonal-redundancy] [--no-promote] + [--[no-]gpu-zonal-redundancy] [--instances=INSTANCES] [--no-promote] [--remove-containers=[CONTAINER,...]] - [--revision-suffix=REVISION_SUFFIX] [--scaling=SCALING] - [--service-account=SERVICE_ACCOUNT] [--vpc-egress=VPC_EGRESS] + [--revision-suffix=REVISION_SUFFIX] [--service-account=SERVICE_ACCOUNT] + [--vpc-egress=VPC_EGRESS] [--add-cloudsql-instances=[CLOUDSQL-INSTANCES,...] | --clear-cloudsql-instances | --remove-cloudsql-instances=[CLOUDSQL-INSTANCES,...] @@ -113,6 +113,11 @@ FLAGS Set GPU zonal redundancy. Use --gpu-zonal-redundancy to enable and --no-gpu-zonal-redundancy to disable. + --instances=INSTANCES + The number of instances to run for this WorkerPool. Flag value should + be a positive integer to configure manual scaling with the given + integer as a fixed instance count. + --no-promote True to avoid assign instances to the worker revision being deployed. Setting this flag assigns any instances assigned to the LATEST revision @@ -135,11 +140,6 @@ FLAGS a revision named 'helloworld-v1'. Set empty string to clear the suffix and resume server-assigned naming. - --scaling=SCALING - The scaling mode to use for this resource. Flag value should be a - positive integer to configure manual scaling with the given integer as - a fixed instance count. - --service-account=SERVICE_ACCOUNT the email address of an IAM service account associated with the revision of the service. The service account represents the identity of @@ -308,7 +308,8 @@ FLAGS KEY_1: "value1" KEY_2: "value 2" - Example ENV content: + + Example ENV content: KEY_1="value1" KEY_2="value 2" diff --git a/gcloud/beta/secrets/replication/update b/gcloud/beta/secrets/replication/update index c56ff1347..8ad192d76 100644 --- a/gcloud/beta/secrets/replication/update +++ b/gcloud/beta/secrets/replication/update @@ -24,15 +24,16 @@ EXAMPLES To set the CMEK key on an automatic secret called my-secret to a specified KMS key, run: - $gcloud beta secrets replication update my-secret - --set-kms-key=projects/my-project/locations/global/keyRings/my-keyring/cryptoKeys/my-key + $ gcloud beta secrets replication update my-secret \ + --set-kms-key=projects/my-project/locations/global/keyRings/\ + my-keyring/cryptoKeys/my-key To set the CMEK key on a secret called my-secret to a specified KMS key in a specified location in its replication, run: - $gcloud beta secrets replication update my-secret - --set-kms-key=projects/my-project/locations/us-central1/keyRings/my-keyring/cryptoKeys/my-key - --location=us-central1 + $ gcloud beta secrets replication update my-secret \ + --set-kms-key=projects/my-project/locations/us-central1/\ + keyRings/my-keyring/cryptoKeys/my-key --location=us-central1 POSITIONAL ARGUMENTS Secret resource - The secret to update. This represents a Cloud resource. diff --git a/gcloud/beta/spanner/instance-partitions/create b/gcloud/beta/spanner/instance-partitions/create index fbf2c2237..a6316d3c8 100644 --- a/gcloud/beta/spanner/instance-partitions/create +++ b/gcloud/beta/spanner/instance-partitions/create @@ -6,7 +6,9 @@ SYNOPSIS gcloud beta spanner instance-partitions create (INSTANCE_PARTITION : --instance=INSTANCE) --config=CONFIG --description=DESCRIPTION [--async] - [--nodes=NODES | --processing-units=PROCESSING_UNITS] + [--nodes=NODES | --processing-units=PROCESSING_UNITS + | --autoscaling-storage-target=AUTOSCALING_STORAGE_TARGET + (--autoscaling-high-priority-cpu-target=AUTOSCALING_HIGH_PRIORITY_CPU_TARGET --autoscaling-total-cpu-target=AUTOSCALING_TOTAL_CPU_TARGET) (--autoscaling-max-nodes=AUTOSCALING_MAX_NODES --autoscaling-min-nodes=AUTOSCALING_MIN_NODES | --autoscaling-max-processing-units=AUTOSCALING_MAX_PROCESSING_UNITS --autoscaling-min-processing-units=AUTOSCALING_MIN_PROCESSING_UNITS)] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -75,6 +77,59 @@ OPTIONAL FLAGS --processing-units=PROCESSING_UNITS Number of processing units for the instance partition. + Autoscaling + + --autoscaling-storage-target=AUTOSCALING_STORAGE_TARGET + Specifies the target percentage of storage the autoscaled instance + can utilize. + + This flag argument must be specified if any of the other arguments + in this group are specified. + + Autoscaling CPU targets. + + At least one of these must be specified: + + --autoscaling-high-priority-cpu-target=AUTOSCALING_HIGH_PRIORITY_CPU_TARGET + Specifies the target percentage of high-priority CPU the + autoscaled instance can utilize. + + --autoscaling-total-cpu-target=AUTOSCALING_TOTAL_CPU_TARGET + Specifies the target percentage of total CPU the autoscaled + instance can utilize. + + Autoscaling limits can be defined in either nodes or processing units. + + Exactly one of these must be specified: + + Autoscaling limits in nodes: + + --autoscaling-max-nodes=AUTOSCALING_MAX_NODES + Maximum number of nodes for the autoscaled instance. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --autoscaling-min-nodes=AUTOSCALING_MIN_NODES + Minimum number of nodes for the autoscaled instance. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + Autoscaling limits in processing units: + + --autoscaling-max-processing-units=AUTOSCALING_MAX_PROCESSING_UNITS + Maximum number of processing units for the autoscaled instance. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --autoscaling-min-processing-units=AUTOSCALING_MIN_PROCESSING_UNITS + Minimum number of processing units for the autoscaled instance. + + This flag argument must be specified if any of the other + arguments in this group are specified. + 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/spanner/instance-partitions/update b/gcloud/beta/spanner/instance-partitions/update index b16eb0b6d..5f7a664ba 100644 --- a/gcloud/beta/spanner/instance-partitions/update +++ b/gcloud/beta/spanner/instance-partitions/update @@ -7,7 +7,9 @@ SYNOPSIS gcloud beta spanner instance-partitions update (INSTANCE_PARTITION : --instance=INSTANCE) [--async] [--description=DESCRIPTION] - [--nodes=NODES | --processing-units=PROCESSING_UNITS] + [--nodes=NODES | --processing-units=PROCESSING_UNITS + | --autoscaling-storage-target=AUTOSCALING_STORAGE_TARGET + --autoscaling-high-priority-cpu-target=AUTOSCALING_HIGH_PRIORITY_CPU_TARGET --autoscaling-total-cpu-target=AUTOSCALING_TOTAL_CPU_TARGET --autoscaling-max-nodes=AUTOSCALING_MAX_NODES --autoscaling-min-nodes=AUTOSCALING_MIN_NODES | --autoscaling-max-processing-units=AUTOSCALING_MAX_PROCESSING_UNITS --autoscaling-min-processing-units=AUTOSCALING_MIN_PROCESSING_UNITS] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -75,6 +77,42 @@ FLAGS --processing-units=PROCESSING_UNITS Number of processing units for the instance partition. + Autoscaling + + --autoscaling-storage-target=AUTOSCALING_STORAGE_TARGET + Specifies the target percentage of storage the autoscaled instance + can utilize. + + Autoscaling CPU targets. + + --autoscaling-high-priority-cpu-target=AUTOSCALING_HIGH_PRIORITY_CPU_TARGET + Specifies the target percentage of high-priority CPU the + autoscaled instance can utilize. + + --autoscaling-total-cpu-target=AUTOSCALING_TOTAL_CPU_TARGET + Specifies the target percentage of total CPU the autoscaled + instance can utilize. + + Autoscaling limits can be defined in either nodes or processing units. + + At most one of these can be specified: + + Autoscaling limits in nodes: + + --autoscaling-max-nodes=AUTOSCALING_MAX_NODES + Maximum number of nodes for the autoscaled instance. + + --autoscaling-min-nodes=AUTOSCALING_MIN_NODES + Minimum number of nodes for the autoscaled instance. + + Autoscaling limits in processing units: + + --autoscaling-max-processing-units=AUTOSCALING_MAX_PROCESSING_UNITS + Maximum number of processing units for the autoscaled instance. + + --autoscaling-min-processing-units=AUTOSCALING_MIN_PROCESSING_UNITS + Minimum number of processing units for the autoscaled instance. + 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/spanner/instances/create b/gcloud/beta/spanner/instances/create index 6a0796dce..53c0e5d5e 100644 --- a/gcloud/beta/spanner/instances/create +++ b/gcloud/beta/spanner/instances/create @@ -8,13 +8,15 @@ SYNOPSIS [--edition=EDITION] [--expire-behavior=EXPIRE_BEHAVIOR] [--instance-type=INSTANCE_TYPE] [--nodes=NODES | --processing-units=PROCESSING_UNITS - | [--autoscaling-high-priority-cpu-target=AUTOSCALING_HIGH_PRIORITY_CPU_TARGET --autoscaling-storage-target=AUTOSCALING_STORAGE_TARGET (--autoscaling-max-nodes=AUTOSCALING_MAX_NODES --autoscaling-min-nodes=AUTOSCALING_MIN_NODES | --autoscaling-max-processing-units=AUTOSCALING_MAX_PROCESSING_UNITS --autoscaling-min-processing-units=AUTOSCALING_MIN_PROCESSING_UNITS) : --asymmetric-autoscaling-option=[disable_high_priority_cpu_autoscaling=DISABLE_HIGH_PRIORITY_CPU_AUTOSCALING], + | [--autoscaling-storage-target=AUTOSCALING_STORAGE_TARGET + (--autoscaling-high-priority-cpu-target=AUTOSCALING_HIGH_PRIORITY_CPU_TARGET --autoscaling-total-cpu-target=AUTOSCALING_TOTAL_CPU_TARGET) (--autoscaling-max-nodes=AUTOSCALING_MAX_NODES --autoscaling-min-nodes=AUTOSCALING_MIN_NODES | --autoscaling-max-processing-units=AUTOSCALING_MAX_PROCESSING_UNITS --autoscaling-min-processing-units=AUTOSCALING_MIN_PROCESSING_UNITS) : --asymmetric-autoscaling-option=[disable_high_priority_cpu_autoscaling=DISABLE_HIGH_PRIORITY_CPU_AUTOSCALING], [disable_total_cpu_autoscaling=DISABLE_TOTAL_CPU_AUTOSCALING], [high_priority_cpu_target=HIGH_PRIORITY_CPU_TARGET], [location=LOCATION],[max_nodes=MAX_NODES], [max_processing_units=MAX_PROCESSING_UNITS],[min_nodes=MIN_NODES], [min_processing_units=MIN_PROCESSING_UNITS], - [total_cpu_target=TOTAL_CPU_TARGET]]] [GCLOUD_WIDE_FLAG ...] + [total_cpu_target=TOTAL_CPU_TARGET] --[no-]disable-downscaling]] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Create a Cloud Spanner instance. @@ -107,13 +109,6 @@ OPTIONAL FLAGS Autoscaling - --autoscaling-high-priority-cpu-target=AUTOSCALING_HIGH_PRIORITY_CPU_TARGET - Specifies the target percentage of high-priority CPU the autoscaled - instance can utilize. - - This flag argument must be specified if any of the other arguments - in this group are specified. - --autoscaling-storage-target=AUTOSCALING_STORAGE_TARGET Specifies the target percentage of storage the autoscaled instance can utilize. @@ -124,6 +119,23 @@ OPTIONAL FLAGS --asymmetric-autoscaling-option=[disable_high_priority_cpu_autoscaling=DISABLE_HIGH_PRIORITY_CPU_AUTOSCALING],[disable_total_cpu_autoscaling=DISABLE_TOTAL_CPU_AUTOSCALING],[high_priority_cpu_target=HIGH_PRIORITY_CPU_TARGET],[location=LOCATION],[max_nodes=MAX_NODES],[max_processing_units=MAX_PROCESSING_UNITS],[min_nodes=MIN_NODES],[min_processing_units=MIN_PROCESSING_UNITS],[total_cpu_target=TOTAL_CPU_TARGET] Specifies the asymmetric autoscaling option for the instance. + --[no-]disable-downscaling + Set the flag to disable downscaling for the autoscaled instance. + Use --disable-downscaling to enable and --no-disable-downscaling to + disable. + + Specify one or both CPU targets: + + At least one of these must be specified: + + --autoscaling-high-priority-cpu-target=AUTOSCALING_HIGH_PRIORITY_CPU_TARGET + Specifies the target percentage of high-priority CPU the + autoscaled instance can utilize. + + --autoscaling-total-cpu-target=AUTOSCALING_TOTAL_CPU_TARGET + Specifies the target percentage of total CPU the autoscaled + instance can utilize. + Autoscaling limits can be defined in either nodes or processing units. Exactly one of these must be specified: diff --git a/gcloud/beta/spanner/instances/update b/gcloud/beta/spanner/instances/update index 1a6cdbbe0..50d444590 100644 --- a/gcloud/beta/spanner/instances/update +++ b/gcloud/beta/spanner/instances/update @@ -7,7 +7,9 @@ SYNOPSIS [--description=DESCRIPTION] [--edition=EDITION] [--expire-behavior=EXPIRE_BEHAVIOR] [--instance-type=INSTANCE_TYPE] [--nodes=NODES | --processing-units=PROCESSING_UNITS - | --autoscaling-high-priority-cpu-target=AUTOSCALING_HIGH_PRIORITY_CPU_TARGET --autoscaling-storage-target=AUTOSCALING_STORAGE_TARGET --asymmetric-autoscaling-option=[disable_high_priority_cpu_autoscaling=DISABLE_HIGH_PRIORITY_CPU_AUTOSCALING], + | --autoscaling-storage-target=AUTOSCALING_STORAGE_TARGET + --[no-]disable-downscaling + --asymmetric-autoscaling-option=[disable_high_priority_cpu_autoscaling=DISABLE_HIGH_PRIORITY_CPU_AUTOSCALING], [disable_total_cpu_autoscaling=DISABLE_TOTAL_CPU_AUTOSCALING], [high_priority_cpu_target=HIGH_PRIORITY_CPU_TARGET], [location=LOCATION],[max_nodes=MAX_NODES], @@ -15,10 +17,7 @@ SYNOPSIS [min_processing_units=MIN_PROCESSING_UNITS], [total_cpu_target=TOTAL_CPU_TARGET] | --clear-asymmetric-autoscaling-option=LOCATION,[LOCATION,...] - --autoscaling-max-nodes=AUTOSCALING_MAX_NODES - --autoscaling-min-nodes=AUTOSCALING_MIN_NODES - | --autoscaling-max-processing-units=AUTOSCALING_MAX_PROCESSING_UNITS - --autoscaling-min-processing-units=AUTOSCALING_MIN_PROCESSING_UNITS] + --autoscaling-high-priority-cpu-target=AUTOSCALING_HIGH_PRIORITY_CPU_TARGET --autoscaling-total-cpu-target=AUTOSCALING_TOTAL_CPU_TARGET --autoscaling-max-nodes=AUTOSCALING_MAX_NODES --autoscaling-min-nodes=AUTOSCALING_MIN_NODES | --autoscaling-max-processing-units=AUTOSCALING_MAX_PROCESSING_UNITS --autoscaling-min-processing-units=AUTOSCALING_MIN_PROCESSING_UNITS] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -106,14 +105,15 @@ FLAGS Autoscaling - --autoscaling-high-priority-cpu-target=AUTOSCALING_HIGH_PRIORITY_CPU_TARGET - Specifies the target percentage of high-priority CPU the autoscaled - instance can utilize. - --autoscaling-storage-target=AUTOSCALING_STORAGE_TARGET Specifies the target percentage of storage the autoscaled instance can utilize. + --[no-]disable-downscaling + Set the flag to disable downscaling for the autoscaled instance. + Use --disable-downscaling to enable and --no-disable-downscaling to + disable. + At most one of these can be specified: --asymmetric-autoscaling-option=[disable_high_priority_cpu_autoscaling=DISABLE_HIGH_PRIORITY_CPU_AUTOSCALING],[disable_total_cpu_autoscaling=DISABLE_TOTAL_CPU_AUTOSCALING],[high_priority_cpu_target=HIGH_PRIORITY_CPU_TARGET],[location=LOCATION],[max_nodes=MAX_NODES],[max_processing_units=MAX_PROCESSING_UNITS],[min_nodes=MIN_NODES],[min_processing_units=MIN_PROCESSING_UNITS],[total_cpu_target=TOTAL_CPU_TARGET] @@ -123,6 +123,16 @@ FLAGS Specify a comma separated list of locations from which to remove asymmetric autoscaling options + Specify one or both CPU targets: + + --autoscaling-high-priority-cpu-target=AUTOSCALING_HIGH_PRIORITY_CPU_TARGET + Specifies the target percentage of high-priority CPU the + autoscaled instance can utilize. + + --autoscaling-total-cpu-target=AUTOSCALING_TOTAL_CPU_TARGET + Specifies the target percentage of total CPU the autoscaled + instance can utilize. + Autoscaling limits can be defined in either nodes or processing units. At most one of these can be specified: diff --git a/gcloud/beta/workbench/instances/create b/gcloud/beta/workbench/instances/create index 3a7013188..aa977a6f9 100644 --- a/gcloud/beta/workbench/instances/create +++ b/gcloud/beta/workbench/instances/create @@ -190,7 +190,7 @@ FLAGS NVIDIA_TESLA_P4, NVIDIA_TESLA_T4, NVIDIA_TESLA_A100, NVIDIA_A100_80GB, NVIDIA_TESLA_T4_VWS, NVIDIA_TESLA_P100_VWS, NVIDIA_TESLA_P4_VWS, NVIDIA_L4, NVIDIA_H100_80GB, - NVIDIA_H100_MEGA_80GB. + NVIDIA_H100_MEGA_80GB, NVIDIA_H200_141GB, NVIDIA_B200. Boot disk configurations. diff --git a/gcloud/beta/workbench/instances/update b/gcloud/beta/workbench/instances/update index 9c8c59e61..bd129128a 100644 --- a/gcloud/beta/workbench/instances/update +++ b/gcloud/beta/workbench/instances/update @@ -97,7 +97,7 @@ FLAGS NVIDIA_TESLA_P4, NVIDIA_TESLA_T4, NVIDIA_TESLA_A100, NVIDIA_A100_80GB, NVIDIA_TESLA_T4_VWS, NVIDIA_TESLA_P100_VWS, NVIDIA_TESLA_P4_VWS, NVIDIA_L4, NVIDIA_H100_80GB, - NVIDIA_H100_MEGA_80GB. + NVIDIA_H100_MEGA_80GB, NVIDIA_H200_141GB, NVIDIA_B200. Container image configurations. diff --git a/gcloud/composer/environments/create b/gcloud/composer/environments/create index 230abc01f..a5b9263ca 100644 --- a/gcloud/composer/environments/create +++ b/gcloud/composer/environments/create @@ -373,12 +373,12 @@ FLAGS --enable-ip-alias Enable use of alias IPs - (https://cloud.google.com/compute/docs/alias-ip/) for Pod IPs. This + (https://cloud.google.com/compute/docs/alias-ip) for Pod IPs. This will require at least two secondary ranges in the subnetwork, one for the pod IPs and another to reserve space for the services range. --enable-ip-masq-agent - When enabled, the IP Masquarade Agent + When enabled, the IP Masquerade Agent (https://cloud.google.com/composer/docs/enable-ip-masquerade-agent) is deployed to your environment's cluster. It performs many-to-one IP address translations to hide a pod's IP address behind the cluster @@ -454,7 +454,7 @@ FLAGS --enable-master-authorized-networks Enable Master Authorized Networks feature - (https://cloud.google.com/kubernetes-engine/docs/how-to/authorized-networks/) + (https://cloud.google.com/kubernetes-engine/docs/how-to/authorized-networks) in the Composer Environment's GKE cluster. --master-authorized-networks=[NETWORK,...] diff --git a/gcloud/composer/environments/update b/gcloud/composer/environments/update index 119cd6288..c4a9510bd 100644 --- a/gcloud/composer/environments/update +++ b/gcloud/composer/environments/update @@ -248,12 +248,12 @@ REQUIRED FLAGS --disable-master-authorized-networks Disable Master Authorized Networks feature - (https://cloud.google.com/kubernetes-engine/docs/how-to/authorized-networks/) + (https://cloud.google.com/kubernetes-engine/docs/how-to/authorized-networks) in the Composer Environment's GKE cluster. --enable-master-authorized-networks Enable Master Authorized Networks feature - (https://cloud.google.com/kubernetes-engine/docs/how-to/authorized-networks/) + (https://cloud.google.com/kubernetes-engine/docs/how-to/authorized-networks) in the Composer Environment's GKE cluster. --master-authorized-networks=[NETWORK,...] diff --git a/gcloud/compute/backend-services/import b/gcloud/compute/backend-services/import index 3683edf89..8788b6057 100644 --- a/gcloud/compute/backend-services/import +++ b/gcloud/compute/backend-services/import @@ -21,8 +21,8 @@ POSITIONAL ARGUMENTS FLAGS --source=SOURCE Path to a YAML file containing configuration export data. - Alternatively, you may omit this flag to read from standard input.For a - schema describing the export/import format, see: + Alternatively, you may omit this flag to read from standard input. For + a schema describing the export/import format, see: $CLOUDSDKROOT/lib/googlecloudsdk/schemas/compute/v1/BackendService.yaml. Note: $CLOUDSDKROOT represents the Google Cloud CLI's installation directory. diff --git a/gcloud/compute/commitments/create b/gcloud/compute/commitments/create index a9a40a81e..822a4bb51 100644 --- a/gcloud/compute/commitments/create +++ b/gcloud/compute/commitments/create @@ -111,8 +111,11 @@ OPTIONAL FLAGS general-purpose-n2d, general-purpose-n4, general-purpose-n4d, general-purpose-t2d, graphics-optimized, graphics-optimized-g4, memory-optimized, memory-optimized-m3, memory-optimized-m4, - memory-optimized-m4-6tb, memory-optimized-x4-16tb, + memory-optimized-m4-6tb, memory-optimized-x4-1440-24t, + memory-optimized-x4-16tb, memory-optimized-x4-1920-32t, memory-optimized-x4-24tb, memory-optimized-x4-32tb, + memory-optimized-x4-480-6t, memory-optimized-x4-480-8t, + memory-optimized-x4-960-12t, memory-optimized-x4-960-16t, storage-optimized-z3. Manage the reservations to be created with the commitment. diff --git a/gcloud/compute/firewall-policies/import-rules b/gcloud/compute/firewall-policies/import-rules index 05c47df6f..739e50225 100644 --- a/gcloud/compute/firewall-policies/import-rules +++ b/gcloud/compute/firewall-policies/import-rules @@ -26,8 +26,8 @@ FLAGS --source=SOURCE Path to a YAML file containing configuration export data. - Alternatively, you may omit this flag to read from standard input.For a - schema describing the export/import format, see: + Alternatively, you may omit this flag to read from standard input. For + a schema describing the export/import format, see: $CLOUDSDKROOT/lib/googlecloudsdk/schemas/compute/v1/FirewallPolicy.yaml. Note: $CLOUDSDKROOT represents the Google Cloud CLI's installation directory. diff --git a/gcloud/compute/forwarding-rules/import b/gcloud/compute/forwarding-rules/import index 218af1285..beca5f6f8 100644 --- a/gcloud/compute/forwarding-rules/import +++ b/gcloud/compute/forwarding-rules/import @@ -20,8 +20,8 @@ POSITIONAL ARGUMENTS FLAGS --source=SOURCE Path to a YAML file containing configuration export data. - Alternatively, you may omit this flag to read from standard input.For a - schema describing the export/import format, see: + Alternatively, you may omit this flag to read from standard input. For + a schema describing the export/import format, see: $CLOUDSDKROOT/lib/googlecloudsdk/schemas/compute/v1/ForwardingRule.yaml. Note: $CLOUDSDKROOT represents the Google Cloud CLI's installation directory. diff --git a/gcloud/compute/instances/update-from-file b/gcloud/compute/instances/update-from-file index b9dee7654..c70dba0f8 100644 --- a/gcloud/compute/instances/update-from-file +++ b/gcloud/compute/instances/update-from-file @@ -39,8 +39,8 @@ FLAGS --source=SOURCE Path to a YAML file containing configuration export data. - Alternatively, you may omit this flag to read from standard input.For a - schema describing the export/import format, see: + Alternatively, you may omit this flag to read from standard input. For + a schema describing the export/import format, see: $CLOUDSDKROOT/lib/googlecloudsdk/schemas/compute/v1/Instance.yaml. Note: $CLOUDSDKROOT represents the Google Cloud CLI's installation directory. diff --git a/gcloud/compute/network-firewall-policies/import-rules b/gcloud/compute/network-firewall-policies/import-rules index a9485349c..12926950a 100644 --- a/gcloud/compute/network-firewall-policies/import-rules +++ b/gcloud/compute/network-firewall-policies/import-rules @@ -22,8 +22,8 @@ POSITIONAL ARGUMENTS FLAGS --source=SOURCE Path to a YAML file containing configuration export data. - Alternatively, you may omit this flag to read from standard input.For a - schema describing the export/import format, see: + Alternatively, you may omit this flag to read from standard input. For + a schema describing the export/import format, see: $CLOUDSDKROOT/lib/googlecloudsdk/schemas/compute/v1/FirewallPolicy.yaml. Note: $CLOUDSDKROOT represents the Google Cloud CLI's installation directory. diff --git a/gcloud/compute/project-info/help b/gcloud/compute/project-info/help index 159cb0517..b40019a09 100644 --- a/gcloud/compute/project-info/help +++ b/gcloud/compute/project-info/help @@ -39,7 +39,7 @@ COMMANDS Remove project-wide metadata entries. set-usage-bucket - Set usage reporting bucket for a project. + (DEPRECATED) Set usage reporting bucket for a project. update Update a Compute Engine project resource. diff --git a/gcloud/compute/project-info/set-usage-bucket b/gcloud/compute/project-info/set-usage-bucket index 7ef94e6a9..b68d7f668 100644 --- a/gcloud/compute/project-info/set-usage-bucket +++ b/gcloud/compute/project-info/set-usage-bucket @@ -8,6 +8,11 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION + (DEPRECATED) Set usage reporting bucket for a project. + + This command is deprecated. Please onboard with BigQuery Export instead. + https://docs.cloud.google.com/billing/docs/how-to/export-data-bigquery + gcloud compute project-info set-usage-bucket configures usage reporting for projects. diff --git a/gcloud/compute/target-http-proxies/import b/gcloud/compute/target-http-proxies/import index 342c2ee9b..6a14d342e 100644 --- a/gcloud/compute/target-http-proxies/import +++ b/gcloud/compute/target-http-proxies/import @@ -21,8 +21,8 @@ POSITIONAL ARGUMENTS FLAGS --source=SOURCE Path to a YAML file containing configuration export data. - Alternatively, you may omit this flag to read from standard input.For a - schema describing the export/import format, see: + Alternatively, you may omit this flag to read from standard input. For + a schema describing the export/import format, see: $CLOUDSDKROOT/lib/googlecloudsdk/schemas/compute/v1/TargetHttpProxy.yaml. Note: $CLOUDSDKROOT represents the Google Cloud CLI's installation directory. diff --git a/gcloud/compute/target-https-proxies/import b/gcloud/compute/target-https-proxies/import index ff2990222..3759dd2a7 100644 --- a/gcloud/compute/target-https-proxies/import +++ b/gcloud/compute/target-https-proxies/import @@ -26,8 +26,8 @@ POSITIONAL ARGUMENTS FLAGS --source=SOURCE Path to a YAML file containing configuration export data. - Alternatively, you may omit this flag to read from standard input.For a - schema describing the export/import format, see: + Alternatively, you may omit this flag to read from standard input. For + a schema describing the export/import format, see: $CLOUDSDKROOT/lib/googlecloudsdk/schemas/compute/v1/TargetHttpsProxy.yaml. Note: $CLOUDSDKROOT represents the Google Cloud CLI's installation directory. diff --git a/gcloud/compute/url-maps/import b/gcloud/compute/url-maps/import index d805cc47e..01a26e519 100644 --- a/gcloud/compute/url-maps/import +++ b/gcloud/compute/url-maps/import @@ -20,8 +20,8 @@ POSITIONAL ARGUMENTS FLAGS --source=SOURCE Path to a YAML file containing configuration export data. - Alternatively, you may omit this flag to read from standard input.For a - schema describing the export/import format, see: + Alternatively, you may omit this flag to read from standard input. For + a schema describing the export/import format, see: $CLOUDSDKROOT/lib/googlecloudsdk/schemas/compute/v1/UrlMap.yaml. Note: $CLOUDSDKROOT represents the Google Cloud CLI's installation directory. diff --git a/gcloud/config/get b/gcloud/config/get index 9be0d08d3..d52ad3995 100644 --- a/gcloud/config/get +++ b/gcloud/config/get @@ -232,6 +232,10 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud certificate-manager command group. Defaults to https://certificatemanager.googleapis.com/ + cloudapiregistry + Overrides API endpoint for gcloud api-registry command group. + Defaults to https://cloudapiregistry.googleapis.com/ + cloudasset Overrides API endpoint for gcloud asset command group. Defaults to https://cloudasset.googleapis.com/ diff --git a/gcloud/config/help b/gcloud/config/help index 37e1e08b4..06e7f41e9 100644 --- a/gcloud/config/help +++ b/gcloud/config/help @@ -264,6 +264,10 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud certificate-manager command group. Defaults to https://certificatemanager.googleapis.com/ + cloudapiregistry + Overrides API endpoint for gcloud api-registry command group. + Defaults to https://cloudapiregistry.googleapis.com/ + cloudasset Overrides API endpoint for gcloud asset command group. Defaults to https://cloudasset.googleapis.com/ diff --git a/gcloud/config/list b/gcloud/config/list index ea04f6237..a216a8758 100644 --- a/gcloud/config/list +++ b/gcloud/config/list @@ -276,6 +276,10 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud certificate-manager command group. Defaults to https://certificatemanager.googleapis.com/ + cloudapiregistry + Overrides API endpoint for gcloud api-registry command group. + Defaults to https://cloudapiregistry.googleapis.com/ + cloudasset Overrides API endpoint for gcloud asset command group. Defaults to https://cloudasset.googleapis.com/ diff --git a/gcloud/config/set b/gcloud/config/set index a55f97195..81790b736 100644 --- a/gcloud/config/set +++ b/gcloud/config/set @@ -279,6 +279,10 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud certificate-manager command group. Defaults to https://certificatemanager.googleapis.com/ + cloudapiregistry + Overrides API endpoint for gcloud api-registry command group. + Defaults to https://cloudapiregistry.googleapis.com/ + cloudasset Overrides API endpoint for gcloud asset command group. Defaults to https://cloudasset.googleapis.com/ diff --git a/gcloud/config/unset b/gcloud/config/unset index 3cae890b9..e9cbf826f 100644 --- a/gcloud/config/unset +++ b/gcloud/config/unset @@ -240,6 +240,10 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud certificate-manager command group. Defaults to https://certificatemanager.googleapis.com/ + cloudapiregistry + Overrides API endpoint for gcloud api-registry command group. + Defaults to https://cloudapiregistry.googleapis.com/ + cloudasset Overrides API endpoint for gcloud asset command group. Defaults to https://cloudasset.googleapis.com/ diff --git a/gcloud/container/clusters/create b/gcloud/container/clusters/create index c9baee516..92a7575c3 100644 --- a/gcloud/container/clusters/create +++ b/gcloud/container/clusters/create @@ -241,7 +241,7 @@ FLAGS KubernetesDashboard, NetworkPolicy, NodeLocalDNS, ConfigConnector, GcePersistentDiskCsiDriver, GcpFilestoreCsiDriver, BackupRestore, GcsFuseCsiDriver, ParallelstoreCsiDriver, HighScaleCheckpointing, - LustreCsiDriver, RayOperator, CloudRun. + LustreCsiDriver, RayOperator, SlurmOperator, CloudRun. --alpha-cluster-feature-gates=[FEATURE=true|false,...] Selectively enable or disable Kubernetes alpha and beta @@ -398,7 +398,7 @@ FLAGS --confidential-node-type=CONFIDENTIAL_NODE_TYPE Enable confidential nodes for the cluster. Enabling Confidential Nodes will create nodes using Confidential VM - https://cloud.google.com/compute/confidential-vm/docs/about-cvm. + https://docs.cloud.google.com/compute/docs/about-confidential-vm. CONFIDENTIAL_NODE_TYPE must be one of: sev, sev_snp, tdx. --containerd-config-from-file=PATH_TO_FILE @@ -578,7 +578,7 @@ FLAGS --enable-confidential-nodes Enable confidential nodes for the cluster. Enabling Confidential Nodes will create nodes using Confidential VM - https://cloud.google.com/compute/confidential-vm/docs/about-cvm. + https://docs.cloud.google.com/compute/docs/about-confidential-vm. --enable-confidential-storage Enable confidential storage for the cluster. Enabling Confidential @@ -1649,7 +1649,10 @@ FLAGS [65536, 2147483647] vm.overcommit_memory Must be one of {0, - 1, 2} + 1, 2}. Not + supported on + machines with less + than 15 GB memory. vm.overcommit_ratio Must be between [0, 100] vm.vfs_cache_pressure Must be between @@ -1707,9 +1710,15 @@ FLAGS KEY VALUE diskCount integer - Allocated hugepage size should not exceed 60% of available memory on - the node. For example, c2d-highcpu-4 has 8GB memory, total allocated - hugepage of 2m and 1g should not exceed 8GB * 0.6 = 4.8GB. + The upper limit for total allocated hugepage size differs based upon + machine size. + + ◆ On machines with less than 30 GB memory: 60% of the total memory. + For example, on e2-standard-2 machine with 8 GB of memory, you can't + allocate more than 4.8 GB for hugepages. + ◆ On machines with more than 30 GB memory: 80% of the total memory. + For example, on c4a-standard-8 machines with 32 GB of memory, + hugepages cannot exceed 25.6 GB. 1G hugepages are only available in following machine familes: c3, m2, c2d, c3d, h3, m3, a2, a3, g2. diff --git a/gcloud/container/clusters/create-auto b/gcloud/container/clusters/create-auto index 91d60260b..79069b0ef 100644 --- a/gcloud/container/clusters/create-auto +++ b/gcloud/container/clusters/create-auto @@ -289,7 +289,7 @@ FLAGS --enable-confidential-nodes Enable confidential nodes for the cluster. Enabling Confidential Nodes will create nodes using Confidential VM - https://cloud.google.com/compute/confidential-vm/docs/about-cvm. + https://docs.cloud.google.com/compute/docs/about-confidential-vm. --enable-default-compute-class Enable the default compute class to use for the cluster. diff --git a/gcloud/container/node-pools/create b/gcloud/container/node-pools/create index 3cc27f1d6..b0854c44a 100644 --- a/gcloud/container/node-pools/create +++ b/gcloud/container/node-pools/create @@ -74,6 +74,9 @@ SYNOPSIS | --local-nvme-ssd-block[=[count=COUNT]] | --local-ssd-count=LOCAL_SSD_COUNT] [--location=LOCATION | --region=REGION | --zone=ZONE, -z ZONE] + [--node-drain-grace-period-seconds=NODE_DRAIN_GRACE_PERIOD_SECONDS + --node-drain-pdb-timeout-seconds=NODE_DRAIN_PDB_TIMEOUT_SECONDS + --respect-pdb-during-node-pool-deletion] [--reservation=RESERVATION --reservation-affinity=RESERVATION_AFFINITY] [--scopes=[SCOPE,...]; default="gke-default" --service-account=SERVICE_ACCOUNT] @@ -222,7 +225,7 @@ FLAGS --confidential-node-type=CONFIDENTIAL_NODE_TYPE Enable confidential nodes for the node pool. Enabling Confidential Nodes will create nodes using Confidential VM - https://cloud.google.com/compute/confidential-vm/docs/about-cvm. + https://docs.cloud.google.com/compute/docs/about-confidential-vm. CONFIDENTIAL_NODE_TYPE must be one of: sev, sev_snp, tdx, disabled. --containerd-config-from-file=PATH_TO_FILE @@ -290,7 +293,7 @@ FLAGS --enable-confidential-nodes Enable confidential nodes for the node pool. Enabling Confidential Nodes will create nodes using Confidential VM - https://cloud.google.com/compute/confidential-vm/docs/about-cvm. + https://docs.cloud.google.com/compute/docs/about-confidential-vm. --enable-confidential-storage Enable confidential storage for the node pool. Enabling Confidential @@ -1065,7 +1068,10 @@ FLAGS [65536, 2147483647] vm.overcommit_memory Must be one of {0, - 1, 2} + 1, 2}. Not + supported on + machines with less + than 15 GB memory. vm.overcommit_ratio Must be between [0, 100] vm.vfs_cache_pressure Must be between @@ -1123,9 +1129,15 @@ FLAGS KEY VALUE diskCount integer - Allocated hugepage size should not exceed 60% of available memory on - the node. For example, c2d-highcpu-4 has 8GB memory, total allocated - hugepage of 2m and 1g should not exceed 8GB * 0.6 = 4.8GB. + The upper limit for total allocated hugepage size differs based upon + machine size. + + ◆ On machines with less than 30 GB memory: 60% of the total memory. + For example, on e2-standard-2 machine with 8 GB of memory, you can't + allocate more than 4.8 GB for hugepages. + ◆ On machines with more than 30 GB memory: 80% of the total memory. + For example, on c4a-standard-8 machines with 32 GB of memory, + hugepages cannot exceed 25.6 GB. 1G hugepages are only available in following machine familes: c3, m2, c2d, c3d, h3, m3, a2, a3, g2. @@ -1412,6 +1424,18 @@ FLAGS Compute zone (e.g. us-central1-a) for a zonal cluster. Overrides the default compute/zone property value for this command invocation. + Node drain settings + + --node-drain-grace-period-seconds=NODE_DRAIN_GRACE_PERIOD_SECONDS + The grace period in seconds for nodes to drain before being + forcefully removed. + + --node-drain-pdb-timeout-seconds=NODE_DRAIN_PDB_TIMEOUT_SECONDS + The timeout in seconds for the node pool to be drained. + + --respect-pdb-during-node-pool-deletion + Whether to respect PDBs when deleting nodes in the node pool. + Specifies the reservation for the node pool. --reservation=RESERVATION diff --git a/gcloud/container/node-pools/update b/gcloud/container/node-pools/update index 66e6c71bc..c4c010163 100644 --- a/gcloud/container/node-pools/update +++ b/gcloud/container/node-pools/update @@ -37,7 +37,10 @@ SYNOPSIS --location-policy=LOCATION_POLICY --max-nodes=MAX_NODES --min-nodes=MIN_NODES --total-max-nodes=TOTAL_MAX_NODES --total-min-nodes=TOTAL_MIN_NODES - | --enable-autorepair --enable-autoupgrade) [--async] + | --enable-autorepair --enable-autoupgrade + | --node-drain-grace-period-seconds=NODE_DRAIN_GRACE_PERIOD_SECONDS + --node-drain-pdb-timeout-seconds=NODE_DRAIN_PDB_TIMEOUT_SECONDS + --respect-pdb-during-node-pool-deletion) [--async] [--cluster=CLUSTER] [--location=LOCATION | --region=REGION | --zone=ZONE, -z ZONE] [GCLOUD_WIDE_FLAG ...] @@ -104,7 +107,7 @@ REQUIRED FLAGS --confidential-node-type=CONFIDENTIAL_NODE_TYPE Recreate all the nodes in the node pool to be confidential VM - https://cloud.google.com/compute/confidential-vm/docs/about-cvm. + https://docs.cloud.google.com/compute/docs/about-confidential-vm. CONFIDENTIAL_NODE_TYPE must be one of: sev, sev_snp, tdx, disabled. --containerd-config-from-file=PATH_TO_FILE @@ -123,7 +126,7 @@ REQUIRED FLAGS --enable-confidential-nodes Recreate all the nodes in the node pool to be confidential VM - https://cloud.google.com/compute/confidential-vm/docs/about-cvm. + https://docs.cloud.google.com/compute/docs/about-confidential-vm. --enable-gvnic Enable the use of GVNIC for this cluster. Requires re-creation of @@ -608,7 +611,11 @@ REQUIRED FLAGS [65536, 2147483647] vm.overcommit_memory Must be one of - {0, 1, 2} + {0, 1, 2}. Not + supported on + machines with + less than 15 GB + memory. vm.overcommit_ratio Must be between [0, 100] vm.vfs_cache_pressure Must be between @@ -666,9 +673,15 @@ REQUIRED FLAGS KEY VALUE diskCount integer - Allocated hugepage size should not exceed 60% of available memory on - the node. For example, c2d-highcpu-4 has 8GB memory, total allocated - hugepage of 2m and 1g should not exceed 8GB * 0.6 = 4.8GB. + The upper limit for total allocated hugepage size differs based upon + machine size. + + ▸ On machines with less than 30 GB memory: 60% of the total memory. + For example, on e2-standard-2 machine with 8 GB of memory, you + can't allocate more than 4.8 GB for hugepages. + ▸ On machines with more than 30 GB memory: 80% of the total memory. + For example, on c4a-standard-8 machines with 32 GB of memory, + hugepages cannot exceed 25.6 GB. 1G hugepages are only available in following machine familes: c3, m2, c2d, c3d, h3, m3, a2, a3, g2. @@ -964,6 +977,18 @@ REQUIRED FLAGS https://cloud.google.com/kubernetes-engine/docs/node-auto-upgrades for more info. + Node drain settings + + --node-drain-grace-period-seconds=NODE_DRAIN_GRACE_PERIOD_SECONDS + The grace period in seconds for nodes to drain before being + forcefully removed. + + --node-drain-pdb-timeout-seconds=NODE_DRAIN_PDB_TIMEOUT_SECONDS + The timeout in seconds for the node pool to be drained. + + --respect-pdb-during-node-pool-deletion + Whether to respect PDBs when deleting nodes in the node pool. + OPTIONAL FLAGS --async Return immediately, without waiting for the operation in progress to diff --git a/gcloud/dataplex/datascans/create/data-documentation b/gcloud/dataplex/datascans/create/data-documentation index f0705f6c6..479f99877 100644 --- a/gcloud/dataplex/datascans/create/data-documentation +++ b/gcloud/dataplex/datascans/create/data-documentation @@ -9,7 +9,9 @@ SYNOPSIS | --data-source-resource=DATA_SOURCE_RESOURCE) [--description=DESCRIPTION] [--display-name=DISPLAY_NAME] [--labels=[KEY=VALUE,...]] [--async | --validate-only] - [--on-demand=ON_DEMAND | --schedule=SCHEDULE] [GCLOUD_WIDE_FLAG ...] + [--on-demand=ON_DEMAND | --schedule=SCHEDULE + | --one-time --ttl-after-scan-completion=TTL_AFTER_SCAN_COMPLETION] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION Allows users to generate documentation for Dataplex BigQuery tables. @@ -101,7 +103,7 @@ OPTIONAL FLAGS Data documentation scan execution settings. - Data documentation scan scheduling and trigger settings. + Data documentation scan trigger settings. At most one of these can be specified: @@ -116,7 +118,24 @@ OPTIONAL FLAGS "TZ=${IANA_TIME_ZONE}". The ${IANA_TIME_ZONE} may only be a valid string from IANA time zone database. For example, CRON_TZ=America/New_York 1 * * * * or TZ=America/New_York 1 * * * - *. This field is required for RECURRING scans. + *. This field is required for RECURRING scans. The argument is only + valid when --on-demand is not set. + + Data documentation scan one-time trigger settings. + + --one-time + If set, the data documentation scan runs once, and is + auto-deleted once the ttl_after_scan_completion expires. + + --ttl-after-scan-completion=TTL_AFTER_SCAN_COMPLETION + The time to live for one-time scans. Default value is 24 hours, + minimum value is 0 seconds, and maximum value is 365 days. The + time is calculated from the data scan job completion time. If + value is set as 0 seconds, the scan will be immediately deleted + upon job completion, regardless of whether the job succeeded or + failed. The value should be a number followed by a unit suffix + "s". Example: "100s" for 100 seconds. The argument is only valid + when --one-time is set. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/dataplex/datascans/create/data-profile b/gcloud/dataplex/datascans/create/data-profile index bebb1df40..6486eddab 100644 --- a/gcloud/dataplex/datascans/create/data-profile +++ b/gcloud/dataplex/datascans/create/data-profile @@ -10,7 +10,8 @@ SYNOPSIS [--description=DESCRIPTION] [--display-name=DISPLAY_NAME] [--labels=[KEY=VALUE,...]] [--async | --validate-only] [--data-profile-spec-file=DATA_PROFILE_SPEC_FILE - | --exclude-field-names=EXCLUDE_FIELD_NAMES + | --enable-catalog-publishing + --exclude-field-names=EXCLUDE_FIELD_NAMES --export-results-table=EXPORT_RESULTS_TABLE --include-field-names=INCLUDE_FIELD_NAMES --row-filter=ROW_FILTER --sampling-percent=SAMPLING_PERCENT] @@ -120,6 +121,9 @@ OPTIONAL FLAGS Command line spec arguments for the data profile scan. + --enable-catalog-publishing + Publish data profile results to Dataplex catalog. + --exclude-field-names=EXCLUDE_FIELD_NAMES Names of the fields to exclude from data profile. If specified, the respective fields will be excluded from data profile, regardless of diff --git a/gcloud/dataplex/datascans/update/data-documentation b/gcloud/dataplex/datascans/update/data-documentation index 38104d250..1b6936690 100644 --- a/gcloud/dataplex/datascans/update/data-documentation +++ b/gcloud/dataplex/datascans/update/data-documentation @@ -7,7 +7,9 @@ SYNOPSIS (DATASCAN : --location=LOCATION) [--description=DESCRIPTION] [--display-name=DISPLAY_NAME] [--labels=[KEY=VALUE,...]] [--async | --validate-only] - [--on-demand=ON_DEMAND | --schedule=SCHEDULE] [GCLOUD_WIDE_FLAG ...] + [--on-demand=ON_DEMAND | --schedule=SCHEDULE + | --one-time --ttl-after-scan-completion=TTL_AFTER_SCAN_COMPLETION] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION Update a Dataplex data documentation scan job. @@ -81,7 +83,7 @@ FLAGS Data documentation scan execution settings. - Data documentation scan scheduling and trigger settings. + Data documentation scan trigger settings. At most one of these can be specified: @@ -98,6 +100,22 @@ FLAGS CRON_TZ=America/New_York 1 * * * * or TZ=America/New_York 1 * * * *. This field is required for RECURRING scans. + Data documentation scan one-time trigger settings. + + --one-time + If set, the data documentation scan runs once, and auto deleted + once the ttl_after_scan_completion expires. + + --ttl-after-scan-completion=TTL_AFTER_SCAN_COMPLETION + The time to live for one-time scans. Default value is 24 hours, + minimum value is 0 seconds, and maximum value is 365 days. The + time is calculated from the data scan job completion time. If + value is set as 0 seconds, the scan will be immediately deleted + upon job completion, regardless of whether the job succeeded or + failed. The value should be a number followed by a unit suffix + "s". Example: "100s" for 100 seconds. The argument is only valid + when --one-time is set. + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/dataplex/datascans/update/data-profile b/gcloud/dataplex/datascans/update/data-profile index 38ccc07e5..734d29c22 100644 --- a/gcloud/dataplex/datascans/update/data-profile +++ b/gcloud/dataplex/datascans/update/data-profile @@ -8,7 +8,8 @@ SYNOPSIS [--display-name=DISPLAY_NAME] [--labels=[KEY=VALUE,...]] [--async | --validate-only] [--data-profile-spec-file=DATA_PROFILE_SPEC_FILE - | --exclude-field-names=EXCLUDE_FIELD_NAMES + | --enable-catalog-publishing + --exclude-field-names=EXCLUDE_FIELD_NAMES --include-field-names=INCLUDE_FIELD_NAMES --row-filter=ROW_FILTER --sampling-percent=SAMPLING_PERCENT] [--on-demand=ON_DEMAND | --schedule=SCHEDULE] [GCLOUD_WIDE_FLAG ...] @@ -96,6 +97,9 @@ FLAGS Command line spec arguments for the data profile scan. + --enable-catalog-publishing + Publish data profile results to Dataplex catalog. + --exclude-field-names=EXCLUDE_FIELD_NAMES Names of the fields to exclude from data profile. If specified, the respective fields will be excluded from data profile, regardless of diff --git a/gcloud/datastream/connection-profiles/create b/gcloud/datastream/connection-profiles/create index fe7769a69..2812237ba 100644 --- a/gcloud/datastream/connection-profiles/create +++ b/gcloud/datastream/connection-profiles/create @@ -14,7 +14,14 @@ SYNOPSIS | --oracle-secret-manager-stored-password=ORACLE_SECRET_MANAGER_STORED_PASSWORD) : --oracle-ca-certificate=ORACLE_CA_CERTIFICATE --oracle-server-certificate-distinguished-name=ORACLE_SERVER_CERTIFICATE_DISTINGUISHED_NAME] | [--mongodb-host-addresses=IPv4_ADDRESS_OR_HOSTNAME:PORT, [...] --mongodb-username=MONGODB_USERNAME (--mongodb-password=MONGODB_PASSWORD | --mongodb-prompt-for-password - | --mongodb-secret-manager-stored-password=MONGODB_SECRET_MANAGER_STORED_PASSWORD) (--mongodb-srv-connection-format | --mongodb-standard-connection-format) : --mongodb-direct-connection --mongodb-replica-set=MONGODB_REPLICA_SET --mongodb-ca-certificate=MONGODB_CA_CERTIFICATE --mongodb-tls] | [--mysql-hostname=MYSQL_HOSTNAME --mysql-port=MYSQL_PORT --mysql-username=MYSQL_USERNAME (--mysql-password=MYSQL_PASSWORD | --mysql-prompt-for-password | --mysql-secret-manager-stored-password=MYSQL_SECRET_MANAGER_STORED_PASSWORD) : --ca-certificate=CA_CERTIFICATE --client-certificate=CLIENT_CERTIFICATE --client-key=CLIENT_KEY] | [--postgresql-database=POSTGRESQL_DATABASE --postgresql-hostname=POSTGRESQL_HOSTNAME --postgresql-port=POSTGRESQL_PORT --postgresql-username=POSTGRESQL_USERNAME (--postgresql-password=POSTGRESQL_PASSWORD | --postgresql-prompt-for-password | --postgresql-secret-manager-stored-password=POSTGRESQL_SECRET_MANAGER_STORED_PASSWORD) : [--postgresql-ca-certificate=POSTGRESQL_CA_CERTIFICATE : --postgresql-server-certificate-hostname=POSTGRESQL_SERVER_CERTIFICATE_HOSTNAME --postgresql-client-certificate=POSTGRESQL_CLIENT_CERTIFICATE --postgresql-client-key=POSTGRESQL_CLIENT_KEY]] | --salesforce-domain=SALESFORCE_DOMAIN (--salesforce-oauth2-client-id=SALESFORCE_OAUTH2_CLIENT_ID (--salesforce-oauth2-client-secret=SALESFORCE_OAUTH2_CLIENT_SECRET | --salesforce-prompt-for-oauth2-client-secret | --salesforce-secret-manager-stored-oauth2-client-secret=SALESFORCE_SECRET_MANAGER_STORED_OAUTH2_CLIENT_SECRET) | --salesforce-username=SALESFORCE_USERNAME (--salesforce-password=SALESFORCE_PASSWORD | --salesforce-prompt-for-password | --salesforce-secret-manager-stored-password=SALESFORCE_SECRET_MANAGER_STORED_PASSWORD) (--salesforce-prompt-for-security-token | --salesforce-secret-manager-stored-security-token=SALESFORCE_SECRET_MANAGER_STORED_SECURITY_TOKEN | --salesforce-security-token=SALESFORCE_SECURITY_TOKEN)) | --sqlserver-database=SQLSERVER_DATABASE --sqlserver-hostname=SQLSERVER_HOSTNAME --sqlserver-port=SQLSERVER_PORT --sqlserver-username=SQLSERVER_USERNAME (--sqlserver-password=SQLSERVER_PASSWORD | --sqlserver-prompt-for-password | --sqlserver-secret-manager-stored-password=SQLSERVER_SECRET_MANAGER_STORED_PASSWORD)] + | --mongodb-secret-manager-stored-password=MONGODB_SECRET_MANAGER_STORED_PASSWORD) (--mongodb-srv-connection-format | --mongodb-standard-connection-format) : --mongodb-additional-options=[MONGODB_PROFILE_ADDITIONAL_OPTIONS, + ...] --mongodb-direct-connection + --mongodb-replica-set=MONGODB_REPLICA_SET + --mongodb-ca-certificate=MONGODB_CA_CERTIFICATE --mongodb-tls] + | [--mysql-hostname=MYSQL_HOSTNAME --mysql-port=MYSQL_PORT + --mysql-username=MYSQL_USERNAME (--mysql-password=MYSQL_PASSWORD + | --mysql-prompt-for-password + | --mysql-secret-manager-stored-password=MYSQL_SECRET_MANAGER_STORED_PASSWORD) : --ca-certificate=CA_CERTIFICATE --client-certificate=CLIENT_CERTIFICATE --client-key=CLIENT_KEY] | [--postgresql-database=POSTGRESQL_DATABASE --postgresql-hostname=POSTGRESQL_HOSTNAME --postgresql-port=POSTGRESQL_PORT --postgresql-username=POSTGRESQL_USERNAME (--postgresql-password=POSTGRESQL_PASSWORD | --postgresql-prompt-for-password | --postgresql-secret-manager-stored-password=POSTGRESQL_SECRET_MANAGER_STORED_PASSWORD) : [--postgresql-ca-certificate=POSTGRESQL_CA_CERTIFICATE : --postgresql-server-certificate-hostname=POSTGRESQL_SERVER_CERTIFICATE_HOSTNAME --postgresql-client-certificate=POSTGRESQL_CLIENT_CERTIFICATE --postgresql-client-key=POSTGRESQL_CLIENT_KEY]] | --salesforce-domain=SALESFORCE_DOMAIN (--salesforce-oauth2-client-id=SALESFORCE_OAUTH2_CLIENT_ID (--salesforce-oauth2-client-secret=SALESFORCE_OAUTH2_CLIENT_SECRET | --salesforce-prompt-for-oauth2-client-secret | --salesforce-secret-manager-stored-oauth2-client-secret=SALESFORCE_SECRET_MANAGER_STORED_OAUTH2_CLIENT_SECRET) | --salesforce-username=SALESFORCE_USERNAME (--salesforce-password=SALESFORCE_PASSWORD | --salesforce-prompt-for-password | --salesforce-secret-manager-stored-password=SALESFORCE_SECRET_MANAGER_STORED_PASSWORD) (--salesforce-prompt-for-security-token | --salesforce-secret-manager-stored-security-token=SALESFORCE_SECRET_MANAGER_STORED_SECURITY_TOKEN | --salesforce-security-token=SALESFORCE_SECURITY_TOKEN)) | --sqlserver-database=SQLSERVER_DATABASE --sqlserver-hostname=SQLSERVER_HOSTNAME --sqlserver-port=SQLSERVER_PORT --sqlserver-username=SQLSERVER_USERNAME (--sqlserver-password=SQLSERVER_PASSWORD | --sqlserver-prompt-for-password | --sqlserver-secret-manager-stored-password=SQLSERVER_SECRET_MANAGER_STORED_PASSWORD)] [--private-connection=PRIVATE_CONNECTION | --static-ip-connectivity | [--forward-ssh-hostname=FORWARD_SSH_HOSTNAME --forward-ssh-username=FORWARD_SSH_USERNAME @@ -227,6 +234,9 @@ OPTIONAL FLAGS This flag argument must be specified if any of the other arguments in this group are specified. + --mongodb-additional-options=[MONGODB_PROFILE_ADDITIONAL_OPTIONS,...] + Specifies additional options for the MongoDB connection. + --mongodb-direct-connection Connect to the mongodb hosts directly and do not try to resolve any of the replicas from the replica set. diff --git a/gcloud/datastream/connection-profiles/update b/gcloud/datastream/connection-profiles/update index f48219e9e..3bff0fb57 100644 --- a/gcloud/datastream/connection-profiles/update +++ b/gcloud/datastream/connection-profiles/update @@ -12,8 +12,10 @@ SYNOPSIS --oracle-hostname=ORACLE_HOSTNAME --oracle-port=ORACLE_PORT --oracle-username=ORACLE_USERNAME --oracle-ca-certificate=ORACLE_CA_CERTIFICATE - --oracle-server-certificate-distinguished-name=ORACLE_SERVER_CERTIFICATE_DISTINGUISHED_NAME --oracle-password=ORACLE_PASSWORD | --oracle-prompt-for-password | --oracle-secret-manager-stored-password=ORACLE_SECRET_MANAGER_STORED_PASSWORD | --mongodb-direct-connection --mongodb-host-addresses=IPv4_ADDRESS_OR_HOSTNAME:PORT, - [...] --mongodb-replica-set=MONGODB_REPLICA_SET + --oracle-server-certificate-distinguished-name=ORACLE_SERVER_CERTIFICATE_DISTINGUISHED_NAME --oracle-password=ORACLE_PASSWORD | --oracle-prompt-for-password | --oracle-secret-manager-stored-password=ORACLE_SECRET_MANAGER_STORED_PASSWORD | --mongodb-additional-options=[MONGODB_PROFILE_ADDITIONAL_OPTIONS, + ...] --mongodb-direct-connection + --mongodb-host-addresses=IPv4_ADDRESS_OR_HOSTNAME:PORT,[...] + --mongodb-replica-set=MONGODB_REPLICA_SET --mongodb-username=MONGODB_USERNAME --mongodb-ca-certificate=MONGODB_CA_CERTIFICATE --mongodb-tls --mongodb-password=MONGODB_PASSWORD @@ -194,6 +196,9 @@ OPTIONAL FLAGS Path to secret manager, storing the password for the user used to connect to the database. + --mongodb-additional-options=[MONGODB_PROFILE_ADDITIONAL_OPTIONS,...] + Specifies additional options for the MongoDB connection. + --mongodb-direct-connection Connect to the mongodb hosts directly and do not try to resolve any of the replicas from the replica set. diff --git a/gcloud/design-center/operations/help b/gcloud/design-center/operations/help index c5e82eede..48c464534 100644 --- a/gcloud/design-center/operations/help +++ b/gcloud/design-center/operations/help @@ -27,6 +27,9 @@ COMMANDS list List operations. + wait + Wait for an operation to complete. + NOTES This variant is also available: diff --git a/gcloud/design-center/operations/wait b/gcloud/design-center/operations/wait new file mode 100644 index 000000000..779929a13 --- /dev/null +++ b/gcloud/design-center/operations/wait @@ -0,0 +1,65 @@ +NAME + gcloud design-center operations wait - wait for an operation to complete + +SYNOPSIS + gcloud design-center operations wait (OPERATION : --location=LOCATION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Wait for an operation to complete + +EXAMPLES + To wait for the operation myOperation to complete in project my-project and + location us-central1, run: + + $ gcloud design-center operations wait myOperation \ + --project=my-project --location=us-central1 + +POSITIONAL ARGUMENTS + Operation resource - The name of the operation resource to wait on. The + arguments in this group can be used to specify the attributes of this + resource. (NOTE) Some attributes are not given arguments in this group but + can be set in other ways. + + To set the project attribute: + ◆ provide the argument operation on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + OPERATION + ID of the operation or fully qualified identifier for the operation. + + To set the operation attribute: + ▸ provide the argument operation on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The location id of the operation resource. + + To set the location attribute: + ▸ provide the argument operation on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the designcenter/v1 API. The full documentation for this + API can be found at: http://cloud.google.com/application-design-center/docs + +NOTES + This variant is also available: + + $ gcloud alpha design-center operations wait + diff --git a/gcloud/design-center/spaces/applications/create b/gcloud/design-center/spaces/applications/create index 9ec410810..984876ff7 100644 --- a/gcloud/design-center/spaces/applications/create +++ b/gcloud/design-center/spaces/applications/create @@ -25,7 +25,7 @@ SYNOPSIS : --criticality-level=CRITICALITY_LEVEL --criticality-mission-critical] [--environment-type=ENVIRONMENT_TYPE : --environment=ENVIRONMENT]] - [--gke-deployment-target-cluster-self-link=GKE_DEPLOYMENT_TARGET_CLUSTER_SELF_LINK --gke-deployment-target-kubernetes-service-account=GKE_DEPLOYMENT_TARGET_KUBERNETES_SERVICE_ACCOUNT --gke-deployment-target-namespace=GKE_DEPLOYMENT_TARGET_NAMESPACE] + [--gke-deployment-target-cluster-self-link=GKE_DEPLOYMENT_TARGET_CLUSTER_SELF_LINK --gke-deployment-target-kubernetes-service-account=GKE_DEPLOYMENT_TARGET_KUBERNETES_SERVICE_ACCOUNT --gke-deployment-target-namespace=GKE_DEPLOYMENT_TARGET_NAMESPACE : --gke-deployment-target-kubernetes-service-account-creation] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -399,6 +399,11 @@ OPTIONAL FLAGS This flag argument must be specified if any of the other arguments in this group are specified. + --gke-deployment-target-kubernetes-service-account-creation + Whether to create the provided KSA. If true, the KSA will be + created in the namespace provided above. If false, the KSA is + expected to already exist in the namespace provided above. + 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/design-center/spaces/applications/deploy b/gcloud/design-center/spaces/applications/deploy index 33a1f09a5..af1b7af0a 100644 --- a/gcloud/design-center/spaces/applications/deploy +++ b/gcloud/design-center/spaces/applications/deploy @@ -3,9 +3,9 @@ NAME SYNOPSIS gcloud design-center spaces applications deploy - (APPLICATION : --location=LOCATION --space=SPACE) [--async] [--replace] - [--service-account=SERVICE_ACCOUNT] [--worker-pool=WORKER_POOL] - [GCLOUD_WIDE_FLAG ...] + (APPLICATION : --location=LOCATION --space=SPACE) [--async] + [--create-sa] [--replace] [--service-account=SERVICE_ACCOUNT] + [--worker-pool=WORKER_POOL] [GCLOUD_WIDE_FLAG ...] DESCRIPTION Deploy an application in a space. @@ -15,12 +15,12 @@ EXAMPLES my-project and location us-central1, run: $ gcloud design-center spaces applications deploy my-application \ - --space=my-space --project=my-project --location=us-central1 + --space=my-space --project=my-project --location=us-central1 Or run: $ gcloud design-center spaces applications deploy \ - projects/my-project/locations/us-central1/spaces/my-space/\ + projects/my-project/locations/us-central1/spaces/my-space/\ applications/my-application To deploy the application my-application in space my-space, project @@ -28,34 +28,57 @@ EXAMPLES run: $ gcloud design-center spaces applications deploy my-application \ - --space=my-space --project=my-project --location=us-central1 \ - --replace + --space=my-space --project=my-project --location=us-central1 \ + --replace To deploy the application my-application in space my-space, project my-project and location us-central1 using a worker pool projects/my-project/locations/us-central1/workerPools/my-worker-pool, run: $ gcloud design-center spaces applications deploy my-application \ - --space=my-space --project=my-project --location=us-central1 \ - --worker-pool=projects/my-project/locations/us-central1/\ + --space=my-space --project=my-project --location=us-central1 \ + --worker-pool=projects/my-project/locations/us-central1/\ workerPools/my-worker-pool + To deploy the application my-application and create a new service account + for the deployment, run: + + $ gcloud design-center spaces applications deploy my-application \ + --space=my-space --project=my-project --location=us-central1 \ + --create-sa + + To deploy the application my-application and create a new service account + and create a specific service account for the deployment, run: + + $ gcloud design-center spaces applications deploy my-application \ + --space=my-space --project=my-project --location=us-central1 \ + --create-sa \ + --service-account=my-service-account@my-project.iam.gserviceacco\ + unt.com + + To deploy the application my-application and use a specific service account + for the deployment, run: + + $ gcloud design-center spaces applications deploy my-application \ + --space=my-space --project=my-project --location=us-central1 \ + --service-account=projects/my-project/serviceAccounts/\ + my-service-account@my-project.iam.gserviceaccount.com + To deploy the application my-application in space my-space, project my-project and location us-central1 asynchronously, run: $ gcloud design-center spaces applications deploy my-application \ - --space=my-space --project=my-project --location=us-central1 \ - --async + --space=my-space --project=my-project --location=us-central1 \ + --async POSITIONAL ARGUMENTS - Application resource - The application name. Format: - projects/$project/locations/$location/spaces/$space/applications/$application - The arguments in this group can be used to specify the attributes of this - resource. (NOTE) Some attributes are not given arguments in this group but - can be set in other ways. + Application resource - The application to deploy IaC. The arguments in + this group can be used to specify the attributes of this resource. (NOTE) + Some attributes are not given arguments in this group but can be set in + other ways. To set the project attribute: - ◆ provide the argument application on the command line with a fully + ◆ provide the argument APPLICATION on the command line with a fully specified name; ◆ provide the argument --project on the command line; ◆ set the property core/project. @@ -67,24 +90,24 @@ POSITIONAL ARGUMENTS application. To set the application attribute: - ▸ provide the argument application on the command line. + ▸ provide the argument APPLICATION on the command line. This positional argument must be specified if any of the other arguments in this group are specified. --location=LOCATION - The location id of the application resource. + The Cloud location for the application. To set the location attribute: - ▸ provide the argument application on the command line with a fully + ▸ provide the argument APPLICATION on the command line with a fully specified name; ▸ provide the argument --location on the command line. --space=SPACE - The space id of the application resource. + The ID of the space. To set the space attribute: - ▸ provide the argument application on the command line with a fully + ▸ provide the argument APPLICATION on the command line with a fully specified name; ▸ provide the argument --space on the command line. @@ -93,24 +116,34 @@ FLAGS Return immediately, without waiting for the operation in progress to complete. + --create-sa + Create a new service account for the deployment. + --replace Flag to update the existing deployment. If not set or false, deploy will fail if application state is in the DEPLOYED state. --service-account=SERVICE_ACCOUNT - The email address of the service account to use for this deployment. + The service account to use for this deployment. ◆ If provided, this service account will be used to execute the deployment process, taking precedence over any service_account specified on the Application resource. - ◆ The caller must have the 'iam.serviceAccounts.actAs' permission on + ◆ The caller must have the "iam.serviceAccounts.actAs" permission on this service account. - ◆ If this field is omitted, the system will use the 'service_account' + ◆ If this field is omitted, the system will use the "service_account" defined within the Application resource. + ◆ If this field is omitted with --create-sa flag, the system will + create a new and unique service_account and use it for the + deployment. ◆ We recommend that you provide a service account here or on the Application resource. If you don't provide a service account, the - deployment will fail. Format: - projects/{PROJECT}/serviceAccounts/{EMAIL_ADDRESS} + deployment will fail. + ◆ If the --create-sa flag is also provided, this value is the ID of a + new service account to be created (e.g., my-new-sa). + + Format: projects/{PROJECT}/serviceAccounts/{EMAIL_ADDRESS} (when not + using --create-sa) --worker-pool=WORKER_POOL The user-specified Worker Pool resource in which the Cloud Build job @@ -129,10 +162,6 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. -API REFERENCE - This command uses the designcenter/v1 API. The full documentation for this - API can be found at: http://cloud.google.com/application-design-center/docs - NOTES This variant is also available: diff --git a/gcloud/design-center/spaces/applications/help b/gcloud/design-center/spaces/applications/help index f97c3178d..423410e2c 100644 --- a/gcloud/design-center/spaces/applications/help +++ b/gcloud/design-center/spaces/applications/help @@ -37,7 +37,7 @@ COMMANDS List applications. preview - Preview an application. + Preview a Design Center application. update Update an application. diff --git a/gcloud/design-center/spaces/applications/preview b/gcloud/design-center/spaces/applications/preview index c5aa6a651..dda704837 100644 --- a/gcloud/design-center/spaces/applications/preview +++ b/gcloud/design-center/spaces/applications/preview @@ -1,11 +1,12 @@ NAME - gcloud design-center spaces applications preview - preview an application + gcloud design-center spaces applications preview - preview a Design Center + application SYNOPSIS gcloud design-center spaces applications preview (APPLICATION : --location=LOCATION --space=SPACE) [--async] - [--service-account=SERVICE_ACCOUNT] [--worker-pool=WORKER_POOL] - [GCLOUD_WIDE_FLAG ...] + [--create-sa] [--service-account=SERVICE_ACCOUNT] + [--worker-pool=WORKER_POOL] [GCLOUD_WIDE_FLAG ...] DESCRIPTION Preview an application in a space. @@ -15,12 +16,12 @@ EXAMPLES my-project and location us-central1, run: $ gcloud design-center spaces applications preview my-application \ - --space=my-space --project=my-project --location=us-central1 + --space=my-space --project=my-project --location=us-central1 Or run: $ gcloud design-center spaces applications preview \ - projects/my-project/locations/us-central1/spaces/my-space/\ + projects/my-project/locations/us-central1/spaces/my-space/\ applications/my-application To preview the application my-application in space my-space, project @@ -28,26 +29,49 @@ EXAMPLES projects/my-project/locations/us-central1/workerPools/my-worker-pool, run: $ gcloud design-center spaces applications preview my-application \ - --space=my-space --project=my-project --location=us-central1 \ - --worker-pool=projects/my-project/locations/us-central1/\ + --space=my-space --project=my-project --location=us-central1 \ + --worker-pool=projects/my-project/locations/us-central1/\ workerPools/my-worker-pool + To preview the application my-application and create a new service account + for the preview, run: + + $ gcloud design-center spaces applications preview my-application \ + --space=my-space --project=my-project --location=us-central1 \ + --create-sa + + To preview the application my-application and create a new provided service + account for the preview, run: + + $ gcloud design-center spaces applications preview my-application \ + --space=my-space --project=my-project --location=us-central1 \ + --create-sa \ + --service-account=my-service-account@my-project.iam.gserviceacco\ + unt.com + + To preview the application my-application and use a specific existing + service account for the preview, run: + + $ gcloud design-center spaces applications preview my-application \ + --space=my-space --project=my-project --location=us-central1 \ + --service-account=projects/my-project/serviceAccounts/\ + my-service-account@my-project.iam.gserviceaccount.com + To preview the application my-application in space my-space, project my-project and location us-central1 asynchronously, run: $ gcloud design-center spaces applications preview my-application \ - --space=my-space --project=my-project --location=us-central1 \ - --async + --space=my-space --project=my-project --location=us-central1 \ + --async POSITIONAL ARGUMENTS - Application resource - The application name in the following format: - projects/$project/locations/$location/spaces/$space/applications/$application - The arguments in this group can be used to specify the attributes of this - resource. (NOTE) Some attributes are not given arguments in this group but - can be set in other ways. + Application resource - The application to preview IaC. The arguments in + this group can be used to specify the attributes of this resource. (NOTE) + Some attributes are not given arguments in this group but can be set in + other ways. To set the project attribute: - ◆ provide the argument application on the command line with a fully + ◆ provide the argument APPLICATION on the command line with a fully specified name; ◆ provide the argument --project on the command line; ◆ set the property core/project. @@ -59,24 +83,24 @@ POSITIONAL ARGUMENTS application. To set the application attribute: - ▸ provide the argument application on the command line. + ▸ provide the argument APPLICATION on the command line. This positional argument must be specified if any of the other arguments in this group are specified. --location=LOCATION - The location id of the application resource. + The Cloud location for the application. To set the location attribute: - ▸ provide the argument application on the command line with a fully + ▸ provide the argument APPLICATION on the command line with a fully specified name; ▸ provide the argument --location on the command line. --space=SPACE - The space id of the application resource. + The ID of the space. To set the space attribute: - ▸ provide the argument application on the command line with a fully + ▸ provide the argument APPLICATION on the command line with a fully specified name; ▸ provide the argument --space on the command line. @@ -85,21 +109,29 @@ FLAGS Return immediately, without waiting for the operation in progress to complete. + --create-sa + Create a new service account for the preview. + --service-account=SERVICE_ACCOUNT - The email address of the service account to use for this preview - operation. + The service account to use for this preview. ◆ If provided, this service account will be used to execute the preview process, taking precedence over any service_account specified on the Application resource. - ◆ The caller must have the 'iam.serviceAccounts.actAs' permission on + ◆ The caller must have the "iam.serviceAccounts.actAs" permission on this service account. - ◆ If this field is omitted, the system will use the 'service_account' + ◆ If this field is omitted, the system will use the "service_account" defined within the Application resource. + ◆ If this field is omitted with --create-sa flag, the system will + create a new and unique service_account and use it for the preview. ◆ We recommend that you provide a service account here or on the Application resource. If you don't provide a service account, the - preview will fail. Format: - projects/{PROJECT}/serviceAccounts/{EMAIL_ADDRESS} + preview will fail. + ◆ If the --create-sa flag is also provided, this value is the ID of a + new service account to be created (e.g., my-new-sa). + + Format: projects/{PROJECT}/serviceAccounts/{EMAIL_ADDRESS} (when not + using --create-sa) --worker-pool=WORKER_POOL The user-specified Worker Pool resource in which the Cloud Build job @@ -118,10 +150,6 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. -API REFERENCE - This command uses the designcenter/v1 API. The full documentation for this - API can be found at: http://cloud.google.com/application-design-center/docs - NOTES This variant is also available: diff --git a/gcloud/design-center/spaces/applications/update b/gcloud/design-center/spaces/applications/update index 73f7c9206..86e5f51bb 100644 --- a/gcloud/design-center/spaces/applications/update +++ b/gcloud/design-center/spaces/applications/update @@ -38,7 +38,7 @@ SYNOPSIS --criticality-type=CRITICALITY_TYPE --environment=ENVIRONMENT --environment-type=ENVIRONMENT_TYPE] [--clear-deployment-target - --gke-deployment-target-cluster-self-link=GKE_DEPLOYMENT_TARGET_CLUSTER_SELF_LINK --gke-deployment-target-kubernetes-service-account=GKE_DEPLOYMENT_TARGET_KUBERNETES_SERVICE_ACCOUNT --gke-deployment-target-namespace=GKE_DEPLOYMENT_TARGET_NAMESPACE] + --gke-deployment-target-cluster-self-link=GKE_DEPLOYMENT_TARGET_CLUSTER_SELF_LINK --gke-deployment-target-kubernetes-service-account=GKE_DEPLOYMENT_TARGET_KUBERNETES_SERVICE_ACCOUNT --[no-]gke-deployment-target-kubernetes-service-account-creation --gke-deployment-target-namespace=GKE_DEPLOYMENT_TARGET_NAMESPACE] [--clear-scope --scope-type=SCOPE_TYPE] [--clear-source --source-application-template-revision=SOURCE_APPLICATION_TEMPLATE_REVISION | --source-shared-template-revision-uri=SOURCE_SHARED_TEMPLATE_REVISION_URI] @@ -612,6 +612,15 @@ FLAGS The kubernetes service account that is created within the namespace provided above. Example: default or node-sa + --[no-]gke-deployment-target-kubernetes-service-account-creation + Whether to create the provided KSA. If true, the KSA will be + created in the namespace provided above. If false, the KSA is + expected to already exist in the namespace provided above. Use + --gke-deployment-target-kubernetes-service-account-creation to + enable and + --no-gke-deployment-target-kubernetes-service-account-creation to + disable. + --gke-deployment-target-namespace=GKE_DEPLOYMENT_TARGET_NAMESPACE The namespace where the application is deployed. diff --git a/gcloud/developer-connect/connections/create b/gcloud/developer-connect/connections/create index 2dba6831b..ed251e6a3 100644 --- a/gcloud/developer-connect/connections/create +++ b/gcloud/developer-connect/connections/create @@ -7,7 +7,7 @@ SYNOPSIS [--git-proxy-config-enabled] [--labels=[LABELS,...]] [--location=LOCATION] [--namespace=NAMESPACE] [--request-id=REQUEST_ID] [--secret=SECRET] [--validate-only] - [--bitbucket-cloud-config-authorizer-credential-user-token-secret-version=BITBUCKET_CLOUD_CONFIG_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --bitbucket-cloud-config-read-authorizer-credential-user-token-secret-version=BITBUCKET_CLOUD_CONFIG_READ_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --bitbucket-cloud-config-webhook-secret-version=BITBUCKET_CLOUD_CONFIG_WEBHOOK_SECRET_VERSION --bitbucket-cloud-config-workspace=BITBUCKET_CLOUD_CONFIG_WORKSPACE | [--bitbucket-data-center-config-authorizer-credential-user-token-secret-version=BITBUCKET_DATA_CENTER_CONFIG_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --bitbucket-data-center-config-host-uri=BITBUCKET_DATA_CENTER_CONFIG_HOST_URI --bitbucket-data-center-config-read-authorizer-credential-user-token-secret-version=BITBUCKET_DATA_CENTER_CONFIG_READ_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --bitbucket-data-center-config-webhook-secret-version=BITBUCKET_DATA_CENTER_CONFIG_WEBHOOK_SECRET_VERSION : --bitbucket-data-center-config-service-directory=BITBUCKET_DATA_CENTER_CONFIG_SERVICE_DIRECTORY --bitbucket-data-center-config-ssl-ca-certificate=BITBUCKET_DATA_CENTER_CONFIG_SSL_CA_CERTIFICATE] | [--github-config-app=GITHUB_CONFIG_APP : --github-config-app-installation-id=GITHUB_CONFIG_APP_INSTALLATION_ID --github-config-authorizer-credential-oauth-token-secret-version=GITHUB_CONFIG_AUTHORIZER_CREDENTIAL_OAUTH_TOKEN_SECRET_VERSION] | [--github-enterprise-config-host-uri=GITHUB_ENTERPRISE_CONFIG_HOST_URI : --github-enterprise-config-app-id=GITHUB_ENTERPRISE_CONFIG_APP_ID --github-enterprise-config-app-installation-id=GITHUB_ENTERPRISE_CONFIG_APP_INSTALLATION_ID --github-enterprise-config-private-key-secret-version=GITHUB_ENTERPRISE_CONFIG_PRIVATE_KEY_SECRET_VERSION --github-enterprise-config-service-directory=GITHUB_ENTERPRISE_CONFIG_SERVICE_DIRECTORY --github-enterprise-config-ssl-ca-certificate=GITHUB_ENTERPRISE_CONFIG_SSL_CA_CERTIFICATE --github-enterprise-config-webhook-secret-version=GITHUB_ENTERPRISE_CONFIG_WEBHOOK_SECRET_VERSION] | --gitlab-config-authorizer-credential-user-token-secret-version=GITLAB_CONFIG_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --gitlab-config-read-authorizer-credential-user-token-secret-version=GITLAB_CONFIG_READ_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --gitlab-config-webhook-secret-version=GITLAB_CONFIG_WEBHOOK_SECRET_VERSION | [--gitlab-enterprise-config-authorizer-credential-user-token-secret-version=GITLAB_ENTERPRISE_CONFIG_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --gitlab-enterprise-config-host-uri=GITLAB_ENTERPRISE_CONFIG_HOST_URI --gitlab-enterprise-config-read-authorizer-credential-user-token-secret-version=GITLAB_ENTERPRISE_CONFIG_READ_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --gitlab-enterprise-config-webhook-secret-version=GITLAB_ENTERPRISE_CONFIG_WEBHOOK_SECRET_VERSION : --gitlab-enterprise-config-service-directory=GITLAB_ENTERPRISE_CONFIG_SERVICE_DIRECTORY --gitlab-enterprise-config-ssl-ca-certificate=GITLAB_ENTERPRISE_CONFIG_SSL_CA_CERTIFICATE]] + [--bitbucket-cloud-config-authorizer-credential-user-token-secret-version=BITBUCKET_CLOUD_CONFIG_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --bitbucket-cloud-config-read-authorizer-credential-user-token-secret-version=BITBUCKET_CLOUD_CONFIG_READ_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --bitbucket-cloud-config-webhook-secret-version=BITBUCKET_CLOUD_CONFIG_WEBHOOK_SECRET_VERSION --bitbucket-cloud-config-workspace=BITBUCKET_CLOUD_CONFIG_WORKSPACE | [--bitbucket-data-center-config-authorizer-credential-user-token-secret-version=BITBUCKET_DATA_CENTER_CONFIG_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --bitbucket-data-center-config-host-uri=BITBUCKET_DATA_CENTER_CONFIG_HOST_URI --bitbucket-data-center-config-read-authorizer-credential-user-token-secret-version=BITBUCKET_DATA_CENTER_CONFIG_READ_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --bitbucket-data-center-config-webhook-secret-version=BITBUCKET_DATA_CENTER_CONFIG_WEBHOOK_SECRET_VERSION : --bitbucket-data-center-config-service-directory=BITBUCKET_DATA_CENTER_CONFIG_SERVICE_DIRECTORY --bitbucket-data-center-config-ssl-ca-certificate=BITBUCKET_DATA_CENTER_CONFIG_SSL_CA_CERTIFICATE] | [--github-config-app=GITHUB_CONFIG_APP : --github-config-app-installation-id=GITHUB_CONFIG_APP_INSTALLATION_ID --github-config-authorizer-credential-oauth-token-secret-version=GITHUB_CONFIG_AUTHORIZER_CREDENTIAL_OAUTH_TOKEN_SECRET_VERSION] | [--github-enterprise-config-host-uri=GITHUB_ENTERPRISE_CONFIG_HOST_URI : --github-enterprise-config-app-id=GITHUB_ENTERPRISE_CONFIG_APP_ID --github-enterprise-config-app-installation-id=GITHUB_ENTERPRISE_CONFIG_APP_INSTALLATION_ID --github-enterprise-config-private-key-secret-version=GITHUB_ENTERPRISE_CONFIG_PRIVATE_KEY_SECRET_VERSION --github-enterprise-config-service-directory=GITHUB_ENTERPRISE_CONFIG_SERVICE_DIRECTORY --github-enterprise-config-ssl-ca-certificate=GITHUB_ENTERPRISE_CONFIG_SSL_CA_CERTIFICATE --github-enterprise-config-webhook-secret-version=GITHUB_ENTERPRISE_CONFIG_WEBHOOK_SECRET_VERSION] | --gitlab-config-authorizer-credential-user-token-secret-version=GITLAB_CONFIG_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --gitlab-config-read-authorizer-credential-user-token-secret-version=GITLAB_CONFIG_READ_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --gitlab-config-webhook-secret-version=GITLAB_CONFIG_WEBHOOK_SECRET_VERSION | [--gitlab-enterprise-config-authorizer-credential-user-token-secret-version=GITLAB_ENTERPRISE_CONFIG_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --gitlab-enterprise-config-host-uri=GITLAB_ENTERPRISE_CONFIG_HOST_URI --gitlab-enterprise-config-read-authorizer-credential-user-token-secret-version=GITLAB_ENTERPRISE_CONFIG_READ_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --gitlab-enterprise-config-webhook-secret-version=GITLAB_ENTERPRISE_CONFIG_WEBHOOK_SECRET_VERSION : --gitlab-enterprise-config-service-directory=GITLAB_ENTERPRISE_CONFIG_SERVICE_DIRECTORY --gitlab-enterprise-config-ssl-ca-certificate=GITLAB_ENTERPRISE_CONFIG_SSL_CA_CERTIFICATE] | [--http-config-host-uri=HTTP_CONFIG_HOST_URI : --http-config-service-directory=HTTP_CONFIG_SERVICE_DIRECTORY --http-config-ssl-ca-certificate=HTTP_CONFIG_SSL_CA_CERTIFICATE --http-config-bearer-token-authentication-secret-version=HTTP_CONFIG_BEARER_TOKEN_AUTHENTICATION_SECRET_VERSION | [--http-config-basic-authentication-username=HTTP_CONFIG_BASIC_AUTHENTICATION_USERNAME : --http-config-basic-authentication-password-secret-version=HTTP_CONFIG_BASIC_AUTHENTICATION_PASSWORD_SECRET_VERSION]]] [(--crypto-key-config-reference=CRYPTO_KEY_CONFIG_REFERENCE : --key-ring=KEY_RING)] [GCLOUD_WIDE_FLAG ...] @@ -1018,6 +1018,142 @@ FLAGS SSL Certificate Authority certificate to use for requests to GitLab Enterprise instance. + Configuration for connections to an HTTP service provider. + + --http-config-host-uri=HTTP_CONFIG_HOST_URI + The service provider's https endpoint. + + This flag argument must be specified if any of the other arguments + in this group are specified. + + ServiceDirectoryConfig represents Service Directory configuration for + a connection. + + Service resource - The Service Directory service name. Format: + projects/{project}/locations/{location}/namespaces/{namespace}/services/{service}. + 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 --http-config-service-directory on the + command line with a fully specified name; + ◇ provide the argument --project on the command line; + ◇ set the property core/project. + + To set the location attribute: + ◇ provide the argument --http-config-service-directory on the + command line with a fully specified name; + ◇ provide the argument --location on the command line. + + To set the namespace attribute: + ◇ provide the argument --http-config-service-directory on the + command line with a fully specified name; + ◇ provide the argument --namespace on the command line. + + This must be specified. + + --http-config-service-directory=HTTP_CONFIG_SERVICE_DIRECTORY + ID of the service or fully qualified identifier for the + service. + + To set the service attribute: + ▹ provide the argument --http-config-service-directory on the + command line. + + --http-config-ssl-ca-certificate=HTTP_CONFIG_SSL_CA_CERTIFICATE + The SSL certificate to use for requests to the HTTP service + provider. + + Arguments for the authentication. + + At most one of these can be specified: + + Bearer token authentication with a token. + + Arguments for the token. + + SecretVersion resource - The token SecretManager secret version + to authenticate as. 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 + --http-config-bearer-token-authentication-secret-version on + the command line with a fully specified name; + ▪ provide the argument --project on the command line; + ▪ set the property core/project. + + To set the location attribute: + ▪ provide the argument + --http-config-bearer-token-authentication-secret-version on + the command line with a fully specified name; + ▪ provide the argument --location on the command line. + + To set the secret attribute: + ▪ provide the argument + --http-config-bearer-token-authentication-secret-version on + the command line with a fully specified name; + ▪ provide the argument --secret on the command line. This + resource can be one of the following types: + [developerconnect.projects.locations.secrets.versions, + developerconnect.projects.secrets.versions]. + + --http-config-bearer-token-authentication-secret-version=HTTP_CONFIG_BEARER_TOKEN_AUTHENTICATION_SECRET_VERSION + ID of the secretVersion or fully qualified identifier for + the secretVersion. + + To set the secret_version attribute: + ◆ provide the argument + --http-config-bearer-token-authentication-secret-version + on the command line. + + Basic authentication with username and password. + + --http-config-basic-authentication-username=HTTP_CONFIG_BASIC_AUTHENTICATION_USERNAME + The username to authenticate as. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + Arguments for the password. + + SecretVersion resource - The password SecretManager secret + version to authenticate as. 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 + --http-config-basic-authentication-password-secret-version on + the command line with a fully specified name; + ▪ provide the argument --project on the command line; + ▪ set the property core/project. + + To set the location attribute: + ▪ provide the argument + --http-config-basic-authentication-password-secret-version on + the command line with a fully specified name; + ▪ provide the argument --location on the command line. + + To set the secret attribute: + ▪ provide the argument + --http-config-basic-authentication-password-secret-version on + the command line with a fully specified name; + ▪ provide the argument --secret on the command line. This + resource can be one of the following types: + [developerconnect.projects.locations.secrets.versions, + developerconnect.projects.secrets.versions]. + + --http-config-basic-authentication-password-secret-version=HTTP_CONFIG_BASIC_AUTHENTICATION_PASSWORD_SECRET_VERSION + ID of the secretVersion or fully qualified identifier for + the secretVersion. + + To set the secret_version attribute: + ◆ provide the argument + --http-config-basic-authentication-password-secret-version + on the command line. + The crypto key configuration. This field is used by the Customer-managed encryption keys (CMEK) feature. diff --git a/gcloud/developer-connect/connections/update b/gcloud/developer-connect/connections/update index 026e7c714..af00ec66b 100644 --- a/gcloud/developer-connect/connections/update +++ b/gcloud/developer-connect/connections/update @@ -10,7 +10,7 @@ SYNOPSIS [--annotations=[ANNOTATIONS,...] | --update-annotations=[UPDATE_ANNOTATIONS,...] --clear-annotations | --remove-annotations=REMOVE_ANNOTATIONS] - [--bitbucket-cloud-config-authorizer-credential-user-token-secret-version=BITBUCKET_CLOUD_CONFIG_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --bitbucket-cloud-config-read-authorizer-credential-user-token-secret-version=BITBUCKET_CLOUD_CONFIG_READ_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --bitbucket-cloud-config-workspace=BITBUCKET_CLOUD_CONFIG_WORKSPACE --clear-bitbucket-cloud-config | --bitbucket-data-center-config-authorizer-credential-user-token-secret-version=BITBUCKET_DATA_CENTER_CONFIG_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --bitbucket-data-center-config-host-uri=BITBUCKET_DATA_CENTER_CONFIG_HOST_URI --bitbucket-data-center-config-read-authorizer-credential-user-token-secret-version=BITBUCKET_DATA_CENTER_CONFIG_READ_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --bitbucket-data-center-config-service-directory=BITBUCKET_DATA_CENTER_CONFIG_SERVICE_DIRECTORY --bitbucket-data-center-config-ssl-ca-certificate=BITBUCKET_DATA_CENTER_CONFIG_SSL_CA_CERTIFICATE --clear-bitbucket-data-center-config | --clear-github-config --github-config-app-installation-id=GITHUB_CONFIG_APP_INSTALLATION_ID --github-config-authorizer-credential-oauth-token-secret-version=GITHUB_CONFIG_AUTHORIZER_CREDENTIAL_OAUTH_TOKEN_SECRET_VERSION | --clear-github-enterprise-config --github-enterprise-config-app-id=GITHUB_ENTERPRISE_CONFIG_APP_ID --github-enterprise-config-app-installation-id=GITHUB_ENTERPRISE_CONFIG_APP_INSTALLATION_ID --github-enterprise-config-host-uri=GITHUB_ENTERPRISE_CONFIG_HOST_URI --github-enterprise-config-service-directory=GITHUB_ENTERPRISE_CONFIG_SERVICE_DIRECTORY --github-enterprise-config-ssl-ca-certificate=GITHUB_ENTERPRISE_CONFIG_SSL_CA_CERTIFICATE --clear-github-enterprise-config-private-key-secret-version | --github-enterprise-config-private-key-secret-version=GITHUB_ENTERPRISE_CONFIG_PRIVATE_KEY_SECRET_VERSION --clear-github-enterprise-config-webhook-secret-version | --github-enterprise-config-webhook-secret-version=GITHUB_ENTERPRISE_CONFIG_WEBHOOK_SECRET_VERSION | --clear-gitlab-config --gitlab-config-authorizer-credential-user-token-secret-version=GITLAB_CONFIG_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --gitlab-config-read-authorizer-credential-user-token-secret-version=GITLAB_CONFIG_READ_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION | --clear-gitlab-enterprise-config --gitlab-enterprise-config-authorizer-credential-user-token-secret-version=GITLAB_ENTERPRISE_CONFIG_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --gitlab-enterprise-config-host-uri=GITLAB_ENTERPRISE_CONFIG_HOST_URI --gitlab-enterprise-config-read-authorizer-credential-user-token-secret-version=GITLAB_ENTERPRISE_CONFIG_READ_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --gitlab-enterprise-config-service-directory=GITLAB_ENTERPRISE_CONFIG_SERVICE_DIRECTORY --gitlab-enterprise-config-ssl-ca-certificate=GITLAB_ENTERPRISE_CONFIG_SSL_CA_CERTIFICATE] + [--bitbucket-cloud-config-authorizer-credential-user-token-secret-version=BITBUCKET_CLOUD_CONFIG_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --bitbucket-cloud-config-read-authorizer-credential-user-token-secret-version=BITBUCKET_CLOUD_CONFIG_READ_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --bitbucket-cloud-config-workspace=BITBUCKET_CLOUD_CONFIG_WORKSPACE --clear-bitbucket-cloud-config | --bitbucket-data-center-config-authorizer-credential-user-token-secret-version=BITBUCKET_DATA_CENTER_CONFIG_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --bitbucket-data-center-config-host-uri=BITBUCKET_DATA_CENTER_CONFIG_HOST_URI --bitbucket-data-center-config-read-authorizer-credential-user-token-secret-version=BITBUCKET_DATA_CENTER_CONFIG_READ_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --bitbucket-data-center-config-service-directory=BITBUCKET_DATA_CENTER_CONFIG_SERVICE_DIRECTORY --bitbucket-data-center-config-ssl-ca-certificate=BITBUCKET_DATA_CENTER_CONFIG_SSL_CA_CERTIFICATE --clear-bitbucket-data-center-config | --clear-github-config --github-config-app-installation-id=GITHUB_CONFIG_APP_INSTALLATION_ID --github-config-authorizer-credential-oauth-token-secret-version=GITHUB_CONFIG_AUTHORIZER_CREDENTIAL_OAUTH_TOKEN_SECRET_VERSION | --clear-github-enterprise-config --github-enterprise-config-app-id=GITHUB_ENTERPRISE_CONFIG_APP_ID --github-enterprise-config-app-installation-id=GITHUB_ENTERPRISE_CONFIG_APP_INSTALLATION_ID --github-enterprise-config-host-uri=GITHUB_ENTERPRISE_CONFIG_HOST_URI --github-enterprise-config-service-directory=GITHUB_ENTERPRISE_CONFIG_SERVICE_DIRECTORY --github-enterprise-config-ssl-ca-certificate=GITHUB_ENTERPRISE_CONFIG_SSL_CA_CERTIFICATE --clear-github-enterprise-config-private-key-secret-version | --github-enterprise-config-private-key-secret-version=GITHUB_ENTERPRISE_CONFIG_PRIVATE_KEY_SECRET_VERSION --clear-github-enterprise-config-webhook-secret-version | --github-enterprise-config-webhook-secret-version=GITHUB_ENTERPRISE_CONFIG_WEBHOOK_SECRET_VERSION | --clear-gitlab-config --gitlab-config-authorizer-credential-user-token-secret-version=GITLAB_CONFIG_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --gitlab-config-read-authorizer-credential-user-token-secret-version=GITLAB_CONFIG_READ_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION | --clear-gitlab-enterprise-config --gitlab-enterprise-config-authorizer-credential-user-token-secret-version=GITLAB_ENTERPRISE_CONFIG_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --gitlab-enterprise-config-host-uri=GITLAB_ENTERPRISE_CONFIG_HOST_URI --gitlab-enterprise-config-read-authorizer-credential-user-token-secret-version=GITLAB_ENTERPRISE_CONFIG_READ_AUTHORIZER_CREDENTIAL_USER_TOKEN_SECRET_VERSION --gitlab-enterprise-config-service-directory=GITLAB_ENTERPRISE_CONFIG_SERVICE_DIRECTORY --gitlab-enterprise-config-ssl-ca-certificate=GITLAB_ENTERPRISE_CONFIG_SSL_CA_CERTIFICATE | --clear-http-config --http-config-service-directory=HTTP_CONFIG_SERVICE_DIRECTORY --http-config-ssl-ca-certificate=HTTP_CONFIG_SSL_CA_CERTIFICATE --clear-http-config-bearer-token-authentication-secret-version | --http-config-bearer-token-authentication-secret-version=HTTP_CONFIG_BEARER_TOKEN_AUTHENTICATION_SECRET_VERSION | --http-config-basic-authentication-username=HTTP_CONFIG_BASIC_AUTHENTICATION_USERNAME --clear-http-config-basic-authentication-password-secret-version | --http-config-basic-authentication-password-secret-version=HTTP_CONFIG_BASIC_AUTHENTICATION_PASSWORD_SECRET_VERSION] [--clear-crypto-key-config [--crypto-key-config-reference=CRYPTO_KEY_CONFIG_REFERENCE : --key-ring=KEY_RING]] @@ -868,6 +868,160 @@ FLAGS SSL Certificate Authority certificate to use for requests to GitLab Enterprise instance. + Configuration for connections to an HTTP service provider. + + --clear-http-config + Set connection.httpConfig back to default value. + + ServiceDirectoryConfig represents Service Directory configuration for + a connection. + + Service resource - The Service Directory service name. Format: + projects/{project}/locations/{location}/namespaces/{namespace}/services/{service}. + 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 --http-config-service-directory on the + command line with a fully specified name; + ◇ provide the argument --project on the command line; + ◇ set the property core/project. + + To set the location attribute: + ◇ provide the argument --http-config-service-directory on the + command line with a fully specified name; + ◇ provide the argument --location on the command line. + + To set the namespace attribute: + ◇ provide the argument --http-config-service-directory on the + command line with a fully specified name; + ◇ provide the argument --namespace on the command line. + + --http-config-service-directory=HTTP_CONFIG_SERVICE_DIRECTORY + ID of the service or fully qualified identifier for the + service. + + To set the service attribute: + ▹ provide the argument --http-config-service-directory on the + command line. + + --http-config-ssl-ca-certificate=HTTP_CONFIG_SSL_CA_CERTIFICATE + The SSL certificate to use for requests to the HTTP service + provider. + + Arguments for the authentication. + + At most one of these can be specified: + + Bearer token authentication with a token. + + Arguments for the token. + + Update http_config_bearer_token_authentication_secret_version. + + At most one of these can be specified: + + --clear-http-config-bearer-token-authentication-secret-version + Clear + http_config_bearer_token_authentication_secret_version + value and set to null. + + SecretVersion resource - Set + http_config_bearer_token_authentication_secret_version to new + value. + + The token SecretManager secret version to authenticate as. + 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 + --http-config-bearer-token-authentication-secret-version on + the command line with a fully specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + To set the location attribute: + ◆ provide the argument + --http-config-bearer-token-authentication-secret-version on + the command line with a fully specified name; + ◆ provide the argument --location on the command line. + + To set the secret attribute: + ◆ provide the argument + --http-config-bearer-token-authentication-secret-version on + the command line with a fully specified name; + ◆ provide the argument --secret on the command line. This + resource can be one of the following types: + [developerconnect.projects.locations.secrets.versions, + developerconnect.projects.secrets.versions]. + + --http-config-bearer-token-authentication-secret-version=HTTP_CONFIG_BEARER_TOKEN_AUTHENTICATION_SECRET_VERSION + ID of the secretVersion or fully qualified identifier for + the secretVersion. + + To set the secret_version attribute: + ▸ provide the argument + --http-config-bearer-token-authentication-secret-version + on the command line. + + Basic authentication with username and password. + + --http-config-basic-authentication-username=HTTP_CONFIG_BASIC_AUTHENTICATION_USERNAME + The username to authenticate as. + + Arguments for the password. + + Update http_config_basic_authentication_password_secret_version. + + At most one of these can be specified: + + --clear-http-config-basic-authentication-password-secret-version + Clear + http_config_basic_authentication_password_secret_version + value and set to null. + + SecretVersion resource - Set + http_config_basic_authentication_password_secret_version to + new value. + + The password SecretManager secret version to authenticate as. + 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 + --http-config-basic-authentication-password-secret-version + on the command line with a fully specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + To set the location attribute: + ◆ provide the argument + --http-config-basic-authentication-password-secret-version + on the command line with a fully specified name; + ◆ provide the argument --location on the command line. + + To set the secret attribute: + ◆ provide the argument + --http-config-basic-authentication-password-secret-version + on the command line with a fully specified name; + ◆ provide the argument --secret on the command line. This + resource can be one of the following types: + [developerconnect.projects.locations.secrets.versions, + developerconnect.projects.secrets.versions]. + + --http-config-basic-authentication-password-secret-version=HTTP_CONFIG_BASIC_AUTHENTICATION_PASSWORD_SECRET_VERSION + ID of the secretVersion or fully qualified identifier for + the secretVersion. + + To set the secret_version attribute: + ▸ provide the argument + --http-config-basic-authentication-password-secret-version + on the command line. + The crypto key configuration. This field is used by the Customer-managed encryption keys (CMEK) feature. diff --git a/gcloud/firestore/databases/create b/gcloud/firestore/databases/create index 28a58efff..f592ba5f5 100644 --- a/gcloud/firestore/databases/create +++ b/gcloud/firestore/databases/create @@ -5,16 +5,34 @@ NAME SYNOPSIS gcloud firestore databases create --location=LOCATION [--database=DATABASE; default="(default)"] [--delete-protection] - [--edition=EDITION; default="standard"] [--enable-pitr] - [--kms-key-name=KMS_KEY_NAME] [--tags=[KEY=VALUE,...]] - [--type=TYPE; default="firestore-native"] [GCLOUD_WIDE_FLAG ...] + [--edition=EDITION; default="standard"] + [--enable-firestore-data-access] + [--enable-mongodb-compatible-data-access] [--enable-pitr] + [--enable-realtime-updates] [--kms-key-name=KMS_KEY_NAME] + [--tags=[KEY=VALUE,...]] [--type=TYPE; default="firestore-native"] + [GCLOUD_WIDE_FLAG ...] EXAMPLES To create a Firestore Enterprise database named foo in nam5 for use with - MongoDB Compatibility. + MongoDB Compatible API with Data Access Mode enabled. $ gcloud firestore databases create --database=foo \ - --edition=enterprise --location=nam5 + --edition=enterprise --location=nam5 \ + --enable-mongodb-compatible-data-access + + To create a Firestore Enterprise database named foo in nam5 for use with + Firestore API Data Access Mode enabled and Realtime Updates disabled. + + $ gcloud firestore databases create --database=foo \ + --edition=enterprise --location=nam5 \ + --enable-firestore-data-access + + To create a Firestore Enterprise database named foo in nam5 for use with + Firestore API Data Access Mode enabled and Realtime Updates enabled. + + $ gcloud firestore databases create --database=foo \ + --edition=enterprise --location=nam5 \ + --enable-firestore-data-access --enable-realtime-updates To create a Firestore Native database in nam5. @@ -87,6 +105,23 @@ OPTIONAL FLAGS The edition of the database. EDITION must be one of: standard, enterprise. + --enable-firestore-data-access + Whether to enable Firestore API Data Access on the created database. + + If set to true, Firestore API Data Access on the new database will be + enabled. By default, this feature is disabled for Enterprise edition + databases. To explicitly disable, use + --no-enable-firestore-data-access. + + --enable-mongodb-compatible-data-access + Whether to enable MongoDB Compatible API Data Access on the created + database. + + If set to true, MongoDB Compatible API Data Access on the new database + will be enabled. By default, this feature is enabled for Enterprise + edition databases. To disable, use + --no-enable-mongodb-compatible-data-access. + --enable-pitr Whether to enable Point In Time Recovery (PITR) on the created database. @@ -94,6 +129,13 @@ OPTIONAL FLAGS If set to true, PITR on the new database will be enabled. By default, this feature is not enabled. + --enable-realtime-updates + Whether to enable Realtime Updates feature on the created database. + + If set to true, Realtime Updates feature on the new database will be + enabled. By default, this feature is disabled for Enterprise edition + databases. To explicitly disable, use --no-enable-realtime-updates. + --kms-key-name=KMS_KEY_NAME The resource ID of a Cloud KMS key. If set, the database created will be a Customer-Managed Encryption Key (CMEK) database encrypted with diff --git a/gcloud/gemini/help b/gcloud/gemini/help index ae709b486..504135335 100644 --- a/gcloud/gemini/help +++ b/gcloud/gemini/help @@ -37,3 +37,9 @@ GROUPS release-channel-settings Manage Release Channel Setting resources. + +NOTES + This variant is also available: + + $ gcloud beta gemini + diff --git a/gcloud/infra-manager/automigrationconfig/describe b/gcloud/infra-manager/automigrationconfig/describe new file mode 100644 index 000000000..fa80c0f55 --- /dev/null +++ b/gcloud/infra-manager/automigrationconfig/describe @@ -0,0 +1,45 @@ +NAME + gcloud infra-manager automigrationconfig describe - describe an + AutoMigrationConfig + +SYNOPSIS + gcloud infra-manager automigrationconfig describe [--location=LOCATION] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Describe an AutoMigrationConfig. + +EXAMPLES + To describe an AutoMigrationConfig for location us-central1: $ gcloud infra-manager automigrationconfig describe \ + --location=us-central1 + +FLAGS + Location resource - The location to read the AutoMigrationConfig from. + This represents a Cloud resource. (NOTE) Some attributes are not given + arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument --location on the command line with a fully + specified name; + ◆ set the property infra-manager/location with a fully specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + --location=LOCATION + ID of the location or fully qualified identifier for the location. + + To set the location attribute: + ▸ provide the argument --location on the command line; + ▸ set the property infra-manager/location. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the config/v1 API. The full documentation for this API + can be found at: https://cloud.google.com/infrastructure-manager/docs diff --git a/gcloud/infra-manager/automigrationconfig/disable-auto-migration b/gcloud/infra-manager/automigrationconfig/disable-auto-migration new file mode 100644 index 000000000..9aaa7c9f7 --- /dev/null +++ b/gcloud/infra-manager/automigrationconfig/disable-auto-migration @@ -0,0 +1,49 @@ +NAME + gcloud infra-manager automigrationconfig disable-auto-migration - disable + AutoMigrationConfig + +SYNOPSIS + gcloud infra-manager automigrationconfig disable-auto-migration [--async] + [--location=LOCATION] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Disable AutoMigrationConfig. + +EXAMPLES + To disable AutoMigrationConfig for location us-central1: $ gcloud infra-manager automigrationconfig disable-auto-migration \ + --location=us-central1 + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + Location resource - The location to disable AutoMigrationConfig for. This + represents a Cloud resource. (NOTE) Some attributes are not given + arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument --location on the command line with a fully + specified name; + ◆ set the property infra-manager/location with a fully specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + --location=LOCATION + ID of the location or fully qualified identifier for the location. + + To set the location attribute: + ▸ provide the argument --location on the command line; + ▸ set the property infra-manager/location. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the config/v1 API. The full documentation for this API + can be found at: https://cloud.google.com/infrastructure-manager/docs diff --git a/gcloud/infra-manager/automigrationconfig/enable-auto-migration b/gcloud/infra-manager/automigrationconfig/enable-auto-migration new file mode 100644 index 000000000..34739bb98 --- /dev/null +++ b/gcloud/infra-manager/automigrationconfig/enable-auto-migration @@ -0,0 +1,49 @@ +NAME + gcloud infra-manager automigrationconfig enable-auto-migration - enable + AutoMigrationConfig + +SYNOPSIS + gcloud infra-manager automigrationconfig enable-auto-migration [--async] + [--location=LOCATION] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Enable AutoMigrationConfig. + +EXAMPLES + To enable AutoMigrationConfig for location us-central1: $ gcloud infra-manager automigrationconfig enable-auto-migration \ + --location=us-central1 + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + Location resource - The location to enable AutoMigrationConfig for. This + represents a Cloud resource. (NOTE) Some attributes are not given + arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument --location on the command line with a fully + specified name; + ◆ set the property infra-manager/location with a fully specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + --location=LOCATION + ID of the location or fully qualified identifier for the location. + + To set the location attribute: + ▸ provide the argument --location on the command line; + ▸ set the property infra-manager/location. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the config/v1 API. The full documentation for this API + can be found at: https://cloud.google.com/infrastructure-manager/docs diff --git a/gcloud/infra-manager/automigrationconfig/help b/gcloud/infra-manager/automigrationconfig/help new file mode 100644 index 000000000..bff637f15 --- /dev/null +++ b/gcloud/infra-manager/automigrationconfig/help @@ -0,0 +1,26 @@ +NAME + gcloud infra-manager automigrationconfig - manage auto migration config + resources + +SYNOPSIS + gcloud infra-manager automigrationconfig COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Manage auto migration config resources. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + describe + Describe an AutoMigrationConfig. + + disable-auto-migration + Disable AutoMigrationConfig. + + enable-auto-migration + Enable AutoMigrationConfig. diff --git a/gcloud/infra-manager/help b/gcloud/infra-manager/help index 7e0411c15..679457fb3 100644 --- a/gcloud/infra-manager/help +++ b/gcloud/infra-manager/help @@ -15,6 +15,9 @@ GCLOUD WIDE FLAGS GROUPS GROUP is one of the following: + automigrationconfig + Manage auto migration config resources. + deployments Manage Deployment resources. diff --git a/gcloud/redis/clusters/create b/gcloud/redis/clusters/create index ab36869ee..e1d5a8d50 100644 --- a/gcloud/redis/clusters/create +++ b/gcloud/redis/clusters/create @@ -9,7 +9,7 @@ SYNOPSIS [--automated-backup-start-time=AUTOMATED_BACKUP_START_TIME] [--automated-backup-ttl=AUTOMATED_BACKUP_TTL] [--cross-cluster-replication-role=CROSS_CLUSTER_REPLICATION_ROLE] - [--deletion-protection] [--kms-key=KMS_KEY] + [--deletion-protection] [--kms-key=KMS_KEY] [--labels=[KEY=VALUE,...]] [--maintenance-window-day=MAINTENANCE_WINDOW_DAY] [--maintenance-window-hour=MAINTENANCE_WINDOW_HOUR] [--network=NETWORK] [--node-type=NODE_TYPE] [--persistence-mode=PERSISTENCE_MODE] @@ -151,6 +151,14 @@ FLAGS The key must be in the same region as the cluster. Otherwise, the create operation fails. + --labels=[KEY=VALUE,...] + List of label KEY=VALUE pairs to add. + + Keys must start with a lowercase character and contain only hyphens + (-), underscores (_), lowercase characters, and numbers. Values must + contain only hyphens (-), underscores (_), lowercase characters, and + numbers. + --maintenance-window-day=MAINTENANCE_WINDOW_DAY Day of week when the window starts, e.g. sunday. MAINTENANCE_WINDOW_DAY must be one of: friday, monday, saturday, sunday, thursday, tuesday, diff --git a/gcloud/redis/clusters/update b/gcloud/redis/clusters/update index d2c94cb4e..cfa43fb09 100644 --- a/gcloud/redis/clusters/update +++ b/gcloud/redis/clusters/update @@ -14,7 +14,8 @@ SYNOPSIS [--rdb-snapshot-start-time=RDB_SNAPSHOT_START_TIME] [--remove-redis-config=[KEY,...]] [--replica-count=REPLICA_COUNT] [--shard-count=SHARD_COUNT] [--simulate-maintenance-event] - [--update-redis-config=KEY=VALUE] + [--update-labels=[KEY=VALUE,...]] [--update-redis-config=KEY=VALUE] + [--clear-labels | --remove-labels=[KEY,...]] [--maintenance-window-any | --maintenance-window-day=MAINTENANCE_WINDOW_DAY --maintenance-window-hour=MAINTENANCE_WINDOW_HOUR] @@ -156,11 +157,40 @@ FLAGS --simulate-maintenance-event Trigger a simulation for maintenance event. + --update-labels=[KEY=VALUE,...] + List of label KEY=VALUE pairs to update. If a label exists, its value + is modified. Otherwise, a new label is created. + + Keys must start with a lowercase character and contain only hyphens + (-), underscores (_), lowercase characters, and numbers. Values must + contain only hyphens (-), underscores (_), lowercase characters, and + numbers. + --update-redis-config=KEY=VALUE A list of Redis Cluster config KEY=VALUE pairs to update. If a config parameter is already set, its value is modified; otherwise a new Redis config parameter is added. + At most one of these can be specified: + + --clear-labels + Remove all labels. If --update-labels is also specified then + --clear-labels is applied first. + + For example, to remove all labels: + + $ gcloud redis clusters update --clear-labels + + To remove all existing labels and create two new labels, foo and baz: + + $ gcloud redis clusters update --clear-labels \ + --update-labels foo=bar,baz=qux + + --remove-labels=[KEY,...] + List of label keys to remove. If a label does not exist it is + silently ignored. If --update-labels is also specified then + --update-labels is applied first. + At most one of these can be specified: --maintenance-window-any diff --git a/gcloud/run/deploy b/gcloud/run/deploy index 9e597a0df..f5c9b5c01 100644 --- a/gcloud/run/deploy +++ b/gcloud/run/deploy @@ -251,7 +251,7 @@ FLAGS and resume server-assigned naming. --scaling=SCALING - The scaling mode to use for this resource. Flag value could be either + The scaling mode to use for this service. Flag value could be either "auto" for automatic scaling, or a positive integer to configure manual scaling with the given integer as a fixed instance count. @@ -559,7 +559,8 @@ FLAGS KEY_1: "value1" KEY_2: "value 2" - Example ENV content: + + Example ENV content: KEY_1="value1" KEY_2="value 2" diff --git a/gcloud/run/jobs/create b/gcloud/run/jobs/create index b0c3f4c57..1649869a2 100644 --- a/gcloud/run/jobs/create +++ b/gcloud/run/jobs/create @@ -275,7 +275,8 @@ FLAGS KEY_1: "value1" KEY_2: "value 2" - Example ENV content: + + Example ENV content: KEY_1="value1" KEY_2="value 2" diff --git a/gcloud/run/jobs/deploy b/gcloud/run/jobs/deploy index 876dc7e01..947d5a834 100644 --- a/gcloud/run/jobs/deploy +++ b/gcloud/run/jobs/deploy @@ -277,7 +277,8 @@ FLAGS KEY_1: "value1" KEY_2: "value 2" - Example ENV content: + + Example ENV content: KEY_1="value1" KEY_2="value 2" diff --git a/gcloud/run/jobs/update b/gcloud/run/jobs/update index 2a8ac8e8b..cefe2ffb0 100644 --- a/gcloud/run/jobs/update +++ b/gcloud/run/jobs/update @@ -292,7 +292,8 @@ FLAGS KEY_1: "value1" KEY_2: "value 2" - Example ENV content: + + Example ENV content: KEY_1="value1" KEY_2="value 2" diff --git a/gcloud/run/multi-region-services/update b/gcloud/run/multi-region-services/update index 0fd80721d..91a307cc3 100644 --- a/gcloud/run/multi-region-services/update +++ b/gcloud/run/multi-region-services/update @@ -222,7 +222,7 @@ FLAGS and resume server-assigned naming. --scaling=SCALING - The scaling mode to use for this resource. Flag value could be either + The scaling mode to use for this service. Flag value could be either "auto" for automatic scaling, or a positive integer to configure manual scaling with the given integer as a fixed instance count. @@ -443,7 +443,8 @@ FLAGS KEY_1: "value1" KEY_2: "value 2" - Example ENV content: + + Example ENV content: KEY_1="value1" KEY_2="value 2" diff --git a/gcloud/run/services/update b/gcloud/run/services/update index 9bae0ac1b..9938b0ebf 100644 --- a/gcloud/run/services/update +++ b/gcloud/run/services/update @@ -220,7 +220,7 @@ FLAGS and resume server-assigned naming. --scaling=SCALING - The scaling mode to use for this resource. Flag value could be either + The scaling mode to use for this service. Flag value could be either "auto" for automatic scaling, or a positive integer to configure manual scaling with the given integer as a fixed instance count. @@ -468,7 +468,8 @@ FLAGS KEY_1: "value1" KEY_2: "value 2" - Example ENV content: + + Example ENV content: KEY_1="value1" KEY_2="value 2" diff --git a/gcloud/secrets/replication/update b/gcloud/secrets/replication/update index 233ab2725..761af5a80 100644 --- a/gcloud/secrets/replication/update +++ b/gcloud/secrets/replication/update @@ -24,15 +24,16 @@ EXAMPLES To set the CMEK key on an automatic secret called my-secret to a specified KMS key, run: - $gcloud secrets replication update my-secret - --set-kms-key=projects/my-project/locations/global/keyRings/my-keyring/cryptoKeys/my-key + $ gcloud secrets replication update my-secret \ + --set-kms-key=projects/my-project/locations/global/keyRings/\ + my-keyring/cryptoKeys/my-key To set the CMEK key on a secret called my-secret to a specified KMS key in a specified location in its replication, run: - $gcloud secrets replication update my-secret - --set-kms-key=projects/my-project/locations/us-central1/keyRings/my-keyring/cryptoKeys/my-key - --location=us-central1 + $ gcloud secrets replication update my-secret \ + --set-kms-key=projects/my-project/locations/us-central1/\ + keyRings/my-keyring/cryptoKeys/my-key --location=us-central1 POSITIONAL ARGUMENTS Secret resource - The secret to update. This represents a Cloud resource. diff --git a/gcloud/spanner/instance-partitions/create b/gcloud/spanner/instance-partitions/create index a3039cf4c..8de2ef6e6 100644 --- a/gcloud/spanner/instance-partitions/create +++ b/gcloud/spanner/instance-partitions/create @@ -6,7 +6,9 @@ SYNOPSIS gcloud spanner instance-partitions create (INSTANCE_PARTITION : --instance=INSTANCE) --config=CONFIG --description=DESCRIPTION [--async] - [--nodes=NODES | --processing-units=PROCESSING_UNITS] + [--nodes=NODES | --processing-units=PROCESSING_UNITS + | --autoscaling-storage-target=AUTOSCALING_STORAGE_TARGET + (--autoscaling-high-priority-cpu-target=AUTOSCALING_HIGH_PRIORITY_CPU_TARGET --autoscaling-total-cpu-target=AUTOSCALING_TOTAL_CPU_TARGET) (--autoscaling-max-nodes=AUTOSCALING_MAX_NODES --autoscaling-min-nodes=AUTOSCALING_MIN_NODES | --autoscaling-max-processing-units=AUTOSCALING_MAX_PROCESSING_UNITS --autoscaling-min-processing-units=AUTOSCALING_MIN_PROCESSING_UNITS)] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -75,6 +77,59 @@ OPTIONAL FLAGS --processing-units=PROCESSING_UNITS Number of processing units for the instance partition. + Autoscaling + + --autoscaling-storage-target=AUTOSCALING_STORAGE_TARGET + Specifies the target percentage of storage the autoscaled instance + can utilize. + + This flag argument must be specified if any of the other arguments + in this group are specified. + + Autoscaling CPU targets. + + At least one of these must be specified: + + --autoscaling-high-priority-cpu-target=AUTOSCALING_HIGH_PRIORITY_CPU_TARGET + Specifies the target percentage of high-priority CPU the + autoscaled instance can utilize. + + --autoscaling-total-cpu-target=AUTOSCALING_TOTAL_CPU_TARGET + Specifies the target percentage of total CPU the autoscaled + instance can utilize. + + Autoscaling limits can be defined in either nodes or processing units. + + Exactly one of these must be specified: + + Autoscaling limits in nodes: + + --autoscaling-max-nodes=AUTOSCALING_MAX_NODES + Maximum number of nodes for the autoscaled instance. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --autoscaling-min-nodes=AUTOSCALING_MIN_NODES + Minimum number of nodes for the autoscaled instance. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + Autoscaling limits in processing units: + + --autoscaling-max-processing-units=AUTOSCALING_MAX_PROCESSING_UNITS + Maximum number of processing units for the autoscaled instance. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --autoscaling-min-processing-units=AUTOSCALING_MIN_PROCESSING_UNITS + Minimum number of processing units for the autoscaled instance. + + This flag argument must be specified if any of the other + arguments in this group are specified. + 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/spanner/instance-partitions/update b/gcloud/spanner/instance-partitions/update index af0cc67bd..ec8157164 100644 --- a/gcloud/spanner/instance-partitions/update +++ b/gcloud/spanner/instance-partitions/update @@ -7,7 +7,9 @@ SYNOPSIS gcloud spanner instance-partitions update (INSTANCE_PARTITION : --instance=INSTANCE) [--async] [--description=DESCRIPTION] - [--nodes=NODES | --processing-units=PROCESSING_UNITS] + [--nodes=NODES | --processing-units=PROCESSING_UNITS + | --autoscaling-storage-target=AUTOSCALING_STORAGE_TARGET + --autoscaling-high-priority-cpu-target=AUTOSCALING_HIGH_PRIORITY_CPU_TARGET --autoscaling-total-cpu-target=AUTOSCALING_TOTAL_CPU_TARGET --autoscaling-max-nodes=AUTOSCALING_MAX_NODES --autoscaling-min-nodes=AUTOSCALING_MIN_NODES | --autoscaling-max-processing-units=AUTOSCALING_MAX_PROCESSING_UNITS --autoscaling-min-processing-units=AUTOSCALING_MIN_PROCESSING_UNITS] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -75,6 +77,42 @@ FLAGS --processing-units=PROCESSING_UNITS Number of processing units for the instance partition. + Autoscaling + + --autoscaling-storage-target=AUTOSCALING_STORAGE_TARGET + Specifies the target percentage of storage the autoscaled instance + can utilize. + + Autoscaling CPU targets. + + --autoscaling-high-priority-cpu-target=AUTOSCALING_HIGH_PRIORITY_CPU_TARGET + Specifies the target percentage of high-priority CPU the + autoscaled instance can utilize. + + --autoscaling-total-cpu-target=AUTOSCALING_TOTAL_CPU_TARGET + Specifies the target percentage of total CPU the autoscaled + instance can utilize. + + Autoscaling limits can be defined in either nodes or processing units. + + At most one of these can be specified: + + Autoscaling limits in nodes: + + --autoscaling-max-nodes=AUTOSCALING_MAX_NODES + Maximum number of nodes for the autoscaled instance. + + --autoscaling-min-nodes=AUTOSCALING_MIN_NODES + Minimum number of nodes for the autoscaled instance. + + Autoscaling limits in processing units: + + --autoscaling-max-processing-units=AUTOSCALING_MAX_PROCESSING_UNITS + Maximum number of processing units for the autoscaled instance. + + --autoscaling-min-processing-units=AUTOSCALING_MIN_PROCESSING_UNITS + Minimum number of processing units for the autoscaled instance. + 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/spanner/instances/create b/gcloud/spanner/instances/create index 3c6967392..bad7fc339 100644 --- a/gcloud/spanner/instances/create +++ b/gcloud/spanner/instances/create @@ -8,13 +8,15 @@ SYNOPSIS [--edition=EDITION] [--expire-behavior=EXPIRE_BEHAVIOR] [--instance-type=INSTANCE_TYPE] [--nodes=NODES | --processing-units=PROCESSING_UNITS - | [--autoscaling-high-priority-cpu-target=AUTOSCALING_HIGH_PRIORITY_CPU_TARGET --autoscaling-storage-target=AUTOSCALING_STORAGE_TARGET (--autoscaling-max-nodes=AUTOSCALING_MAX_NODES --autoscaling-min-nodes=AUTOSCALING_MIN_NODES | --autoscaling-max-processing-units=AUTOSCALING_MAX_PROCESSING_UNITS --autoscaling-min-processing-units=AUTOSCALING_MIN_PROCESSING_UNITS) : --asymmetric-autoscaling-option=[disable_high_priority_cpu_autoscaling=DISABLE_HIGH_PRIORITY_CPU_AUTOSCALING], + | [--autoscaling-storage-target=AUTOSCALING_STORAGE_TARGET + (--autoscaling-high-priority-cpu-target=AUTOSCALING_HIGH_PRIORITY_CPU_TARGET --autoscaling-total-cpu-target=AUTOSCALING_TOTAL_CPU_TARGET) (--autoscaling-max-nodes=AUTOSCALING_MAX_NODES --autoscaling-min-nodes=AUTOSCALING_MIN_NODES | --autoscaling-max-processing-units=AUTOSCALING_MAX_PROCESSING_UNITS --autoscaling-min-processing-units=AUTOSCALING_MIN_PROCESSING_UNITS) : --asymmetric-autoscaling-option=[disable_high_priority_cpu_autoscaling=DISABLE_HIGH_PRIORITY_CPU_AUTOSCALING], [disable_total_cpu_autoscaling=DISABLE_TOTAL_CPU_AUTOSCALING], [high_priority_cpu_target=HIGH_PRIORITY_CPU_TARGET], [location=LOCATION],[max_nodes=MAX_NODES], [max_processing_units=MAX_PROCESSING_UNITS],[min_nodes=MIN_NODES], [min_processing_units=MIN_PROCESSING_UNITS], - [total_cpu_target=TOTAL_CPU_TARGET]]] [GCLOUD_WIDE_FLAG ...] + [total_cpu_target=TOTAL_CPU_TARGET] --[no-]disable-downscaling]] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION Create a Cloud Spanner instance. @@ -107,13 +109,6 @@ OPTIONAL FLAGS Autoscaling - --autoscaling-high-priority-cpu-target=AUTOSCALING_HIGH_PRIORITY_CPU_TARGET - Specifies the target percentage of high-priority CPU the autoscaled - instance can utilize. - - This flag argument must be specified if any of the other arguments - in this group are specified. - --autoscaling-storage-target=AUTOSCALING_STORAGE_TARGET Specifies the target percentage of storage the autoscaled instance can utilize. @@ -124,6 +119,23 @@ OPTIONAL FLAGS --asymmetric-autoscaling-option=[disable_high_priority_cpu_autoscaling=DISABLE_HIGH_PRIORITY_CPU_AUTOSCALING],[disable_total_cpu_autoscaling=DISABLE_TOTAL_CPU_AUTOSCALING],[high_priority_cpu_target=HIGH_PRIORITY_CPU_TARGET],[location=LOCATION],[max_nodes=MAX_NODES],[max_processing_units=MAX_PROCESSING_UNITS],[min_nodes=MIN_NODES],[min_processing_units=MIN_PROCESSING_UNITS],[total_cpu_target=TOTAL_CPU_TARGET] Specifies the asymmetric autoscaling option for the instance. + --[no-]disable-downscaling + Set the flag to disable downscaling for the autoscaled instance. + Use --disable-downscaling to enable and --no-disable-downscaling to + disable. + + Specify one or both CPU targets: + + At least one of these must be specified: + + --autoscaling-high-priority-cpu-target=AUTOSCALING_HIGH_PRIORITY_CPU_TARGET + Specifies the target percentage of high-priority CPU the + autoscaled instance can utilize. + + --autoscaling-total-cpu-target=AUTOSCALING_TOTAL_CPU_TARGET + Specifies the target percentage of total CPU the autoscaled + instance can utilize. + Autoscaling limits can be defined in either nodes or processing units. Exactly one of these must be specified: diff --git a/gcloud/spanner/instances/update b/gcloud/spanner/instances/update index 390f0547f..12a7d4719 100644 --- a/gcloud/spanner/instances/update +++ b/gcloud/spanner/instances/update @@ -7,7 +7,9 @@ SYNOPSIS [--description=DESCRIPTION] [--edition=EDITION] [--expire-behavior=EXPIRE_BEHAVIOR] [--instance-type=INSTANCE_TYPE] [--nodes=NODES | --processing-units=PROCESSING_UNITS - | --autoscaling-high-priority-cpu-target=AUTOSCALING_HIGH_PRIORITY_CPU_TARGET --autoscaling-storage-target=AUTOSCALING_STORAGE_TARGET --asymmetric-autoscaling-option=[disable_high_priority_cpu_autoscaling=DISABLE_HIGH_PRIORITY_CPU_AUTOSCALING], + | --autoscaling-storage-target=AUTOSCALING_STORAGE_TARGET + --[no-]disable-downscaling + --asymmetric-autoscaling-option=[disable_high_priority_cpu_autoscaling=DISABLE_HIGH_PRIORITY_CPU_AUTOSCALING], [disable_total_cpu_autoscaling=DISABLE_TOTAL_CPU_AUTOSCALING], [high_priority_cpu_target=HIGH_PRIORITY_CPU_TARGET], [location=LOCATION],[max_nodes=MAX_NODES], @@ -15,10 +17,7 @@ SYNOPSIS [min_processing_units=MIN_PROCESSING_UNITS], [total_cpu_target=TOTAL_CPU_TARGET] | --clear-asymmetric-autoscaling-option=LOCATION,[LOCATION,...] - --autoscaling-max-nodes=AUTOSCALING_MAX_NODES - --autoscaling-min-nodes=AUTOSCALING_MIN_NODES - | --autoscaling-max-processing-units=AUTOSCALING_MAX_PROCESSING_UNITS - --autoscaling-min-processing-units=AUTOSCALING_MIN_PROCESSING_UNITS] + --autoscaling-high-priority-cpu-target=AUTOSCALING_HIGH_PRIORITY_CPU_TARGET --autoscaling-total-cpu-target=AUTOSCALING_TOTAL_CPU_TARGET --autoscaling-max-nodes=AUTOSCALING_MAX_NODES --autoscaling-min-nodes=AUTOSCALING_MIN_NODES | --autoscaling-max-processing-units=AUTOSCALING_MAX_PROCESSING_UNITS --autoscaling-min-processing-units=AUTOSCALING_MIN_PROCESSING_UNITS] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -106,14 +105,15 @@ FLAGS Autoscaling - --autoscaling-high-priority-cpu-target=AUTOSCALING_HIGH_PRIORITY_CPU_TARGET - Specifies the target percentage of high-priority CPU the autoscaled - instance can utilize. - --autoscaling-storage-target=AUTOSCALING_STORAGE_TARGET Specifies the target percentage of storage the autoscaled instance can utilize. + --[no-]disable-downscaling + Set the flag to disable downscaling for the autoscaled instance. + Use --disable-downscaling to enable and --no-disable-downscaling to + disable. + At most one of these can be specified: --asymmetric-autoscaling-option=[disable_high_priority_cpu_autoscaling=DISABLE_HIGH_PRIORITY_CPU_AUTOSCALING],[disable_total_cpu_autoscaling=DISABLE_TOTAL_CPU_AUTOSCALING],[high_priority_cpu_target=HIGH_PRIORITY_CPU_TARGET],[location=LOCATION],[max_nodes=MAX_NODES],[max_processing_units=MAX_PROCESSING_UNITS],[min_nodes=MIN_NODES],[min_processing_units=MIN_PROCESSING_UNITS],[total_cpu_target=TOTAL_CPU_TARGET] @@ -123,6 +123,16 @@ FLAGS Specify a comma separated list of locations from which to remove asymmetric autoscaling options + Specify one or both CPU targets: + + --autoscaling-high-priority-cpu-target=AUTOSCALING_HIGH_PRIORITY_CPU_TARGET + Specifies the target percentage of high-priority CPU the + autoscaled instance can utilize. + + --autoscaling-total-cpu-target=AUTOSCALING_TOTAL_CPU_TARGET + Specifies the target percentage of total CPU the autoscaled + instance can utilize. + Autoscaling limits can be defined in either nodes or processing units. At most one of these can be specified: diff --git a/gcloud/storage/batch-operations/jobs/create b/gcloud/storage/batch-operations/jobs/create index e7fe7b549..7cec221ea 100644 --- a/gcloud/storage/batch-operations/jobs/create +++ b/gcloud/storage/batch-operations/jobs/create @@ -11,6 +11,7 @@ SYNOPSIS | [--delete-object : --enable-permanent-object-deletion] | --[no-]put-object-event-based-hold --[no-]put-object-temporary-hold) [--description=DESCRIPTION] + [--dry-run] [--log-actions=[LOG_ACTIONS,...] --log-action-states=[LOG_ACTION_STATES,...]] [GCLOUD_WIDE_FLAG ...] @@ -19,6 +20,15 @@ DESCRIPTION deletion, updating metadata, and more on objects in a serverless manner. EXAMPLES + The following example command creates a batch job, named my-dry-run, that + performs a dry run of object deletion on bucket my-bucket for objects + specified in the manifest file gs://my-bucket/manifest.csv: + + $ gcloud storage batch-operations jobs create my-dry-run-job \ + --bucket=my-bucket \ + --manifest-location=gs://my-bucket/manifest.csv \ + --delete-object --dry-run + The following example command creates a batch job, named my-job, that performs object deletion on bucket my-bucket for objects specified in the manifest file gs://my-bucket/manifest.csv: @@ -159,6 +169,11 @@ FLAGS --description=DESCRIPTION Description for the batch job. + --dry-run + If true, the job will run in dry run mode, returning the total object + count and, if the object configuration is a prefix list, the bytes + found from source. No transformations will be performed. + LOGGING_CONFIG FLAGS LOGGING CONFIG diff --git a/gcloud/storage/cp b/gcloud/storage/cp index b778f87d7..97161f157 100644 --- a/gcloud/storage/cp +++ b/gcloud/storage/cp @@ -176,9 +176,13 @@ FLAGS --read-paths-from-stdin, -I Read the list of resources to copy from stdin. No need to enter a source argument if this flag is present. Example: "storage cp -I - gs://bucket/destination" Note: To copy the contents of one file - directly from stdin, use "-" as the source argument without the "-I" - flag. + gs://bucket/destination". The input format must consist of one path + (e.g., "Documents/data/file1.txt") or one object URL (e.g., + "gs://example-bucket/event.log") per line. Use a pipe to send the file + list to the command. Example: "cat example-file-list.txt | gcloud + storage cp --read-paths-from-stdin gs://example-destination-bucket". + Note: To copy the contents of one file directly from stdin, use "-" as + the source argument without the "-I" flag. --recursive, -R, -r Recursively copy the contents of any directories that match the source diff --git a/gcloud/storage/mv b/gcloud/storage/mv index 72658e774..49ec0b121 100644 --- a/gcloud/storage/mv +++ b/gcloud/storage/mv @@ -181,9 +181,13 @@ FLAGS --read-paths-from-stdin, -I Read the list of resources to copy from stdin. No need to enter a source argument if this flag is present. Example: "storage cp -I - gs://bucket/destination" Note: To copy the contents of one file - directly from stdin, use "-" as the source argument without the "-I" - flag. + gs://bucket/destination". The input format must consist of one path + (e.g., "Documents/data/file1.txt") or one object URL (e.g., + "gs://example-bucket/event.log") per line. Use a pipe to send the file + list to the command. Example: "cat example-file-list.txt | gcloud + storage cp --read-paths-from-stdin gs://example-destination-bucket". + Note: To copy the contents of one file directly from stdin, use "-" as + the source argument without the "-I" flag. --skip-unsupported, -U Skip objects with unsupported object types. diff --git a/gcloud/transfer/jobs/create b/gcloud/transfer/jobs/create index d02f99c08..a6e6053d3 100644 --- a/gcloud/transfer/jobs/create +++ b/gcloud/transfer/jobs/create @@ -16,7 +16,7 @@ SYNOPSIS --schedule-repeats-every=SCHEDULE_REPEATS_EVERY --schedule-repeats-until=SCHEDULE_REPEATS_UNTIL] [--include-prefixes=[INCLUDED_PREFIXES,...] - --exclude-prefixes=[EXCLUDED_PREFIXES,...] + --exclude-prefixes=[EXCLUDED_PREFIXES,...] --match-glob=MATCH_GLOB --include-modified-before-absolute=INCLUDE_MODIFIED_BEFORE_ABSOLUTE --include-modified-after-absolute=INCLUDE_MODIFIED_AFTER_ABSOLUTE --include-modified-before-relative=INCLUDE_MODIFIED_BEFORE_RELATIVE @@ -260,6 +260,11 @@ FLAGS multiple prefixes with commas, omitting spaces after the commas (e.g., --exclude-prefixes=foo,bar). + --match-glob=MATCH_GLOB + Include only objects that match the specified glob pattern. For more + information about glob patterns, see + https://docs.cloud.google.com/storage-transfer/docs/filter-by-glob-pattern + --include-modified-before-absolute=INCLUDE_MODIFIED_BEFORE_ABSOLUTE Include objects last modified before an absolute date/time. Ex. by specifying '2020-01-01', the transfer would include objects last diff --git a/gcloud/transfer/jobs/update b/gcloud/transfer/jobs/update index e1949dda1..d0b4506b5 100644 --- a/gcloud/transfer/jobs/update +++ b/gcloud/transfer/jobs/update @@ -18,13 +18,13 @@ SYNOPSIS [--clear-schedule --schedule-starts=SCHEDULE_STARTS --schedule-repeats-every=SCHEDULE_REPEATS_EVERY --schedule-repeats-until=SCHEDULE_REPEATS_UNTIL] - [--clear-include-prefixes --clear-exclude-prefixes + [--clear-include-prefixes --clear-exclude-prefixes --clear-match-glob --clear-include-modified-before-absolute --clear-include-modified-after-absolute --clear-include-modified-before-relative --clear-include-modified-after-relative --include-prefixes=[INCLUDED_PREFIXES,...] - --exclude-prefixes=[EXCLUDED_PREFIXES,...] + --exclude-prefixes=[EXCLUDED_PREFIXES,...] --match-glob=MATCH_GLOB --include-modified-before-absolute=INCLUDE_MODIFIED_BEFORE_ABSOLUTE --include-modified-after-absolute=INCLUDE_MODIFIED_AFTER_ABSOLUTE --include-modified-before-relative=INCLUDE_MODIFIED_BEFORE_RELATIVE @@ -279,6 +279,9 @@ FLAGS Remove the list of object prefixes to exclude from the object conditions. + --clear-match-glob + Remove the glob pattern from the object conditions. + --clear-include-modified-before-absolute Remove the maximum modification datetime from the object conditions. @@ -303,6 +306,11 @@ FLAGS multiple prefixes with commas, omitting spaces after the commas (e.g., --exclude-prefixes=foo,bar). + --match-glob=MATCH_GLOB + Include only objects that match the specified glob pattern. For more + information about glob patterns, see + https://docs.cloud.google.com/storage-transfer/docs/filter-by-glob-pattern + --include-modified-before-absolute=INCLUDE_MODIFIED_BEFORE_ABSOLUTE Include objects last modified before an absolute date/time. Ex. by specifying '2020-01-01', the transfer would include objects last diff --git a/gcloud/vmware/datastores/create b/gcloud/vmware/datastores/create new file mode 100644 index 000000000..db5c4530e --- /dev/null +++ b/gcloud/vmware/datastores/create @@ -0,0 +1,124 @@ +NAME + gcloud vmware datastores create - create a datastore + +SYNOPSIS + gcloud vmware datastores create (DATASTORE : --location=LOCATION) + (--filestore=FILESTORE | --netapp=NETAPP + | --third-party-nfs-file-share=THIRD_PARTY_NFS_FILE_SHARE + --third-party-nfs-network=THIRD_PARTY_NFS_NETWORK + --third-party-nfs-servers=SERVER,[SERVER,...]) [--async] + [--description=DESCRIPTION] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Create a datastore. Datastore creation is considered finished when the + datastore is in ACTIVE state. Check the progress of a datastore using + gcloud vmware datastores list. + +EXAMPLES + To create a datastore named my-datastore in us-west2-a connected to + filestore instance + projects/my-project/locations/us-west2-a/instances/my-filestore-instance, + run: + + $ gcloud vmware datastores create my-datastore \ + --location=us-west2-a --project=my-project \ + --filestore=projects/my-project/locations/us-west2-a/instances/\ + my-filestore-instance + + Or: + + $ gcloud vmware datastores create my-datastore \ + --filestore=projects/my-project/locations/us-west2-a/instances/\ + my-filestore-instance + + Or: + + $ gcloud vmware datastores create my-datastore \ + --netapp=projects/my-project/locations/us-west2-a/volumes/\ + my-netapp-volume + + Or: + + $ gcloud vmware datastores create my-datastore \ + --third-party-nfs-network=my-network \ + --third-party-nfs-file-share=my-fileshare \ + --third-party-nfs-servers=10.0.0.1,10.0.0.2 \ + --location=us-west2-a --project=my-project + + In the second example, the project and location are taken from gcloud + properties core/project and compute/zone. + +POSITIONAL ARGUMENTS + Datastore resource - datastore. The arguments in this group can be used to + specify the attributes of this resource. (NOTE) Some attributes are not + given arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument datastore 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. + + DATASTORE + ID of the datastore or fully qualified identifier for the datastore. + + To set the datastore attribute: + ▸ provide the argument datastore on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Location of the private cloud or cluster. + + To set the location attribute: + ▸ provide the argument datastore on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property compute/zone. + +REQUIRED FLAGS + Exactly one of these must be specified: + + --filestore=FILESTORE + Google Filestore instance to be used as datastore. + + --netapp=NETAPP + Google NetApp volume to be used as datastore. + + --third-party-nfs-file-share=THIRD_PARTY_NFS_FILE_SHARE + Mount folder name of NFS. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --third-party-nfs-network=THIRD_PARTY_NFS_NETWORK + Network name of NFS's VPC. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --third-party-nfs-servers=SERVER,[SERVER,...] + Comma-separated list of server IP addresses of the NFS file service. + + This flag argument must be specified if any of the other arguments in + this group are specified. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. The default is True. Enabled by default, use --no-async to + disable. + + --description=DESCRIPTION + Text describing the datastore. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. diff --git a/gcloud/vmware/datastores/delete b/gcloud/vmware/datastores/delete new file mode 100644 index 000000000..85c88d15f --- /dev/null +++ b/gcloud/vmware/datastores/delete @@ -0,0 +1,70 @@ +NAME + gcloud vmware datastores delete - delete a datastore + +SYNOPSIS + gcloud vmware datastores delete (DATASTORE : --location=LOCATION) [--async] + [--etag=ETAG] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Delete a datastore. + +EXAMPLES + To delete a datastore named my-datastore in location us-west2-a, run: + + $ gcloud vmware datastores delete my-datastore \ + --location=us-west2-a --project=my-project + + Or: + + $ gcloud vmware datastores delete my-datastore + + In the second example, the project and location are taken from gcloud + properties core/project and compute/zone. + +POSITIONAL ARGUMENTS + Datastore resource - datastore. The arguments in this group can be used to + specify the attributes of this resource. (NOTE) Some attributes are not + given arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument datastore 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. + + DATASTORE + ID of the datastore or fully qualified identifier for the datastore. + + To set the datastore attribute: + ▸ provide the argument datastore on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Location of the private cloud or cluster. + + To set the location attribute: + ▸ provide the argument datastore on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property compute/zone. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. The default is True. Enabled by default, use --no-async to + disable. + + --etag=ETAG + Etag of the datastore. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. diff --git a/gcloud/vmware/datastores/describe b/gcloud/vmware/datastores/describe new file mode 100644 index 000000000..ee4ff9a84 --- /dev/null +++ b/gcloud/vmware/datastores/describe @@ -0,0 +1,61 @@ +NAME + gcloud vmware datastores describe - describe a datastore + +SYNOPSIS + gcloud vmware datastores describe (DATASTORE : --location=LOCATION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Describe a datastore. + +EXAMPLES + To describe a datastore named my-datastore in location us-west2-a, run: + + $ gcloud vmware datastores describe my-datastore \ + --location=us-west2-a --project=my-project + + Or: + + $ gcloud vmware datastores describe my-datastore + + In the second example, the project and location are taken from gcloud + properties core/project and compute/zone. + +POSITIONAL ARGUMENTS + Datastore resource - datastore. The arguments in this group can be used to + specify the attributes of this resource. (NOTE) Some attributes are not + given arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument datastore 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. + + DATASTORE + ID of the datastore or fully qualified identifier for the datastore. + + To set the datastore attribute: + ▸ provide the argument datastore on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Location of the private cloud or cluster. + + To set the location attribute: + ▸ provide the argument datastore on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property compute/zone. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. diff --git a/gcloud/vmware/datastores/help b/gcloud/vmware/datastores/help new file mode 100644 index 000000000..b9879a363 --- /dev/null +++ b/gcloud/vmware/datastores/help @@ -0,0 +1,32 @@ +NAME + gcloud vmware datastores - manage VMware Engine datastores in Google Cloud + VMware Engine + +SYNOPSIS + gcloud vmware datastores COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Manage VMware Engine datastores in Google Cloud VMware Engine. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + create + Create a datastore. + + delete + Delete a datastore. + + describe + Describe a datastore. + + list + List datastores. + + update + Update a datastore. diff --git a/gcloud/vmware/datastores/list b/gcloud/vmware/datastores/list new file mode 100644 index 000000000..1878f9701 --- /dev/null +++ b/gcloud/vmware/datastores/list @@ -0,0 +1,82 @@ +NAME + gcloud vmware datastores list - list datastores + +SYNOPSIS + gcloud vmware datastores list [--location=LOCATION] [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + List datastores. + +EXAMPLES + To list datastores in location us-west2-a, run: + + $ gcloud vmware datastores list --location=us-west2-a \ + --project=my-project + + Or: + + $ gcloud vmware datastores list + + In the second example, the project and location are taken from gcloud + properties core/project and compute/zone. + +FLAGS + Location resource - location. This represents a Cloud resource. (NOTE) + Some attributes are not given arguments in this group but can be set in + other ways. + + To set the project attribute: + ◆ provide the argument --location on the command line with a fully + specified name; + ◆ set the property compute/zone with a fully specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + --location=LOCATION + ID of the location or fully qualified identifier for the location. + + To set the location attribute: + ▸ provide the argument --location on the command line; + ▸ set the property compute/zone. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. diff --git a/gcloud/vmware/datastores/update b/gcloud/vmware/datastores/update new file mode 100644 index 000000000..ecd623216 --- /dev/null +++ b/gcloud/vmware/datastores/update @@ -0,0 +1,73 @@ +NAME + gcloud vmware datastores update - update a datastore + +SYNOPSIS + gcloud vmware datastores update (DATASTORE : --location=LOCATION) [--async] + [--description=DESCRIPTION] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Update a datastore. + +EXAMPLES + To update a datastore named my-datastore in location us-west2-a with a new + description, run: + + $ gcloud vmware datastores update my-datastore \ + --location=us-west2-a --project=my-project \ + --description="new description" + + Or: + + $ gcloud vmware datastores update my-datastore \ + --description="new description" + + In the second example, the project and location are taken from gcloud + properties core/project and compute/zone. + +POSITIONAL ARGUMENTS + Datastore resource - datastore. The arguments in this group can be used to + specify the attributes of this resource. (NOTE) Some attributes are not + given arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument datastore 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. + + DATASTORE + ID of the datastore or fully qualified identifier for the datastore. + + To set the datastore attribute: + ▸ provide the argument datastore on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Location of the private cloud or cluster. + + To set the location attribute: + ▸ provide the argument datastore on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property compute/zone. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. The default is True. Enabled by default, use --no-async to + disable. + + --description=DESCRIPTION + New description for the datastore. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. diff --git a/gcloud/vmware/help b/gcloud/vmware/help index 94a031726..8dc36ed99 100644 --- a/gcloud/vmware/help +++ b/gcloud/vmware/help @@ -18,6 +18,9 @@ GROUPS announcements Manage announcements in Google Cloud VMware Engine. + datastores + Manage VMware Engine datastores in Google Cloud VMware Engine. + dns-bind-permission Manage DNS binding permission in Google Cloud VMware Engine. diff --git a/gcloud/vmware/private-clouds/clusters/help b/gcloud/vmware/private-clouds/clusters/help index d8b063500..714bbc6c2 100644 --- a/gcloud/vmware/private-clouds/clusters/help +++ b/gcloud/vmware/private-clouds/clusters/help @@ -35,5 +35,11 @@ COMMANDS list List clusters in a Google Cloud VMware Engine private cloud. + mount-datastore + Mount a datastore to a Google Cloud VMware Engine cluster. + + unmount-datastore + Unmount a datastore from a Google Cloud VMware Engine cluster. + update Update a Google Cloud VMware Engine cluster. diff --git a/gcloud/vmware/private-clouds/clusters/mount-datastore b/gcloud/vmware/private-clouds/clusters/mount-datastore new file mode 100644 index 000000000..6627e088c --- /dev/null +++ b/gcloud/vmware/private-clouds/clusters/mount-datastore @@ -0,0 +1,140 @@ +NAME + gcloud vmware private-clouds clusters mount-datastore - mount a datastore + to a Google Cloud VMware Engine cluster + +SYNOPSIS + gcloud vmware private-clouds clusters mount-datastore + (CLUSTER : --location=LOCATION --private-cloud=PRIVATE_CLOUD) + --datastore=DATASTORE + (--datastore-network=PATH_TO_FILE + | [--subnet=SUBNET : --connection-count=CONNECTION_COUNT --mtu=MTU]) + [--access-mode=ACCESS_MODE] [--async] [--ignore-colocation] + [--nfs-version=NFS_VERSION] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Mount a datastore to a cluster in a VMware Engine private cloud. + +EXAMPLES + To mount a datastore my-datastore to cluster my-cluster in private cloud + my-private-cloud in zone us-west2-a, providing subnet, run: + + $ gcloud vmware private-clouds clusters mount-datastore my-cluster \ + --location=us-west2-a --project=my-project \ + --private-cloud=my-private-cloud \ + --datastore=projects/my-project/locations/us-west2-a/\ + datastores/my-datastore --subnet=my-subnet + + Or: + + $ gcloud vmware private-clouds clusters mount-datastore my-cluster \ + --private-cloud=my-private-cloud \ + --datastore=projects/my-project/locations/us-west2-a/\ + datastores/my-datastore --subnet=my-subnet + + To mount a datastore my-datastore to cluster my-cluster in private cloud + my-private-cloud in zone us-west2-a, providing a json file for datastore + network, run: + + $ gcloud vmware private-clouds clusters mount-datastore my-cluster \ + --location=us-west2-a --project=my-project \ + --private-cloud=my-private-cloud \ + --datastore=projects/my-project/locations/us-west2-a/\ + datastores/my-datastore --datastore-network=network-config.json + + Where `network-config.json` contains: + { + "subnet": "my-subnet", + "mtu": 1500, + "connection-count": 4 + } + + In the examples without location and project, the project and location are taken from gcloud properties core/project and compute/zone. + +POSITIONAL ARGUMENTS + Cluster resource - cluster. The arguments in this group can be used to + specify the attributes of this resource. (NOTE) Some attributes are not + given arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument cluster on the command line with a fully + specified name; + ◆ 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. + + --location=LOCATION + Location of the private cloud or cluster. + + To set the location attribute: + ▸ provide the argument cluster on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property compute/zone. + + --private-cloud=PRIVATE_CLOUD + VMware Engine private cloud. + + To set the private-cloud attribute: + ▸ provide the argument cluster on the command line with a fully + specified name; + ▸ provide the argument --private-cloud on the command line. + +REQUIRED FLAGS + --datastore=DATASTORE + The datastore resource name to mount. + + Exactly one of these must be specified: + + --datastore-network=PATH_TO_FILE + Path to a JSON file containing the datastore network configuration. + Use a full or relative path to a local file containing the value of + datastore_network. + + Datastore network configuration if not providing via file. + + --subnet=SUBNET + Subnet to use for inlined datastore network configuration. + + This flag argument must be specified if any of the other arguments + in this group are specified. + + --connection-count=CONNECTION_COUNT + Connection count for inlined datastore network configuration. + + --mtu=MTU + MTU for inlined datastore network configuration. + +OPTIONAL FLAGS + --access-mode=ACCESS_MODE + Access mode for the datastore. ACCESS_MODE must be one of: READ_WRITE, + READ_ONLY. + + --async + Return immediately, without waiting for the operation in progress to + complete. The default is True. Enabled by default, use --no-async to + disable. + + --ignore-colocation + If set, ignore colocation checks. + + --nfs-version=NFS_VERSION + NFS version for the datastore. NFS_VERSION must be one of: NFS_V3, + NFS_V4. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. diff --git a/gcloud/vmware/private-clouds/clusters/unmount-datastore b/gcloud/vmware/private-clouds/clusters/unmount-datastore new file mode 100644 index 000000000..7cedcf030 --- /dev/null +++ b/gcloud/vmware/private-clouds/clusters/unmount-datastore @@ -0,0 +1,87 @@ +NAME + gcloud vmware private-clouds clusters unmount-datastore - unmount a + datastore from a Google Cloud VMware Engine cluster + +SYNOPSIS + gcloud vmware private-clouds clusters unmount-datastore + (CLUSTER : --location=LOCATION --private-cloud=PRIVATE_CLOUD) + --datastore=DATASTORE [--async] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Unmount a datastore from a cluster in a VMware Engine private cloud. + +EXAMPLES + To unmount a datastore my-datastore from cluster my-cluster in private + cloud my-private-cloud in zone us-west2-a, run: + + $ gcloud vmware private-clouds clusters unmount-datastore \ + my-cluster --location=us-west2-a --project=my-project \ + --private-cloud=my-private-cloud \ + --datastore=projects/my-project/locations/us-west2-a/\ + datastores/my-datastore + + Or: + + $ gcloud vmware private-clouds clusters unmount-datastore \ + my-cluster --private-cloud=my-private-cloud \ + --datastore=projects/my-project/locations/us-west2-a/\ + datastores/my-datastore + + In the second example, the project and location are taken from gcloud properties core/project and compute/zone. + +POSITIONAL ARGUMENTS + Cluster resource - cluster. The arguments in this group can be used to + specify the attributes of this resource. (NOTE) Some attributes are not + given arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument cluster on the command line with a fully + specified name; + ◆ 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. + + --location=LOCATION + Location of the private cloud or cluster. + + To set the location attribute: + ▸ provide the argument cluster on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property compute/zone. + + --private-cloud=PRIVATE_CLOUD + VMware Engine private cloud. + + To set the private-cloud attribute: + ▸ provide the argument cluster on the command line with a fully + specified name; + ▸ provide the argument --private-cloud on the command line. + +REQUIRED FLAGS + --datastore=DATASTORE + The datastore resource name to unmount. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. The default is True. Enabled by default, use --no-async to + disable. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. diff --git a/gcloud/workbench/instances/create b/gcloud/workbench/instances/create index 2d05a65a1..dea664814 100644 --- a/gcloud/workbench/instances/create +++ b/gcloud/workbench/instances/create @@ -190,7 +190,7 @@ FLAGS NVIDIA_TESLA_P4, NVIDIA_TESLA_T4, NVIDIA_TESLA_A100, NVIDIA_A100_80GB, NVIDIA_TESLA_T4_VWS, NVIDIA_TESLA_P100_VWS, NVIDIA_TESLA_P4_VWS, NVIDIA_L4, NVIDIA_H100_80GB, - NVIDIA_H100_MEGA_80GB. + NVIDIA_H100_MEGA_80GB, NVIDIA_H200_141GB, NVIDIA_B200. Boot disk configurations. diff --git a/gcloud/workbench/instances/update b/gcloud/workbench/instances/update index 3cbd61184..69090eb8a 100644 --- a/gcloud/workbench/instances/update +++ b/gcloud/workbench/instances/update @@ -97,7 +97,7 @@ FLAGS NVIDIA_TESLA_P4, NVIDIA_TESLA_T4, NVIDIA_TESLA_A100, NVIDIA_A100_80GB, NVIDIA_TESLA_T4_VWS, NVIDIA_TESLA_P100_VWS, NVIDIA_TESLA_P4_VWS, NVIDIA_L4, NVIDIA_H100_80GB, - NVIDIA_H100_MEGA_80GB. + NVIDIA_H100_MEGA_80GB, NVIDIA_H200_141GB, NVIDIA_B200. Container image configurations. diff --git a/gcloud/workstations/configs/create b/gcloud/workstations/configs/create index 0ab3187f7..82b3cb459 100644 --- a/gcloud/workstations/configs/create +++ b/gcloud/workstations/configs/create @@ -16,7 +16,8 @@ SYNOPSIS [--enable-confidential-compute] [--enable-nested-virtualization] [--enable-ssh-to-vm] [--ephemeral-directory=[PROPERTY=VALUE,...]] [--grant-workstation-admin-role-on-create] - [--idle-timeout=IDLE_TIMEOUT; default=7200] [--labels=[LABELS,...]] + [--idle-timeout=IDLE_TIMEOUT; default=7200] + [--instance-metadata=[INSTANCE_METADATA,...]] [--labels=[LABELS,...]] [--machine-type=MACHINE_TYPE; default="e2-standard-4"] [--max-usable-workstations-count=MAX_USABLE_WORKSTATIONS_COUNT] [--network-tags=[NETWORK_TAGS,...]] [--pool-size=POOL_SIZE] @@ -33,8 +34,11 @@ SYNOPSIS | --container-predefined-image=CONTAINER_PREDEFINED_IMAGE; default="codeoss"] [--kms-key=KMS_KEY : --kms-key-service-account=KMS_KEY_SERVICE_ACCOUNT] - [--no-persistent-storage | --pd-disk-type=PD_DISK_TYPE; - default="pd-standard" --pd-reclaim-policy=PD_RECLAIM_POLICY; + [--no-persistent-storage | --disk-reclaim-policy=DISK_RECLAIM_POLICY; + default="delete" --disk-type=DISK_TYPE --disk-size=DISK_SIZE + | --disk-source-snapshot=DISK_SOURCE_SNAPSHOT + | --pd-disk-type=PD_DISK_TYPE; default="pd-standard" + --pd-reclaim-policy=PD_RECLAIM_POLICY; default="delete" --pd-disk-size=PD_DISK_SIZE; default=200 | --pd-source-snapshot=PD_SOURCE_SNAPSHOT] [GCLOUD_WIDE_FLAG ...] @@ -246,6 +250,14 @@ FLAGS that hasn't received any user traffic. A value of 0 indicates that this instance should never time out due to idleness. + --instance-metadata=[INSTANCE_METADATA,...] + Custom metadata to apply to Compute Engine instances. + + Example: + + $ gcloud workstations configs create \ + --instance-metadata=key1=value1,key2=value2 + --labels=[LABELS,...] Labels that are applied to the configuration and propagated to the underlying Compute Engine resources. @@ -402,6 +414,29 @@ FLAGS If set, workstations under this configuration will not have a persistent directory. + --disk-reclaim-policy=DISK_RECLAIM_POLICY; default="delete" + What should happen to the disk after the Workstation is deleted. + DISK_RECLAIM_POLICY must be one of: + + delete + The persistent disk will be deleted with the Workstation. + retain + The persistent disk will be remain after the workstation is + deleted and the administrator must manually delete the disk. + + --disk-type=DISK_TYPE + Type of the persistent directory. DISK_TYPE must be one of: + pd-standard, pd-balanced, pd-ssd, hyperdisk-balanced-ha. + + At most one of these can be specified: + + --disk-size=DISK_SIZE + Size of the persistent directory in GB. DISK_SIZE must be one of: + 10, 50, 100, 200, 500, 1000. + + --disk-source-snapshot=DISK_SOURCE_SNAPSHOT + Name of the snapshot to use as the source for the home disk. + --pd-disk-type=PD_DISK_TYPE; default="pd-standard" Type of the persistent directory. PD_DISK_TYPE must be one of: pd-standard, pd-balanced, pd-ssd. diff --git a/gcloud/workstations/configs/update b/gcloud/workstations/configs/update index 3d71d3635..27e8a7bfb 100644 --- a/gcloud/workstations/configs/update +++ b/gcloud/workstations/configs/update @@ -14,7 +14,8 @@ SYNOPSIS [--disable-public-ip-addresses] [--enable-audit-agent] [--enable-confidential-compute] [--enable-nested-virtualization] [--grant-workstation-admin-role-on-create] - [--idle-timeout=IDLE_TIMEOUT] [--labels=[LABELS,...]] + [--idle-timeout=IDLE_TIMEOUT] + [--instance-metadata=[INSTANCE_METADATA,...]] [--labels=[LABELS,...]] [--machine-type=MACHINE_TYPE] [--max-usable-workstations-count=MAX_USABLE_WORKSTATIONS_COUNT] [--network-tags=[NETWORK_TAGS,...]] [--pool-size=POOL_SIZE] @@ -29,7 +30,10 @@ SYNOPSIS | --container-predefined-image=CONTAINER_PREDEFINED_IMAGE] [--disable-ssh-to-vm | --enable-ssh-to-vm] [--disable-tcp-connections | --enable-tcp-connections] - [--pd-source-snapshot=PD_SOURCE_SNAPSHOT | --pd-disk-size=PD_DISK_SIZE + [--disk-source-snapshot=DISK_SOURCE_SNAPSHOT + | --pd-source-snapshot=PD_SOURCE_SNAPSHOT + | --disk-size=DISK_SIZE --disk-type=DISK_TYPE + | --pd-disk-size=PD_DISK_SIZE --pd-disk-type=PD_DISK_TYPE; default="pd-standard"] [GCLOUD_WIDE_FLAG ...] @@ -188,6 +192,14 @@ FLAGS that hasn't received any user traffic. A value of 0 indicates that this instance should never time out due to idleness. + --instance-metadata=[INSTANCE_METADATA,...] + Custom metadata to apply to Compute Engine instances. + + Example: + + $ gcloud workstations configs update \ + --instance-metadata=key1=value1,key2=value2 + --labels=[LABELS,...] Labels that are applied to the configuration and propagated to the underlying Compute Engine resources. @@ -333,10 +345,21 @@ FLAGS At most one of these can be specified: + --disk-source-snapshot=DISK_SOURCE_SNAPSHOT + Name of the snapshot to use as the source for the home disk. + --pd-source-snapshot=PD_SOURCE_SNAPSHOT Name of the snapshot to use as the source for the persistent directory. + --disk-size=DISK_SIZE + Size of the persistent directory in GB. DISK_SIZE must be one of: 10, + 50, 100, 200, 500, 1000. + + --disk-type=DISK_TYPE + Type of the persistent directory. DISK_TYPE must be one of: + pd-standard, pd-balanced, pd-ssd, hyperdisk-balanced-ha. + --pd-disk-size=PD_DISK_SIZE Size of the persistent directory in GB. PD_DISK_SIZE must be one of: 10, 50, 100, 200, 500, 1000.