Role of a connector
A connector owns system-specific behavior. It makes registry information practical inside the target environment without requiring the registry itself to implement that environment's internal APIs or lifecycle.
Typical responsibilities
- Discovering configured registry sources.
- Translating extension metadata into system-specific representations.
- Integrating download, installation and update workflows.
- Handling authentication and errors at the system boundary.
- Documenting compatibility with supported system versions.
First implementation
The current connector targets Shopware. Its implementation and concrete setup documentation live in the Extension-Mesh/shopware repository.
Moving system-specific concerns into that repository keeps project-wide documentation honest: the current architecture may inform future connectors, but it is not presented as proof that every system has the same requirements.
Future connectors
Additional connectors are possible when a concrete maintainer and use case exist. A proposed connector should document its target system, lifecycle, registry requirements and the differences from existing implementations.