gcloud eventarc channels update - update an Eventarc channel
gcloud eventarc channels update (CHANNEL : --location=LOCATION) [--async] [--clear-crypto-key | --crypto-key=CRYPTO_KEY] [GCLOUD_WIDE_FLAG ...]
Update an Eventarc channel.
To update the channel my-channel in location us-central1, run:
$ gcloud eventarc channels update my-channel --location=us-central1
To configure the channel my-channel in location us-central1 with a Cloud KMS CryptoKey, run:
$ gcloud eventarc channels update my-channel \ --location=us-central1 \ --crypto-key=projects/PROJECT_ID/locations/KMS_LOCATION/\ keyRings/KEYRING/cryptoKeys/KEY
- Channel resource - Channel 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 channel 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.
- CHANNEL
ID of the channel or fully qualified identifier for the channel. To set the channel attribute:
provide the argument channel 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 channel, which should be either global or one of the supported regions. Alternatively, set the [eventarc/location] property. To set the location attribute:
provide the argument channel on the command line with a fully specified name;
provide the argument --location on the command line;
set the property eventarc/location.
- --async
Return immediately, without waiting for the operation in progress to complete.
- 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.
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.