gcloud beta eventarc message-buses update

NAME
gcloud beta eventarc message-buses update - update an Eventarc message bus
SYNOPSIS
gcloud beta eventarc message-buses update (MESSAGE_BUS : --location=LOCATION) [--async] [--logging-config=LOGGING_CONFIG] [--update-labels=[KEY=VALUE,…]] [--clear-crypto-key     | --crypto-key=CRYPTO_KEY] [--clear-labels     | --remove-labels=[KEY,…]] [GCLOUD_WIDE_FLAG …]
DESCRIPTION
(BETA) Update an Eventarc message bus.
EXAMPLES
To update the message bus my-message-bus in location us-central1, run: 
gcloud beta eventarc message-buses update my-message-bus --location=us-central1

To configure the message bus my-message-bus in location us-central1 with a Cloud KMS CryptoKey, run: 

gcloud beta eventarc message-buses update my-message-bus --location=us-central1 --crypto-key=projects/PROJECT_ID/locations/KMS_LOCATION/keyRings/KEYRING/cryptoKeys/KEY
POSITIONAL ARGUMENTS
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 project attribute:

  • provide the argument message_bus on the command line with a fully specified name;
  • provide the argument --project on the command line;
  • set the property core/project.

This must be specified.

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

To set the message-bus attribute:

  • provide the argument message_bus on the command line.

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

--location=LOCATION
The location for the Eventarc message bus, which should be one of the supported regions. Alternatively, set the [eventarc/location] property.

To set the location attribute:

  • provide the argument message_bus on the command line with a fully specified name;
  • provide the argument --location on the command line;
  • set the property eventarc/location.
FLAGS
--async
Return immediately, without waiting for the operation in progress to complete.
--logging-config=LOGGING_CONFIG
The logging config of the message bus. LOGGING_CONFIG must be one of: NONE, DEBUG, INFO, NOTICE, WARNING, ERROR, CRITICAL, ALERT, EMERGENCY.
--update-labels=[KEY=VALUE,…]
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 (-), underscores (_), lowercase characters, and numbers. Values must contain only hyphens (-), underscores (_), lowercase characters, and numbers.

At most one of these can be specified:
--clear-crypto-key
Remove the previously configured crypto key. The channel will continue to be encrypted using Google-managed keys.
--crypto-key=CRYPTO_KEY
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.
At most one of these can be specified:
--clear-labels
Remove all labels. If --update-labels is also specified then --clear-labels is applied first.

For example, to remove all labels: 

gcloud beta eventarc message-buses update --clear-labels

To remove all existing labels and create two new labels, foo and baz: 

gcloud beta eventarc message-buses update --clear-labels --update-labels foo=bar,baz=qux
--remove-labels=[KEY,…]
List of label keys to remove. If a label does not exist it is silently ignored. If --update-labels is also specified then --update-labels is applied first.
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 $ gcloud help for details.

NOTES
This command is currently in beta and might change without notice.