#110229Provide a `messenger:setup-transports` console command
Description
Symfony Messenger ships a “messenger:setup-transports” command that prepares the
infrastructure (e.g. the database table) of the configured transports, but TYPO3
does not expose it.
TYPO3 should provide a native “messenger:setup-transports” console command that
prepares the infrastructure of the configured messenger transports, while NOT
touching transports whose schema is managed by TYPO3 itself.
Expected
./bin/typo3 messenger:setup-transportssets up every transport that needs it../bin/typo3 messenger:setup-transports <name>sets up only the given
transport.
Managed transports must be skipped
The shipped Doctrine transport (“doctrine”) stores its messages in the
“sys_messenger_messages” table, whose schema is created and updated by the TYPO3
schema management (ext_tables.sql), not by the transport. Running the transport
self-setup against it would reconcile the table to Symfony’s expected shape
(“id” INT vs BIGINT, single-column indexes vs one composite index) and fight
TYPO3’s schema management.
Such a transport must therefore be skipped. It is flagged via a new marker
interface TYPO3\CMS\Core\Messenger\SchemaManagedTransportInterface; the shipped
Doctrine transport is created as schema-managed whenever automatic setup is
disabled (which TYPO3 does for “sys_messenger_messages”). The synchronous
“default” transport is not a receiver and does not support setup either.
On a standard installation the command therefore reports that there is nothing
to set up; it becomes relevant once an additional Doctrine transport with its
own table (and auto_setup enabled) is configured.
Details
- The command is not offered as an EXT:scheduler task (one-off,
deployment-time operation, not a recurring background job). - Sibling of the “messenger:stats” command (#110228).
Reviews 1
History 05
-
Gerrit Code Review pushed patch set 1 for main to change 94836 status
NewUnder Review <span data-processor="relativetime" data-value="2026-07-19T20:38:24+00:00" > 07/19/26, 20:38 </span> -
Gerrit Code Review pushed patch set 2 for main to change 94836 <span data-processor="relativetime" data-value="2026-07-19T23:39:30+00:00" > 07/19/26, 23:39 </span>
-
Gerrit Code Review pushed patch set 3 for main to change 94836 <span data-processor="relativetime" data-value="2026-07-20T13:14:12+00:00" > 07/20/26, 13:14 </span>
-
Gerrit Code Review pushed patch set 4 for main to change 94836 <span data-processor="relativetime" data-value="2026-07-28T06:29:56+00:00" > 07/28/26, 06:29 </span>
-
Gerrit Code Review pushed patch set 5 for main to change 94836 <span data-processor="relativetime" data-value="2026-08-01T20:36:49+00:00" > 08/01/26, 20:36 </span>