.TH "GCLOUD_ALPHA_COMPUTE_SHARED\-VPC_ENABLE" 1



.SH "NAME"
.HP
gcloud alpha compute shared\-vpc enable \- enable the given project as a shared VPC host



.SH "SYNOPSIS"
.HP
\f5gcloud alpha compute shared\-vpc enable\fR \fIPROJECT_ID\fR [\fIGCLOUD_WIDE_FLAG\ ...\fR]



.SH "DESCRIPTION"

\fB(ALPHA)\fR That is, after running this command, one \fBcan\fR enable another
project to use the VPC networks shared by this project.



.SH "EXAMPLES"

To enable the project \f5myproject\fR as a shared VPC host, run:

.RS 2m
$ gcloud alpha compute shared\-vpc enable myproject
.RE



.SH "POSITIONAL ARGUMENTS"

.RS 2m
.TP 2m
\fIPROJECT_ID\fR

ID for the project to enable as a shared VPC host


.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 shared\-vpc enable
.RE

.RS 2m
$ gcloud beta compute shared\-vpc enable
.RE