Context
The engine's startup path previously obtained a single DebeziumConnectorRegistry from the CDI container and iterated its engines directly. This worked for single-connector deployments but had no way to aggregate engines from multiple connectors (e.g., Postgres + MySQL running side by side), and no mechanism to selectively start only a subset of those engines.
Changes
We should support multi connector engines with filtering rule for startup
Context
The engine's startup path previously obtained a single
DebeziumConnectorRegistryfrom the CDI container and iterated its engines directly. This worked for single-connector deployments but had no way to aggregate engines from multiple connectors (e.g., Postgres + MySQL running side by side), and no mechanism to selectively start only a subset of those engines.Changes
We should support multi connector engines with filtering rule for startup