Events are collected from event providers by an Eventarc Advanced bus and routed through an Eventarc Advanced pipeline to a specified destination. Only one destination can be the target of messages forwarded by a pipeline.
Supported providers
Supported providers include Google providers and direct publishers of events (using the Eventarc Publishing API).
-
Google providers send Google events directly from the source (for example, the creation of a Cloud Run function or a status change to a Dataflow job). You must first enable support for Google event types. For more information, see Publish events from Google sources .
-
Event publishers can publish a CloudEvents event directly to a message bus in a supported format such as Avro or Protobuf. For more information, see Publish events directly .
Supported destinations
An Eventarc Advanced pipeline enables the delivery of events between a bus and a destination. The following destinations are supported:
-
Cloud Run—Use the stable, auto-assigned
run.appURL provided on the first deployment of the Cloud Run-hosted service. You can also target a Cloud Run job or specify an HTTP endpoint for Cloud Run functions ( 1st gen and current version ). When you specify an HTTP trigger for a Cloud Run function, the function is assigned a URL at which it can receive requests. -
Eventarc Advanced bus—The message bus must be deployed in the same project and region as the pipeline.
-
HTTP endpoint—A destination URI. The host can be either a static IP addressable from a Virtual Private Cloud (VPC) network , or the internal Domain Name System (DNS) hostname of a service resolvable using Cloud DNS. For example, you can target a Cloud Run service URL or a BigQuery table that will receive events as HTTP
POSTrequests. -
Pub/Sub topic—The Pub/Sub topic must first be created before messages can be routed to it and must be located in the same project as the pipeline. If using a topic schema , make sure to transform your event message appropriately.
-
Workflows—You can trigger the execution of a workflow which is a single run of the logic contained in a workflow definition. This lets you run services in an order that you specify. The workflow must be deployed in the same project as the pipeline.
