Environment Adaptor (prev. Invoker) for mp-reactive-services

[dmitriyslaym]

General description

EnvAdaptor service is responsible for connecting to environment, send request to methods of this environment and expose logs. This service is specific to mp-reactive-services. We will probably define other adaptors in the future for other projects. The contract and the test cases of the service will be in capsula, the implementation should be in mp-reactive-services.

Prerequisites

None.

API

// DRAFT
interface EnvAdaptor {
  connect(connectRequest: ConnectRequest) : Promise<ConnectResponse>;
  disconnect(disconnectRequest: DisconnectRequest) : Promise<DisconnectResponse>;
  send(sendRequest: SendRequest): Promise<void>;
  logs(logsRequest: LogsRequest): Observable<LogEvent>;
}

Design description

A clear and concise description of the design proposition.

• [ ] Is it backward compatible ?
• [x] Adds new API
• [ ] Changes existing API
• [ ] Removes existing API

Behavior

TODO

Test cases

TODO

Ready for implementation

• [ ] External dependencies have been resolved
• [ ] API has been approved
• [ ] Test cases have been prepared
• [ ] Discussed with Product owner
• [ ] Discussed with Technical lead

Definition of Done

• [ ] Maintainer review
• [ ] All tests are implemented
• [ ] Manual QA
• [ ] Documentation
• [ ] Release notes

[idanilt]

@dmitriyslaym @stephanebenayoun I suggest that as long it's just a one line maybe issue, do all of them in backlog general issue or if it's related to a project board like "MVP" put it in txt in the board