gcloud: Thu Sep 8 09:21:50 UTC 2022

gcloud/beta/compute/firewall-rules/help

@@ -34,6 +34,10 @@ COMMANDS
      list
         (BETA) List Compute Engine firewall rules.
 
+     migrate
+        (BETA) Create a new Network Firewall Policy and move all customer
+        defined firewall rules there.
+
      update
         (BETA) Update a firewall rule.
 

gcloud/beta/compute/firewall-rules/migrate

@@ -0,0 +1,57 @@
+NAME
+    gcloud beta compute firewall-rules migrate - create a new Network Firewall
+        Policy and move all customer defined firewall rules there
+
+SYNOPSIS
+    gcloud beta compute firewall-rules migrate --source-network=SOURCE_NETWORK
+        (--export-tag-mapping
+          | --target-firewall-policy=TARGET_FIREWALL_POLICY)
+        [--tag-mapping-file=TAG_MAPPING_FILE] [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (BETA) gcloud beta compute firewall-rules migrate is used to create a new
+    Network Firewall Policy that contain all rules defined in already existing
+    Network Firewall Policy associated with the given VPC Network and all
+    customer defined VPC Firewall Rules attached to that VPC Network.
+
+EXAMPLES
+    To execute the migration for VPC Network 'my-network' which stores the
+    result in 'my-policy' Network Firewall Policy, run:
+
+        $ gcloud beta compute firewall-rules migrate \
+            --source-network=my-network --target-firewall-policy=my-policy
+
+REQUIRED FLAGS
+     --source-network=SOURCE_NETWORK
+        The VPC Network for which the migration should be performed.
+
+     Exactly one of these must be specified:
+
+       --export-tag-mapping
+          If set, migration tool will inspect all VPC Firewalls attached to
+          SOURCE_NETWORK, collect all source and target tags, and store them in
+          TAG_MAPPING_FILE.
+
+       --target-firewall-policy=TARGET_FIREWALL_POLICY
+          Name of the new Network Firewall Policy used to store the migration
+          result.
+
+OPTIONAL FLAGS
+     --tag-mapping-file=TAG_MAPPING_FILE
+        Path to a JSON file with legacy tags and service accounts to secure
+        tags mapping.
+
+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 firewall-rules migrate
+

gcloud/beta/compute/security-policies/update

@@ -5,6 +5,7 @@ NAME
 SYNOPSIS
     gcloud beta compute security-policies update NAME
         [--description=DESCRIPTION] [--enable-layer7-ddos-defense]
+        [--json-custom-content-types=[CONTENT_TYPE,...]]
         [--json-parsing=JSON_PARSING]
         [--layer7-ddos-defense-auto-deploy-confidence-threshold=LAYER7_DDOS_DEFENSE_AUTO_DEPLOY_CONFIDENCE_THRESHOLD]
         [--layer7-ddos-defense-auto-deploy-expiration-sec=LAYER7_DDOS_DEFENSE_AUTO_DEPLOY_EXPIRATION_SEC]
@@ -37,6 +38,13 @@ FLAGS
      --enable-layer7-ddos-defense
         Whether to enable Cloud Armor Layer 7 DDoS Defense Adaptive Protection.
 
+     --json-custom-content-types=[CONTENT_TYPE,...]
+        A comma-separated list of custom Content-Type header values to apply
+        JSON parsing for preconfigured WAF rules. Only applicable when JSON
+        parsing is enabled, like --json-parsing=STANDARD. When configuring a
+        Content-Type header value, only the type/subtype needs to be specified,
+        and the parameters should be excluded.
+
      --json-parsing=JSON_PARSING
         The JSON parsing behavior for this rule. Must be one of the following
         values: [DISABLED, STANDARD]. JSON_PARSING must be one of: DISABLED,

gcloud/beta/compute/snapshots/create

@@ -5,8 +5,8 @@ SYNOPSIS
     gcloud beta compute snapshots create NAME [--async]
         [--chain-name=CHAIN_NAME] [--csek-key-file=FILE]
         [--description=DESCRIPTION] [--guest-flush] [--labels=[KEY=VALUE,...]]
-        [--source-disk=SOURCE_DISK] [--source-disk-key-file=FILE]
-        [--storage-location=LOCATION]
+        [--snapshot-type=SNAPSHOT_TYPE] [--source-disk=SOURCE_DISK]
+        [--source-disk-key-file=FILE] [--storage-location=LOCATION]
         [--source-disk-region=SOURCE_DISK_REGION
           | --source-disk-zone=SOURCE_DISK_ZONE] [GCLOUD_WIDE_FLAG ...]
 
@@ -65,6 +65,11 @@ FLAGS
         contain only hyphens (-), underscores (_), lowercase characters, and
         numbers.
 
+     --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,
+        STANDARD.
+
      --source-disk=SOURCE_DISK
         Source disk used to create the snapshot. To create a snapshot from a
         source disk in a different project, specify the full path to the source