.TH "GCLOUD_ALPHA_KMS_AUTOKEY\-CONFIG_UPDATE" 1



.SH "NAME"
.HP
gcloud alpha kms autokey\-config update \- updates the AutokeyConfig for a folder



.SH "SYNOPSIS"
.HP
\f5gcloud alpha kms autokey\-config update\fR \fICONFIG_FILE\fR [\fIGCLOUD_WIDE_FLAG\ ...\fR]



.SH "DESCRIPTION"

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



.SH "EXAMPLES"

The following command updates the AutokeyConfig for the folder mentioned in the
config.yaml file:

.RS 2m
$ gcloud alpha kms autokey\-config update config.yaml
.RE



.SH "POSITIONAL ARGUMENTS"

.RS 2m
.TP 2m
\fICONFIG_FILE\fR

The file containing the AutokeyConfig resource.


.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 update
.RE

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