.TH "GCLOUD_ALPHA_KMS_AUTOKEY\-CONFIG_DESCRIBE" 1



.SH "NAME"
.HP
gcloud alpha kms autokey\-config describe \- describe the AutokeyConfig of a folder



.SH "SYNOPSIS"
.HP
\f5gcloud alpha kms autokey\-config describe\fR \fB\-\-folder\fR=\fIFOLDER\fR [\fIGCLOUD_WIDE_FLAG\ ...\fR]



.SH "DESCRIPTION"

\fB(ALPHA)\fR gcloud alpha kms autokey\-config describe can be used to retrieve
the AutokeyConfig of a folder.



.SH "EXAMPLES"

The following command retrieves the AutokeyConfig of a folder having folder\-id
\f5123\fR:

.RS 2m
$ gcloud alpha kms autokey\-config describe \-\-folder=123
.RE



.SH "REQUIRED FLAGS"

.RS 2m
.TP 2m
\fB\-\-folder\fR=\fIFOLDER\fR

The folder id in which the AutokeyConfig resource exists.


.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 kms autokey\-config describe
.RE

.RS 2m
$ gcloud beta kms autokey\-config describe
.RE