Skip to content

Deliver EventBridge events to matched rule targets - #46

Merged
damianh merged 2 commits into
mainfrom
dh/eventbridge-deliver-matched-rule-targets
Nov 12, 2026
Merged

damianh merged 2 commits into
mainfrom
dh/eventbridge-deliver-matched-rule-targets

Conversation

@damianh

@damianh damianh commented Nov 12, 2026 •

Copy link
Copy Markdown
Owner

EventBridge currently accepts PutEvents requests but does not deliver events to matched rule targets, which can make successful responses misleading. This adds synchronous in-process delivery for supported Lambda, SQS, and SNS targets using their existing handler protocols and standard EventBridge event envelopes.

Delivery failures and unsupported target types are now reflected in PutEvents entry results and FailedEntryCount. Integration tests cover all three supported target types, suppression for non-matching events, and delivery failure responses.

Validation: dotnet test --project tests/MicroStack.Tests/MicroStack.Tests.csproj --filter-class '*EventBridgeTests*' (36 passed, 0 failed, 0 skipped); git diff --check.

Fixes: #29


Read this PR faster    Follow each request

Route matched events to supported Lambda, SQS, and SNS targets, and report delivery failures in PutEvents results. Add integration coverage for delivery, non-matches, and failure cases.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
@coldtea-pr-lens

coldtea-pr-lens Bot commented Nov 12, 2026 •

Copy link
Copy Markdown
  • Redraw · drawn at c654016, the branch has moved on

Architecture

Walkthrough of Dispatch EventBridge events to SQS, SNS, and Lambda, in five steps

Read this PR faster

Inside the changed components — 1 view

Component view — EventBridge dispatch

Internal resolution and delivery to supported target services.

Architecture view of Component view — EventBridge dispatch in damianh/microstack

Data flow

Data flow diagram for damianh/microstack at c654016

Follow each request


Review

2 findings on the diff · reviewed c654016

Tip

Set github.draw: on-demand in .github/pr-lens.yml and PR Lens stops drawing pull requests on its own. Comment @pr-lens draw on a pull request when you want that one drawn

🪧 More tips
  • Run npx skills add coldteadotai/pr-lens, then tell your coding agent: "Diagram the change you just made with PR Lens and attach it to the pull request."
  • Run npx @coldtea/pr-lens-cli analyze --base origin/main on a branch, then npx @coldtea/pr-lens-cli render .pr-lens/graph.json. Same lenses, your own model key, before the pull request exists
  • Click the link under each diagram to open it on a canvas you can zoom, pan and step through
  • The diagrams are links. Click one to open it on the canvas, then press W or click play to walk through the change
  • Open a diagram on the canvas, then press W or click play to walk through the change one step at a time
  • The CLI's render reads .github/pr-lens.yml and applies your renames, exclusions and lane pins at draw time
  • Set github.comment.collapsed: true in .github/pr-lens.yml to fold the comment behind one View architecture… row. Drawing still runs as before
  • Add .github/workflows/pr-lens.yml with coldteadotai/pr-lens/packages/action@v0 and your model provider's key as its api-key to run PR Lens from your own CI. Any /chat/completions endpoint works
  • After a push, tick Redraw to draw the latest commit
  • Switch GitHub to dark mode and the diagrams follow. The moving dots are this pull request's data in motion
  • Set github.description: false in .github/pr-lens.yml to stop PR Lens adding buttons to your PR descriptions

Thanks for using PR Lens! It's free for OSS. If it helped, a star helps other teams find it.  Star PR Lens on GitHub

Preserve numeric PutEvents timestamps in target envelopes and execute Lambda targets before acknowledging delivery. Verify Lambda execution with a marker side effect.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
@damianh
damianh merged commit 5719c9f into main Nov 12, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

EventBridge: deliver events to matched rule targets

1 participant