HEX
Server: Apache/2.4.65 (Ubuntu)
System: Linux ielts-store-v2 6.8.0-1036-gcp #38~22.04.1-Ubuntu SMP Thu Aug 14 01:19:18 UTC 2025 x86_64
User: root (0)
PHP: 7.2.34-54+ubuntu20.04.1+deb.sury.org+1
Disabled: pcntl_alarm,pcntl_fork,pcntl_waitpid,pcntl_wait,pcntl_wifexited,pcntl_wifstopped,pcntl_wifsignaled,pcntl_wifcontinued,pcntl_wexitstatus,pcntl_wtermsig,pcntl_wstopsig,pcntl_signal,pcntl_signal_get_handler,pcntl_signal_dispatch,pcntl_get_last_error,pcntl_strerror,pcntl_sigprocmask,pcntl_sigwaitinfo,pcntl_sigtimedwait,pcntl_exec,pcntl_getpriority,pcntl_setpriority,pcntl_async_signals,
Upload Files
File: //snap/google-cloud-cli/396/help/man/man1/gcloud_beta_eventarc_message-buses_update.1
.TH "GCLOUD_BETA_EVENTARC_MESSAGE\-BUSES_UPDATE" 1



.SH "NAME"
.HP
gcloud beta eventarc message\-buses update \- update an Eventarc message bus



.SH "SYNOPSIS"
.HP
\f5gcloud beta eventarc message\-buses update\fR (\fIMESSAGE_BUS\fR\ :\ \fB\-\-location\fR=\fILOCATION\fR) [\fB\-\-async\fR] [\fB\-\-logging\-config\fR=\fILOGGING_CONFIG\fR] [\fB\-\-update\-labels\fR=[\fIKEY\fR=\fIVALUE\fR,...]] [\fB\-\-clear\-crypto\-key\fR\ |\ \fB\-\-crypto\-key\fR=\fICRYPTO_KEY\fR] [\fB\-\-clear\-labels\fR\ |\ \fB\-\-remove\-labels\fR=[\fIKEY\fR,...]] [\fIGCLOUD_WIDE_FLAG\ ...\fR]



.SH "DESCRIPTION"

\fB(BETA)\fR Update an Eventarc message bus.



.SH "EXAMPLES"

To update the message bus \f5my\-message\-bus\fR in location \f5us\-central1\fR,
run:

.RS 2m
$ gcloud beta eventarc message\-buses update my\-message\-bus \e
    \-\-location=us\-central1
.RE

To configure the message bus \f5my\-message\-bus\fR in location
\f5us\-central1\fR with a Cloud KMS CryptoKey, run:

.RS 2m
$ gcloud beta eventarc message\-buses update my\-message\-bus \e
    \-\-location=us\-central1 \e
    \-\-crypto\-key=projects/PROJECT_ID/locations/KMS_LOCATION/\e
keyRings/KEYRING/cryptoKeys/KEY
.RE



.SH "POSITIONAL ARGUMENTS"

.RS 2m
.TP 2m

Message bus resource \- Message bus 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 \f5message_bus\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
\fIMESSAGE_BUS\fR

ID of the message bus or fully qualified identifier for the message bus.

To set the \f5message\-bus\fR attribute:
.RS 2m
.IP "\(bu" 2m
provide the argument \f5message_bus\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 for the Eventarc message bus, which should be one of the supported
regions. Alternatively, set the [eventarc/location] property.

To set the \f5location\fR attribute:
.RS 2m
.IP "\(bu" 2m
provide the argument \f5message_bus\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
set the property \f5eventarc/location\fR.
.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\-\-logging\-config\fR=\fILOGGING_CONFIG\fR

The logging config of the message bus. \fILOGGING_CONFIG\fR must be one of:
\fBNONE\fR, \fBDEBUG\fR, \fBINFO\fR, \fBNOTICE\fR, \fBWARNING\fR, \fBERROR\fR,
\fBCRITICAL\fR, \fBALERT\fR, \fBEMERGENCY\fR.

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

List of label KEY=VALUE pairs to update. If a label exists, its value is
modified. Otherwise, a new label is created.

Keys must start with a lowercase character and contain only hyphens (\f5\-\fR),
underscores (\f5_\fR), lowercase characters, and numbers. Values must contain
only hyphens (\f5\-\fR), underscores (\f5_\fR), lowercase characters, and
numbers.

.TP 2m

At most one of these can be specified:


.RS 2m
.TP 2m
\fB\-\-clear\-crypto\-key\fR

Remove the previously configured crypto key. The channel will continue to be
encrypted using Google\-managed keys.

.TP 2m
\fB\-\-crypto\-key\fR=\fICRYPTO_KEY\fR

Fully qualified name of the crypto key to use for customer\-managed encryption.
If this is unspecified, Google\-managed keys will be used for encryption.

.RE
.sp
.TP 2m

At most one of these can be specified:


.RS 2m
.TP 2m
\fB\-\-clear\-labels\fR

Remove all labels. If \f5\-\-update\-labels\fR is also specified then
\f5\-\-clear\-labels\fR is applied first.

For example, to remove all labels:

.RS 2m
$ gcloud beta eventarc message\-buses update \-\-clear\-labels
.RE

To remove all existing labels and create two new labels, \f5\fIfoo\fR\fR and
\f5\fIbaz\fR\fR:

.RS 2m
$ gcloud beta eventarc message\-buses update \-\-clear\-labels \e
  \-\-update\-labels foo=bar,baz=qux
.RE

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

List of label keys to remove. If a label does not exist it is silently ignored.
If \f5\-\-update\-labels\fR is also specified then \f5\-\-update\-labels\fR is
applied first.


.RE
.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 beta and might change without notice. This variant
is also available:

.RS 2m
$ gcloud eventarc message\-buses update
.RE