.TH "GCLOUD_EVENTARC_TRIGGERS_CREATE" 1



.SH "NAME"
.HP
gcloud eventarc triggers create \- create an Eventarc trigger



.SH "SYNOPSIS"
.HP
\f5gcloud eventarc triggers create\fR (\fITRIGGER\fR\ :\ \fB\-\-location\fR=\fILOCATION\fR) \fB\-\-event\-filters\fR=[\fIATTRIBUTE\fR=\fIVALUE\fR,...] ([\fB\-\-destination\-gke\-cluster\fR=\fIDESTINATION_GKE_CLUSTER\fR\ \fB\-\-destination\-gke\-service\fR=\fIDESTINATION_GKE_SERVICE\fR\ :\ \fB\-\-destination\-gke\-location\fR=\fIDESTINATION_GKE_LOCATION\fR\ \fB\-\-destination\-gke\-namespace\fR=\fIDESTINATION_GKE_NAMESPACE\fR\ \fB\-\-destination\-gke\-path\fR=\fIDESTINATION_GKE_PATH\fR]\ |\ [\fB\-\-destination\-http\-endpoint\-uri\fR=\fIDESTINATION_HTTP_ENDPOINT_URI\fR\ :\ \fB\-\-network\-attachment\fR=\fINETWORK_ATTACHMENT\fR]\ |\ [\fB\-\-destination\-run\-service\fR=\fIDESTINATION_RUN_SERVICE\fR\ :\ \fB\-\-destination\-run\-path\fR=\fIDESTINATION_RUN_PATH\fR\ \fB\-\-destination\-run\-region\fR=\fIDESTINATION_RUN_REGION\fR]\ |\ [\fB\-\-destination\-workflow\fR=\fIDESTINATION_WORKFLOW\fR\ :\ \fB\-\-destination\-workflow\-location\fR=\fIDESTINATION_WORKFLOW_LOCATION\fR]) [\fB\-\-async\fR] [\fB\-\-channel\fR=\fICHANNEL\fR] [\fB\-\-event\-data\-content\-type\fR=\fIEVENT_DATA_CONTENT_TYPE\fR] [\fB\-\-event\-filters\-path\-pattern\fR=[\fIATTRIBUTE\fR=\fIPATH_PATTERN\fR,...]] [\fB\-\-labels\fR=[\fIKEY\fR=\fIVALUE\fR,...]] [\fB\-\-service\-account\fR=\fISERVICE_ACCOUNT\fR] [\fB\-\-transport\-topic\fR=\fITRANSPORT_TOPIC\fR] [\fIGCLOUD_WIDE_FLAG\ ...\fR]



.SH "DESCRIPTION"

Create an Eventarc trigger.



.SH "EXAMPLES"

To create a new trigger \f5\fImy\-trigger\fR\fR for events of type
\f5\fIgoogle.cloud.pubsub.topic.v1.messagePublished\fR\fR with destination Cloud
Run service \f5\fImy\-service\fR\fR, run:

.RS 2m
$ gcloud eventarc triggers create my\-trigger \e
     \-\-event\-filters="type=google.cloud.pubsub.topic.v1.messagePublis\e
 hed" \-\-destination\-run\-service=my\-service
.RE



.SH "POSITIONAL ARGUMENTS"

.RS 2m
.TP 2m

Trigger resource \- The trigger 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 \f5project\fR attribute:
.RS 2m
.IP "\(em" 2m
provide the argument \f5trigger\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
\fITRIGGER\fR

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

To set the \f5trigger\fR attribute:
.RS 2m
.IP "\(bu" 2m
provide the argument \f5trigger\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 trigger, which should be either \f5\fIglobal\fR\fR
or 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 \f5trigger\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 "REQUIRED FLAGS"

.RS 2m
.TP 2m
\fB\-\-event\-filters\fR=[\fIATTRIBUTE\fR=\fIVALUE\fR,...]

The trigger's list of filters that apply to CloudEvents attributes. This flag
can be repeated to add more filters to the list. Only events that match all
these filters will be sent to the destination. The filters must include the
\f5\fItype\fR\fR attribute, as well as any other attributes that are expected
for the chosen type.

.TP 2m

Flags for specifying the destination to which events should be sent.

Exactly one of these must be specified:


.RS 2m
.TP 2m

Flags for specifying a GKE service destination.


.RS 2m
.TP 2m
\fB\-\-destination\-gke\-cluster\fR=\fIDESTINATION_GKE_CLUSTER\fR

Name of the GKE cluster that the destination GKE service is running in. The
cluster must be in the same project as the trigger.

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

.TP 2m
\fB\-\-destination\-gke\-service\fR=\fIDESTINATION_GKE_SERVICE\fR

Name of the destination GKE service that receives the events for the trigger.

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

.TP 2m
\fB\-\-destination\-gke\-location\fR=\fIDESTINATION_GKE_LOCATION\fR

Location of the GKE cluster that the destination GKE service is running in. If
not specified, it is assumed that the cluster is a regional cluster and is in
the same region as the trigger.

.TP 2m
\fB\-\-destination\-gke\-namespace\fR=\fIDESTINATION_GKE_NAMESPACE\fR

Namespace that the destination GKE service is running in. If not specified, the
\f5\fIdefault\fR\fR namespace is used.

.TP 2m
\fB\-\-destination\-gke\-path\fR=\fIDESTINATION_GKE_PATH\fR

Relative path on the destination GKE service to which the events for the trigger
should be sent. Examples: \f5\fI/route\fR\fR, \f5\fIroute\fR\fR,
\f5\fIroute/subroute\fR\fR.

.RE
.sp
.TP 2m

Flags for specifying a HTTP Endpoint destination.


.RS 2m
.TP 2m
\fB\-\-destination\-http\-endpoint\-uri\fR=\fIDESTINATION_HTTP_ENDPOINT_URI\fR

URI that the destination HTTP Endpoint is connecting to.

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

.TP 2m

Flags for specifying a Network Config for the destination.


.RS 2m
.TP 2m
\fB\-\-network\-attachment\fR=\fINETWORK_ATTACHMENT\fR

The network attachment associated with the trigger that allows access to the
destination VPC.

.RE
.RE
.sp
.TP 2m

Flags for specifying a Cloud Run fully\-managed resource destination.


.RS 2m
.TP 2m
\fB\-\-destination\-run\-service\fR=\fIDESTINATION_RUN_SERVICE\fR

Name of the Cloud Run fully\-managed service that receives the events for the
trigger. The service must be in the same project as the trigger.

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

.TP 2m
\fB\-\-destination\-run\-path\fR=\fIDESTINATION_RUN_PATH\fR

Relative path on the destination Cloud Run service to which the events for the
trigger should be sent. Examples: \f5\fI/route\fR\fR, \f5\fIroute\fR\fR,
\f5\fIroute/subroute\fR\fR.

.TP 2m
\fB\-\-destination\-run\-region\fR=\fIDESTINATION_RUN_REGION\fR

Region in which the destination Cloud Run service can be found. If not
specified, it is assumed that the service is in the same region as the trigger.

.RE
.sp
.TP 2m

Flags for specifying a Cloud Workflows destination.


.RS 2m
.TP 2m
\fB\-\-destination\-workflow\fR=\fIDESTINATION_WORKFLOW\fR

ID of the workflow that receives the events for the trigger. The workflow must
be in the same project as the trigger.

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

.TP 2m
\fB\-\-destination\-workflow\-location\fR=\fIDESTINATION_WORKFLOW_LOCATION\fR

Location that the destination workflow is running in. If not specified, it is
assumed that the workflow is in the same location as the trigger.


.RE
.RE
.RE
.sp

.SH "OPTIONAL FLAGS"

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

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

.TP 2m

Channel resource \- The channel to use in the trigger. The channel is needed
only if trigger is created for a third\-party provider. This represents a Cloud
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 \f5\-\-channel\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

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


.RS 2m
.TP 2m
\fB\-\-channel\fR=\fICHANNEL\fR

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

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

.RE
.sp
.TP 2m
\fB\-\-event\-data\-content\-type\fR=\fIEVENT_DATA_CONTENT_TYPE\fR

Depending on the event provider, you can specify the encoding of the event data
payload that will be delivered to your destination, to either be encoded in
\f5\fIapplication/json\fR\fR or \f5\fIapplication/protobuf\fR\fR. The default
encoding is \f5\fIapplication/json\fR\fR. Note that for custom sources or
third\-party providers, or for direct events from Cloud Pub/Sub, this formatting
option is not supported.

.TP 2m
\fB\-\-event\-filters\-path\-pattern\fR=[\fIATTRIBUTE\fR=\fIPATH_PATTERN\fR,...]

The trigger's list of filters in path pattern format that apply to CloudEvent
attributes. This flag can be repeated to add more filters to the list. Only
events that match all these filters will be sent to the destination. Currently,
path pattern format is only available for the resourceName attribute for Cloud
Audit Log events.

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

List of label KEY=VALUE pairs to add.

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
\fB\-\-service\-account\fR=\fISERVICE_ACCOUNT\fR

The IAM service account email associated with the trigger.

.TP 2m

Pub/Sub topic resource \- The Cloud Pub/Sub topic to use for the trigger's
transport intermediary. This feature is currently only available for triggers of
event type \f5\fIgoogle.cloud.pubsub.topic.v1.messagePublished\fR\fR. The topic
must be in the same project as the trigger. If not specified, a transport topic
will be created. This represents a Cloud 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 \f5\-\-transport\-topic\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


.RS 2m
.TP 2m
\fB\-\-transport\-topic\fR=\fITRANSPORT_TOPIC\fR

ID of the Pub/Sub topic or fully qualified identifier for the Pub/Sub topic.

To set the \f5transport\-topic\fR attribute:
.RS 2m
.IP "\(bu" 2m
provide the argument \f5\-\-transport\-topic\fR on the command line.
.RE
.sp


.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.