Failed/retry functionality not applied to transports defined before SmCompilerPass or outside of sm.transports parameter

Created on 16 July 2025, 22 days ago

Problem/Motivation

when a transport is defined and set up in the container elsewhere, before SM's SmCompilerPass, the default functionality for failures, retry, etc are no applied since the transports are not in sm.transports.

So transports provided by AMQP, Redis (Im working on), Doctrine, even InMemory in `SmTestTransportCompilerPass`, are not currently getting the nice retry/failure things we merged recently.

Steps to reproduce

@

Proposed resolution

The most straightforward user workaround is to define all transports in sm.transports.

A more permanent way of going forward could be, merging/squashing custom parameters into sm.transports. But that is less flexible, as other modules should be able to define transport services on their own.

Or we could allow others to fully define their transport, somehow tack on the "extra" transport configuration they carry, per `$transport` in SmCompilerPass, as a serialised tag value.

Remaining tasks

@

🐛 Bug report
Status

Active

Version

1.0

Component

Code

Created by

🇦🇺Australia dpi Perth, Australia

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Merge Requests

Comments & Activities

Production build 0.71.5 2024