gcloud: Wed Aug 27 10:57:46 UTC 2025

gcloud/compute/networks/peerings/create

@@ -8,7 +8,7 @@ SYNOPSIS
         [--export-custom-routes] [--export-subnet-routes-with-public-ip]
         [--import-custom-routes] [--import-subnet-routes-with-public-ip]
         [--peer-project=PEER_PROJECT] [--stack-type=STACK_TYPE]
-        [GCLOUD_WIDE_FLAG ...]
+        [--update-strategy=UPDATE_STRATEGY] [GCLOUD_WIDE_FLAG ...]
 
 DESCRIPTION
     gcloud compute networks peerings create is used to create peerings between
@@ -87,6 +87,18 @@ OPTIONAL FLAGS
                IPv6 traffic and routes will be exchanged if the matching peering
                configuration also has stack_type set to IPV4_IPV6.
 
+     --update-strategy=UPDATE_STRATEGY
+        Update strategy of the peering. If not specified, defaults to
+        INDEPENDENT.
+
+        UPDATE_STRATEGY must be one of:
+
+        INDEPENDENT Updates and deletes to the peering connection can be
+        performed by either network admin.
+
+        CONSENSUS Updates and deletes to the peering connection must be agreed
+        upon by both network admins.
+
 GCLOUD WIDE FLAGS
     These flags are available to all commands: --access-token-file, --account,
     --billing-project, --configuration, --flags-file, --flatten, --format,

gcloud/compute/networks/peerings/help

@@ -34,6 +34,9 @@ COMMANDS
      list-routes
         List received or advertised routes for a VPC network peering.
 
+     request-delete
+        Request deletion of a Compute Engine network peering.
+
      update
         Update a Compute Engine network peering.
 

gcloud/compute/networks/peerings/request-delete

@@ -0,0 +1,54 @@
+NAME
+    gcloud compute networks peerings request-delete - request deletion of a
+        Compute Engine network peering
+
+SYNOPSIS
+    gcloud compute networks peerings request-delete NAME --network=NETWORK
+        [--async] [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    gcloud compute networks peerings request-delete is used to request deletion
+    of a consensus peering between virtual networks. The peering can be deleted
+    if both sides request deletion.
+
+EXAMPLES
+    To request deletion of a consensus peering with the name 'peering-name'
+    between the network 'local-network' and the network 'peer-network', run:
+
+        $ gcloud compute networks peerings request-delete peering-name \
+          --network=local-network
+
+        $ gcloud compute networks peerings request-delete peering-name \
+          --network=peer-network
+
+    To complete the deletion, run gcloud compute networks peerings delete for
+    each side of the peering.
+
+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
+    These variants are also available:
+
+        $ gcloud alpha compute networks peerings request-delete
+
+        $ gcloud beta compute networks peerings request-delete
+

gcloud/compute/networks/peerings/update

@@ -6,7 +6,8 @@ SYNOPSIS
     gcloud compute networks peerings update NAME --network=NETWORK
         [--export-custom-routes] [--export-subnet-routes-with-public-ip]
         [--import-custom-routes] [--import-subnet-routes-with-public-ip]
-        [--stack-type=STACK_TYPE] [GCLOUD_WIDE_FLAG ...]
+        [--stack-type=STACK_TYPE] [--update-strategy=UPDATE_STRATEGY]
+        [GCLOUD_WIDE_FLAG ...]
 
 EXAMPLES
     To update the peering named peering-name to both export and import custom
@@ -63,6 +64,18 @@ OPTIONAL FLAGS
                IPv6 traffic and routes will be exchanged if the matching peering
                configuration also has stack_type set to IPV4_IPV6.
 
+     --update-strategy=UPDATE_STRATEGY
+        Update strategy of the peering. If not specified, defaults to
+        INDEPENDENT.
+
+        UPDATE_STRATEGY must be one of:
+
+        INDEPENDENT Updates and deletes to the peering connection can be
+        performed by either network admin.
+
+        CONSENSUS Updates and deletes to the peering connection must be agreed
+        upon by both network admins.
+
 GCLOUD WIDE FLAGS
     These flags are available to all commands: --access-token-file, --account,
     --billing-project, --configuration, --flags-file, --flatten, --format,