Hi all,
currently, we have several base services that can be used to develop adapters + pipeline elements: streampipes-container-standalone (supports data processors and sinks) streampipes-container-connect-worker (for adapters) streampipes-container-extensions (for adapters, data processors and sinks, but this seems to be more like a quick fix and duplicates code from the other two modules) Is there any use case where we want an extensions container to not support adapters, processors and sinks at the same time? As I'm currently doing the rather large refactoring related to service discovery where I would need to touch all these modules, I tend towards having one single service that supports development of all extensions - what do you think? Dominik
