Azure Event Grid

azurePub/Sub topicazure-event-grid

Managed push-based event router with 24-hour retry and optional dead-lettering.

Provider
azure
Category
Messaging
Properties · 4 set by this component
propertytypevaluesrequiredkind defaultthis component
deadLettering · component propertyboolean—nofalseinherited
deliveryenumat-most-once | at-least-once | exactly-onceyes—▸ at-least-once
managedboolean—nofalse▸ true
orderingenumnone | per-keynonone▸ none
replayboolean—nofalse▸ false
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: "event-grid", component: "azure-event-grid" }
Other Pub/Sub topic products · 12
Source
# yaml-language-server: $schema=../../schema/component.schema.json
# Azure Event Grid: push-based event routing, at-least-once with 24 hours of retries; no replay,
# dead-lettering to a storage account is opt-in.
schemaVersion: "1"
type: "component"
id: "azure-event-grid"
kind: "pubsub-topic"
provider: "azure"
docs: "https://learn.microsoft.com/en-us/azure/event-grid/overview"
defaults:
  managed: true
  delivery: "at-least-once"
  ordering: "none"
  replay: false
properties:
  deadLettering:
    type: "boolean"
    default: false

The same page as markdown, for an agent: /catalogue/components/azure-event-grid.md