Eventarc Pipeline

Docs > DDSQL Reference > Data Directory > Eventarc Pipeline

Eventarc Pipeline is a Google Cloud resource that enables the creation of event-driven workflows by connecting event sources to destinations through a managed pipeline. It allows users to route, filter, and transform events across Google Cloud services and external systems. This helps automate processes and integrate applications using standardized event formats.

gcp.eventarc_pipeline

Fields

ID	Type	Data Type	Description
_key	core	string
ancestors	core	array<string>
annotations	core	hstore	Optional. User-defined annotations. See https://google.aip.dev/128#annotations.
create_time	core	timestamp	Output only. The creation time. A timestamp in RFC3339 UTC "Zulu" format, with nanosecond resolution and up to nine fractional digits. Examples: "2014-10-02T15:01:23Z" and "2014-10-02T15:01:23.045123456Z".
crypto_key_name	core	string	Optional. Resource name of a KMS crypto key (managed by the user) used to encrypt/decrypt the event data. If not set, an internal Google-owned key will be used to encrypt messages. It must match the pattern "projects/{project}/locations/{location}/keyRings/{keyring}/cryptoKeys/{key}".
datadog_display_name	core	string
destinations	core	json	Required. List of destinations to which messages will be forwarded. Currently, exactly one destination is supported per Pipeline.
etag	core	string	Output only. This checksum is computed by the server based on the value of other fields, and might be sent only on create requests to ensure that the client has an up-to-date value before proceeding.
gcp_display_name	core	string	Optional. Display name of resource.
input_payload_format	core	json	Optional. The payload format expected for the messages received by the Pipeline. If input_payload_format is set then any messages not matching this format will be treated as persistent errors. If input_payload_format is not set, then the message data will be treated as an opaque binary and no output format can be set on the Pipeline through the Pipeline.Destination.output_payload_format field. Any Mediations on the Pipeline that involve access to the data field will fail as persistent errors.
labels	core	array<string>	Optional. User labels attached to the Pipeline that can be used to group resources. An object containing a list of "key": value pairs. Example: { "name": "wrench", "mass": "1.3kg", "count": "3" }.
logging_config	core	json	Optional. Config to control Platform Logging for Pipelines.
mediations	core	json	Optional. List of mediation operations to be performed on the message. Currently, only one Transformation operation is allowed in each Pipeline.
name	core	string	Identifier. The resource name of the Pipeline. Must be unique within the location of the project and must be in `projects/{project}/locations/{location}/pipelines/{pipeline}` format.
organization_id	core	string
parent	core	string
project_id	core	string
project_number	core	string
region_id	core	string
resource_name	core	string
retry_policy	core	json	Optional. The retry policy to use in the pipeline.
satisfies_pzs	core	bool	Output only. Whether or not this Pipeline satisfies the requirements of physical zone separation
tags	core	hstore_csv
uid	core	string	Output only. Server-assigned unique identifier for the Pipeline. The value is a UUID4 string and guaranteed to remain unchanged until the resource is deleted.
update_time	core	timestamp	Output only. The last-modified time. A timestamp in RFC3339 UTC "Zulu" format, with nanosecond resolution and up to nine fractional digits. Examples: "2014-10-02T15:01:23Z" and "2014-10-02T15:01:23.045123456Z".
zone_id	core	string