Worker executor must track the active set of oplog processor plugins for each worker.
In details:
The initial set comes from the component's enabled set (and new optional parameters if the worker was explicitly started)
The Worker Executor gRPC API and Golem host functions allow adding/removing plugins for a worker
New oplog entries need to be added when the set of plugins change
The current active set is cached in the worker status record and is recomputable from the oplog
The outcome of this task is that there is full support for managing what oplog processor plugins are enabled for a worker but there is no actual oplog broadcast to them yet.
Worker executor must track the active set of oplog processor plugins for each worker. In details:
The outcome of this task is that there is full support for managing what oplog processor plugins are enabled for a worker but there is no actual oplog broadcast to them yet.