.TH "GCLOUD_EDGE\-CACHE_KEYSETS_UPDATE" 1



.SH "NAME"
.HP
gcloud edge\-cache keysets update \- update an EdgeCacheKeyset resource



.SH "SYNOPSIS"
.HP
\f5gcloud edge\-cache keysets update\fR (\fIKEYSET\fR\ :\ \fB\-\-location\fR=\fILOCATION\fR) [\fB\-\-async\fR] [\fB\-\-description\fR=\fIDESCRIPTION\fR] [\fB\-\-labels\fR=[\fIKEY\fR=\fIVALUE\fR,...]] [\fB\-\-public\-key\fR=[\fIid\fR=\fIID\fR],[\fImanaged\fR=\fIMANAGED\fR],[\fIvalue\fR=\fIVALUE\fR]] [\fB\-\-validation\-shared\-key\fR=[\fIsecret_version\fR=\fISECRET_VERSION\fR]] [\fIGCLOUD_WIDE_FLAG\ ...\fR]



.SH "DESCRIPTION"

Update an existing EdgeCacheKeyset resource.



.SH "EXAMPLES"

To update an EdgeCacheKeyset resource called 'my\-keyset', run:

.RS 2m
$ gcloud edge\-cache keysets update my\-keyset \e
    \-\-public\-key='id=KEYID,value=BASE64PUBLICKEY'
.RE

The \f5update\fR command appends keys to an existing EdgeCacheKeyset resource.
To add more than one key to an EdgeCacheKeyset resource, provide multiple
\f5\-\-public\-key\fR values:

.RS 2m
$ gcloud edge\-cache keysets update my\-keyset \e
    \-\-public\-key='id=KEYID,value=BASE64PUBLICKEY' \e
    \-\-public\-key='id=EXISTING,value=EXISTINGPUBLICKEY'
.RE

You can specify, and an EdgeCacheKeyset resource can contain, up to three (3)
public keys. To delete unused public keys within an existing Keyset, use the
\f5import\fR command to specify the EdgeCacheKeyset resource in full, omitting
any unused publicKey items.



.SH "POSITIONAL ARGUMENTS"

.RS 2m
.TP 2m

Keyset resource \- The name of the EdgeCacheKeyset resource to update. The
arguments in this group can be used to specify the attributes of this resource.
(NOTE) Some attributes are not given arguments in this group but can be set in
other ways.

To set the \f5project\fR attribute:
.RS 2m
.IP "\(em" 2m
provide the argument \f5keyset\fR on the command line with a fully specified
name;
.IP "\(em" 2m
provide the argument \f5\-\-project\fR on the command line;
.IP "\(em" 2m
set the property \f5core/project\fR.
.RE
.sp

This must be specified.


.RS 2m
.TP 2m
\fIKEYSET\fR

ID of the keyset or fully qualified identifier for the keyset.

To set the \f5keyset\fR attribute:
.RS 2m
.IP "\(bu" 2m
provide the argument \f5keyset\fR on the command line.
.RE
.sp

This positional argument must be specified if any of the other arguments in this
group are specified.

.TP 2m
\fB\-\-location\fR=\fILOCATION\fR

The location Id.


To set the \f5location\fR attribute:
.RS 2m
.IP "\(bu" 2m
provide the argument \f5keyset\fR on the command line with a fully specified
name;
.IP "\(bu" 2m
provide the argument \f5\-\-location\fR on the command line;
.IP "\(bu" 2m
use global location.
.RE
.sp


.RE
.RE
.sp

.SH "FLAGS"

.RS 2m
.TP 2m
\fB\-\-async\fR

Return immediately, without waiting for the operation in progress to complete.

.TP 2m
\fB\-\-description\fR=\fIDESCRIPTION\fR

Human\-readable description of the resource.

.TP 2m
\fB\-\-labels\fR=[\fIKEY\fR=\fIVALUE\fR,...]

List of KEY=VALUE labels to attach to this resource.

.TP 2m
\fB\-\-public\-key\fR=[\fIid\fR=\fIID\fR],[\fImanaged\fR=\fIMANAGED\fR],[\fIvalue\fR=\fIVALUE\fR]

Set of public keys to use for validating signed requests, when associated with a
route. This flag can be repeated to create a Keyset with multiple public keys.

If you are providing your own public keys, specify the key in the form
\f5id=ID,value=BASE64ENCODEDPUBLICKEY\fR.

If you are using Google\-managed public keys as part of a dual\-token setup,
specify the key in the form \f5id=ID,managed=true\fR.

.RS 2m
.TP 2m
\fBid\fR
id (name) name of the key within the keyset.

.TP 2m
\fBvalue\fR
URL\-safe base64 encoded public key. Cannot be specified if \f5managed=true\fR.

.TP 2m
\fBmanaged\fR
Boolean indicating this is a Google\-managed key. Cannot be specified if
\f5value=true\fR.

.RE
.sp
To create a public key with \f5id\fR 'foo', pass
\f5\-\-public\-key='id=foo,value=VALUE'\fR to gcloud edge\-cache keysets update.

To create a Google\-managed public key with \f5id\fR 'bar', pass
\f5\-\-public\-key='id=foo,managed=true'\fR to gcloud edge\-cache keysets
update.

At least one of public\-key or validation\-shared\-key must be specified.

.TP 2m
\fB\-\-validation\-shared\-key\fR=[\fIsecret_version\fR=\fISECRET_VERSION\fR]

An ordered list of shared keys to use for validating signed requests.

To create a validation shared key pointing to a Secret Manager secret version
with name \f5projects/PROJECT/secrets/SECRET/versions/VERSION\fR, pass
\f5\-\-validation\-shared\-key='secret_version=projects/PROJECT/secrets/SECRET/versions/VERSION'\fR
to gcloud edge\-cache keysets update.

.RS 2m
.TP 2m
\fBsecret_version\fR
The name of the secret in Secret Manager. Must be in the format
\f5projects/PROJECT/secrets/SECRET/versions/VERSION\fR.

.RE
.sp
At least one of public\-key or validation\-shared\-key must be specified.


.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 "API REFERENCE"

This command uses the \fBnetworkservices/v1\fR API. The full documentation for
this API can be found at: https://cloud.google.com/networking



.SH "NOTES"

This variant is also available:

.RS 2m
$ gcloud alpha edge\-cache keysets update
.RE