Google Cloud Pub/Sub

gcpPub/Sub topicgoogle-pubsub

Managed global topic with per-subscription retention and seek, so consumers can replay.

Provider
gcp
Category
Messaging
Properties · 4 set by this component
propertytypevaluesrequiredkind defaultthis component
deliveryenumat-most-once | at-least-once | exactly-onceyes—▸ at-least-once
managedboolean—nofalse▸ true
orderingenumnone | per-keynonone▸ none
replayboolean—nofalse▸ true
retentionDays · component propertyinteger—no7inherited
topicPerEventType · advancedboolean—notrueinherited
Rules that apply · 1

Every rule whose selector covers this component's kind or its category. Whether a rule fires depends on the design: its properties, its edges and its groups.

pubsub-replay-required

The design declares that consumers must be able to replay history. A fan-out topic that does not retain messages cannot deliver that.

  • — all of these hold:
  • — the design requirement `messaging.replay` is true
  • — the node's `replay` is false
Use it in a design
nodes:
  - { id: "pubsub", component: "google-pubsub" }
Other Pub/Sub topic products · 12
Source
# yaml-language-server: $schema=../../schema/component.schema.json
# Google Cloud Pub/Sub: at-least-once, unordered unless ordering keys are used; subscriptions retain
# acked messages for seven days and support seek, so replay is true.
schemaVersion: "1"
type: "component"
id: "google-pubsub"
kind: "pubsub-topic"
provider: "gcp"
docs: "https://cloud.google.com/pubsub/docs/overview"
defaults:
  managed: true
  delivery: "at-least-once"
  ordering: "none"
  replay: true
properties:
  retentionDays:
    type: "integer"
    default: 7

The same page as markdown, for an agent: /catalogue/components/google-pubsub.md