File: //snap/google-cloud-cli/current/help/man/man1/gcloud_alpha_artifacts_vpcsc-config.1
.TH "GCLOUD_ALPHA_ARTIFACTS_VPCSC\-CONFIG" 1
.SH "NAME"
.HP
gcloud alpha artifacts vpcsc\-config \- manage Artifact Registry VPC Service Controls configuration for remote repositories
.SH "SYNOPSIS"
.HP
\f5gcloud alpha artifacts vpcsc\-config\fR \fICOMMAND\fR [\fIGCLOUD_WIDE_FLAG\ ...\fR]
.SH "DESCRIPTION"
\fB(ALPHA)\fR Manage Artifact Registry VPC Service Controls configuration for
remote repositories.
.SH "GCLOUD WIDE FLAGS"
These flags are available to all commands: \-\-help.
Run \fB$ gcloud help\fR for details.
.SH "COMMANDS"
\f5\fICOMMAND\fR\fR is one of the following:
.RS 2m
.TP 2m
\fBallow\fR
\fB(ALPHA)\fR Allow Artifact Registry remote repositories inside a service
perimeter to retrieve data from their upstream sources outside of the perimeter.
.TP 2m
\fBdeny\fR
\fB(ALPHA)\fR Deny access to upstream sources outside the service perimeter for
Artifact Registry remote repositories inside the perimeter.
.TP 2m
\fBdescribe\fR
\fB(ALPHA)\fR Describe the current Artifact Registry configuration for VPC
Service Controls.
.RE
.sp
.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 artifacts vpcsc\-config
.RE
.RS 2m
$ gcloud beta artifacts vpcsc\-config
.RE