tree c115c6b769d974c9ae1959ae2527419010ea7bc2
parent b3e8605de1ce22650e468cdaed4da1c3228035de
author Saša Živkov <sasa.zivkov@sap.com> 1772795942 +0100
committer Saša Živkov <sasa.zivkov@sap.com> 1776154289 +0200

Define ApiModule: expose Forwarder, CommandProcessor and Commands

This change exposes DynamicItem<Forwarder> so that other plugins can
implement message forwarding using technology of their choice, for
example using a GCP pubsub.

Also expose DynamicItem<CommandProcessor>. This is not exposed to be
overridden but only as a mean for other plugins to inject it and pass
received commands back to the high-availability plugin. Injecting the
CommandProcessor directly would require exposing also its implementation
via the API-Module. This quickly pulls almost complete plugin
implementation into the API-Module including the ServerPluginInfoModule
which provides plugin specific bindings like "@PluginName String".
Since the injector created out of the API module is the parent injector
of the injector(s) created in dependent plugins, we would end up with
duplicated bindings for the @PluginName and MetricMaker types.
Using DynamicItem<CommandProcessor> we only expose the interface via the
API module to other plugins.

Change-Id: I57c8b27fa4caf6109d797494fac1a91789f056a0