gcloud: Wed Aug 23 10:30:46 UTC 2023

gcloud/compute/routers/get-nat-ip-info

@@ -0,0 +1,69 @@
+NAME
+    gcloud compute routers get-nat-ip-info - display NAT IP information in a
+        router
+
+SYNOPSIS
+    gcloud compute routers get-nat-ip-info NAME [--nat-name=NAT_NAME]
+        [--region=REGION] [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+        $ gcloud compute routers get-nat-ip-info
+
+    shows a mapping of IP:[usage, mode] allocated to each NAT via the specified
+    router.
+
+EXAMPLES
+    To show NAT IP information from all NATs in router 'r1' in region
+    'us-central1', run:
+
+        $ gcloud compute routers get-nat-ip-info r1 --region=us-central1
+
+    To show NAT IP information for a specific NAT 'nat1' in router 'r1' in
+    region 'us-central1', run:
+
+        $ gcloud compute routers get-nat-ip-info r1 --region=us-central1 \
+          --nat-name="nat1"
+
+POSITIONAL ARGUMENTS
+     NAME
+        Name of the router to get NAT IP info.
+
+FLAGS
+     --nat-name=NAT_NAME
+        The NAT name to filter out NAT IP information
+
+     --region=REGION
+        Region of the router to get NAT IP info. If not specified, you might be
+        prompted to select a region (interactive mode only).
+
+        To avoid prompting when this flag is omitted, you can set the
+        compute/region property:
+
+            $ gcloud config set compute/region REGION
+
+        A list of regions can be fetched by running:
+
+            $ gcloud compute regions list
+
+        To unset the property, run:
+
+            $ gcloud config unset compute/region
+
+        Alternatively, the region can be stored in the environment variable
+        CLOUDSDK_COMPUTE_REGION.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    These variants are also available:
+
+        $ gcloud alpha compute routers get-nat-ip-info
+
+        $ gcloud beta compute routers get-nat-ip-info
+

gcloud/compute/routers/help

@@ -43,6 +43,9 @@ COMMANDS
      describe
         Describe a Compute Engine router.
 
+     get-nat-ip-info
+        Display NAT IP information in a router.
+
      get-nat-mapping-info
         Display NAT Mapping information in a router.
 

gcloud/compute/tpus/tpu-vm/create

@@ -3,9 +3,9 @@ NAME
 
 SYNOPSIS
     gcloud compute tpus tpu-vm create (TPU : --zone=ZONE) --version=VERSION
-        [--async] [--data-disk=DATA_DISK] [--description=DESCRIPTION]
-        [--internal-ips] [--labels=[LABELS,...]] [--metadata=[METADATA,...]]
-        [--metadata-from-file=[METADATA_FROM_FILE,...]]
+        [--async] [--data-disk=[mode=MODE],[source=SOURCE]]
+        [--description=DESCRIPTION] [--internal-ips] [--labels=[KEY=VALUE,...]]
+        [--metadata=[KEY=VALUE,...]] [--metadata-from-file=[KEY=VALUE,...]]
         [--network=NETWORK; default="default"] [--preemptible] [--range=RANGE]
         [--reserved] [--scopes=[SCOPES,...]]
         [--service-account=SERVICE_ACCOUNT] [--shielded-secure-boot]
@@ -81,7 +81,7 @@ OPTIONAL FLAGS
         Return immediately, without waiting for the operation in progress to
         complete.
 
-     --data-disk=DATA_DISK
+     --data-disk=[mode=MODE],[source=SOURCE]
         Additional data disks for the TPU VM.
 
         This flag must be repeated to provide multiple data disks. For example:
@@ -110,15 +110,15 @@ OPTIONAL FLAGS
         default is that external IP addresses will be associated with the TPU
         workers.
 
-     --labels=[LABELS,...]
+     --labels=[KEY=VALUE,...]
         Resource labels to represent user-provided metadata. See
         https://cloud.google.com/compute/docs/labeling-resources for details.
 
-     --metadata=[METADATA,...]
+     --metadata=[KEY=VALUE,...]
         List of comma-separated metadata key-value pairs for the Cloud TPU VM
         node. Example: --metadata='key1=value1,key2=value2'
 
-     --metadata-from-file=[METADATA_FROM_FILE,...]
+     --metadata-from-file=[KEY=VALUE,...]
         Same as --metadata except the value for the entry will be read from a
         local file. Example: --metadata-from-file='key1=value1.txt'