Skip to main content

GCP Pub Sub Subscription

Google Cloud Pub/Sub Subscriptions define how messages published to a particular topic are delivered to subscribers. A subscription persists messages on behalf of subscribers for a configurable retention period, manages acknowledgement flow control, and can be configured for pull or push delivery, dead-lettering and filtering.
See the official documentation for full details: https://cloud.google.com/pubsub/docs/reference/rest/v1/projects.subscriptions#Subscription

Terrafrom Mappings:

  • google_pubsub_subscription.name

Supported Methods​

  • GET: Get a gcp-pub-sub-subscription by its "name"
  • LIST: List all gcp-pub-sub-subscription
  • SEARCH

gcp-pub-sub-subscription​

A subscription can reference another subscription as its dead-letter target. Overmind records that link so you can trace where undeliverable messages will be sent.

gcp-pub-sub-topic​

Every subscription is attached to exactly one Pub/Sub topic—the source of the messages it receives. This parent-child relationship is always mapped.

gcp-big-query-table​

If the subscription is configured as a BigQuery subscription, messages are streamed directly into the specified BigQuery table. Overmind links the subscription to that destination table so that downstream data flow can be inspected.

gcp-storage-bucket​

For Cloud Storage subscriptions, Pub/Sub writes each message as an object to the configured bucket. This link shows where message payloads are persisting in Cloud Storage.