gcloud beta eventarc message-buses create

NAME
gcloud beta eventarc message-buses create - create an Eventarc message bus
SYNOPSIS
gcloud beta eventarc message-buses create (MESSAGE_BUS : --location=LOCATION) [--async] [--crypto-key=CRYPTO_KEY] [--labels=[KEY=VALUE,…]] [--logging-config=LOGGING_CONFIG] [GCLOUD_WIDE_FLAG …]
DESCRIPTION
(BETA) Create an Eventarc message bus.
EXAMPLES
To create a new message bus my-message-bus in location us-central1, run: 
gcloud beta eventarc message-buses create my-message-bus --location=us-central1
POSITIONAL ARGUMENTS
Message bus resource - The message bus to create. 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.
--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.
--labels=[KEY=VALUE,…]
Labels to apply to the message bus.
--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.
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.