.TH "GCLOUD_ALPHA_CONFIG_CONFIGURATIONS_ACTIVATE" 1



.SH "NAME"
.HP
gcloud alpha config configurations activate \- activates an existing named configuration



.SH "SYNOPSIS"
.HP
\f5gcloud alpha config configurations activate\fR \fICONFIGURATION_NAME\fR [\fIGCLOUD_WIDE_FLAG\ ...\fR]



.SH "DESCRIPTION"

\fB(ALPHA)\fR Activates an existing named configuration.

See \f5gcloud topic configurations\fR for an overview of named configurations.



.SH "EXAMPLES"

To activate an existing configuration named \f5my\-config\fR, run:

.RS 2m
$ gcloud alpha config configurations activate my\-config
.RE

To list all properties in the activated configuration, run:

.RS 2m
$ gcloud config list \-\-all
.RE



.SH "POSITIONAL ARGUMENTS"

.RS 2m
.TP 2m
\fICONFIGURATION_NAME\fR

Name of the configuration to activate


.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 config configurations activate
.RE

.RS 2m
$ gcloud beta config configurations activate
.RE

.RS 2m
$ gcloud preview config configurations activate
.RE