.TH "GCLOUD_ALPHA_COMPUTE_NETWORKS_PEERINGS_UPDATE" 1



.SH "NAME"
.HP
gcloud alpha compute networks peerings update \- update a Compute Engine network peering



.SH "SYNOPSIS"
.HP
\f5gcloud alpha compute networks peerings update\fR \fINAME\fR \fB\-\-network\fR=\fINETWORK\fR [\fB\-\-export\-custom\-routes\fR] [\fB\-\-export\-subnet\-routes\-with\-public\-ip\fR] [\fB\-\-import\-custom\-routes\fR] [\fB\-\-import\-subnet\-routes\-with\-public\-ip\fR] [\fB\-\-stack\-type\fR=\fISTACK_TYPE\fR] [\fB\-\-update\-strategy\fR=\fIUPDATE_STRATEGY\fR] [\fIGCLOUD_WIDE_FLAG\ ...\fR]



.SH "EXAMPLES"

To update the peering named peering\-name to both export and import custom
routes, run:

.RS 2m
$ gcloud alpha compute networks peerings update peering\-name \e
    \-\-export\-custom\-routes \-\-import\-custom\-routes
.RE


To update the peering named peering\-name to both export and import subnet
routes with public ip, run:

.RS 2m
$ gcloud alpha compute networks peerings update peering\-name \e
    \-\-export\-subnet\-routes\-with\-public\-ip \e
    \-\-import\-subnet\-routes\-with\-public\-ip
.RE



.SH "POSITIONAL ARGUMENTS"

.RS 2m
.TP 2m
\fINAME\fR

The name of the peering.


.RE
.sp

.SH "REQUIRED FLAGS"

.RS 2m
.TP 2m
\fB\-\-network\fR=\fINETWORK\fR

The name of the network in the current project to be peered with the peer
network.


.RE
.sp

.SH "OPTIONAL FLAGS"

.RS 2m
.TP 2m
\fB\-\-export\-custom\-routes\fR

If set, the network will export custom routes to peer network. Use
\-\-no\-export\-custom\-routes to disable it.

.TP 2m
\fB\-\-export\-subnet\-routes\-with\-public\-ip\fR

If set, the network will export subnet routes with addresses in the public IP
ranges to peer network. Use \-\-no\-export\-subnet\-routes\-with\-public\-ip to
disable it.

.TP 2m
\fB\-\-import\-custom\-routes\fR

If set, the network will import custom routes from peer network. Use
\-\-no\-import\-custom\-routes to disable it.

.TP 2m
\fB\-\-import\-subnet\-routes\-with\-public\-ip\fR

If set, the network will import subnet routes with addresses in the public IP
ranges from peer network. Use \-\-no\-import\-subnet\-routes\-with\-public\-ip
to disable it.

.TP 2m
\fB\-\-stack\-type\fR=\fISTACK_TYPE\fR

Stack type of the peering. If not specified, defaults to IPV4_ONLY.

STACK_TYPE must be one of:

.RS 2m
IPV4_ONLY
   Only IPv4 traffic and routes will be exchanged across this peering.
.RE

.RS 2m
IPV4_IPV6
   IPv4 traffic and routes will be exchanged across this peering.
   IPv6 traffic and routes will be exchanged if the matching peering
   configuration also has stack_type set to IPV4_IPV6.
.RE

.TP 2m
\fB\-\-update\-strategy\fR=\fIUPDATE_STRATEGY\fR

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.


.RE
.sp

.SH "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 \fB$ gcloud help\fR for details.



.SH "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. These variants are also available:

.RS 2m
$ gcloud compute networks peerings update
.RE

.RS 2m
$ gcloud beta compute networks peerings update
.RE