.TH "GCLOUD_COMPUTE_NETWORK\-ATTACHMENTS_UPDATE" 1



.SH "NAME"
.HP
gcloud compute network\-attachments update \- update a Google Compute Engine network attachment



.SH "SYNOPSIS"
.HP
\f5gcloud compute network\-attachments update\fR \fINAME\fR [\fB\-\-description\fR=\fIDESCRIPTION\fR] [\fB\-\-producer\-accept\-list\fR=[\fIACCEPT_LIST\fR,...]] [\fB\-\-producer\-reject\-list\fR=[\fIREJECT_LIST\fR,...]] [\fB\-\-region\fR=\fIREGION\fR] [\fB\-\-subnets\fR=\fISUBNETS\fR,[\fISUBNETS\fR,...]] [\fB\-\-subnets\-region\fR=\fISUBNETS_REGION\fR] [\fIGCLOUD_WIDE_FLAG\ ...\fR]



.SH "DESCRIPTION"

\fBgcloud compute network\-attachments update\fR is used to update network
attachments. You can update the following fields: description, subnets,
producer\-accept\-list and producer\-reject\-list. If you update the
producer\-accept\-list or producer\-reject\-list, the full new list should be
specified.



.SH "EXAMPLES"

To update all the parameters with the new list, run:

.RS 2m
$ gcloud compute network\-attachments update \e
    NETWORK_ATTACHMENT_NAME \-\-region=us\-central1 \e
    \-\-subnets=MY_SUBNET2 \e
    \-\-description='default network attachment' \e
    \-\-producer\-accept\-list=PROJECT5,PROJECT6 \e
    \-\-producer\-reject\-list=PROJECT7,PROJECT8
.RE

To update a network attachment to change only the subnet to MY_SUBNET3, run:

.RS 2m
$ gcloud compute network\-attachments update \e
    NETWORK_ATTACHMENT_NAME \-\-region=us\-central1 \e
    \-\-subnets=MY_SUBNET3
.RE



.SH "POSITIONAL ARGUMENTS"

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

Name of the network attachment to update.


.RE
.sp

.SH "FLAGS"

.RS 2m
.TP 2m
\fB\-\-description\fR=\fIDESCRIPTION\fR

An optional, textual description for the network attachment.

.TP 2m
\fB\-\-producer\-accept\-list\fR=[\fIACCEPT_LIST\fR,...]

Projects that are allowed to connect to this network attachment.

.TP 2m
\fB\-\-producer\-reject\-list\fR=[\fIREJECT_LIST\fR,...]

Projects that are not allowed to connect to this network attachment.

.TP 2m
\fB\-\-region\fR=\fIREGION\fR

Region of the network attachment to update. 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
\f5\fIcompute/region\fR\fR property:

.RS 2m
$ gcloud config set compute/region REGION
.RE

A list of regions can be fetched by running:

.RS 2m
$ gcloud compute regions list
.RE

To unset the property, run:

.RS 2m
$ gcloud config unset compute/region
.RE

Alternatively, the region can be stored in the environment variable
\f5\fICLOUDSDK_COMPUTE_REGION\fR\fR.

.TP 2m
\fB\-\-subnets\fR=\fISUBNETS\fR,[\fISUBNETS\fR,...]

The subnetworks provided by the consumer for the producers

.TP 2m
\fB\-\-subnets\-region\fR=\fISUBNETS_REGION\fR

Region of the subnetworks to operate on. Overrides the default
\fBcompute/region\fR property value for this command invocation.


.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"

These variants are also available:

.RS 2m
$ gcloud alpha compute network\-attachments update
.RE

.RS 2m
$ gcloud beta compute network\-attachments update
.RE