I removed the rule for the kernel: its not needed, we already override the auto-discovered App\Kernel class by an alias to kernel.

Thank you @nicolas-grekas.

Related recipe PR: symfony/recipes#1391

It doesn't seem like I can opt-out from this, can I?

I wanted several entities to be discoverable by a service locator, so I made some of them implement a tagged interface to do so.

The purpose of that is that several our entities define custom SQL behaviour outside of the scope of ORM/DBAL (triggers, stored functions, ...) and because the SQL is tightly coupled with those entities, I thought it would be OK to just add a public function provideCustomQueries(): \Generator method to entities that need it. Later on, I'm listening to the migrationsMigrated event in a service that collects said entities, iterates through the list, extracts the custom SQL and executes whatever the entities want to do.

--

Update: never mind. I tweaked my custom SQL mechanism to rely on Doctrine's class metadata to find known entities that implement specific interfaces. I guess the entire mechanism relates to Doctrine, so using the container to find the right classes was more elegant but not entirely required.