polysource/adapter-messenger

Polysource Admin — Symfony Messenger failed transport data source.

v0.1.1 2026-05-10 21:00 UTC

Requires

• php: >=8.1
• polysource/core: ^0.1
• polysource/symfony-bundle: ^0.1
• symfony/config: ^6.4 || ^7.0 || ^8.0
• symfony/dependency-injection: ^6.4 || ^7.0 || ^8.0
• symfony/http-kernel: ^6.4 || ^7.0 || ^8.0
• symfony/messenger: ^6.4 || ^7.0 || ^8.0

Requires (Dev)

• phpunit/phpunit: ^10.5 || ^11.5

MIT

• admin
• symfony-messenger
• polysource
• failed-messages

README

Polysource adapter exposing Symfony Messenger's failed transport as a read-only Polysource resource.

This is the cas tueur for v0.1: Symfony's Messenger has no built-in admin UI for inspecting failed messages — only the messenger:failed:* CLI. polysource/adapter-messenger plugs into the same failed transport and renders it inside /admin/failed-messages.

Installation

composer require polysource/adapter-messenger

The bundle auto-registers via Symfony Flex.

Configuration

# config/packages/polysource_messenger.yaml
polysource_messenger:
    failed_transport_name: failed   # default

The named transport must implement Symfony\Component\Messenger\Transport\Receiver\ListableReceiverInterface (Doctrine, Redis, AMQP, InMemory all do). The bundle throws a LogicException at boot if the transport is non-listable.

What the resource exposes

Property	Source
message_class	Envelope::getMessage()::class
failed_at	RedeliveryStamp::getRedeliveredAt() (UTC)
exception_class	ErrorDetailsStamp::getExceptionClass()
exception_message	ErrorDetailsStamp::getExceptionMessage()
payload	JSON-encoded message body, var_export fallback (ADR-006)
payload_format	'json' or 'var_export'

Records over 50 KB are truncated with a marker.

Status

v0.1 — read-only. Retry / dismiss / retry-all / purge actions ship in Phase 5 of the development plan.

Architectural decisions

• ADR-001 — identifier type
• ADR-002 — count = null for cursor sources
• ADR-006 — payload serialization

License

MIT