Build GET \services to return FXP providers for a particular currency conversion

Goal:

As a Mojaloop Community member interested in making use of the mojaloop FX flows I want to be able to ask Mojaloop for connected participants providing FXP services so that participants can discover FX services

Note: This fuctionallity is part of the PISP design and the FXP design flow. Here is a reference to the ... The FXP get services is specified here. https://github.com/mojaloop/mojaloop-specification/blob/master/fspiop-api/documents/v2.0-document-set/fspiop-v2.0-openapi3-implementation-draft.yaml The PISP get services is specified here. https://github.com/mojaloop/mojaloop-specification/blob/master/thirdparty-api/thirdparty-pisp-v1.0.yaml

This functionality must be updated through API's however this will not be suppored initially. The first version of this service will provide service data that is made available through configuration data of the service.

Acceptance Criteria:

[ ] Verify that a new microservice is added to provide the get Services functionality as a generic service
[ ] Verify that the new microservice support the FXP service calls that include currency coversion's specified.
[ ] Verify that the microservice can be configured to provide data to be returned through GET services calls.
[ ] Verify that the following are supported
- [ ] GET \services\FXP
- [ ] PUT \services\FXP
- [ ] GET \services\FXP{sourcecurrency}{targetcurrency}
- [ ] PUT \services\FXP{sourcecurrency}{targetcurrency}
[ ] Verify that the Helm is updated to deploy this service
[ ] Extend the outbound Mojaloop Connector (SDK) to include Get Services API GET --> GET + PUT (Sycn to Async mapping)
[ ] Update the Payer FX conversion POC Mojaloop Connector (SDK) to use the Get Services API call rather than use configured values.
[ ] Verify that the testing for this is done on this testing stack
[ ] Verify that the new repo follows the typescript template.

Complexity: <High|Medium|Low> > A short comment to remind the reason for the rating Uncertainty: <High|Medium|Low> > A short comment to remind the reason for the rating

Tasks:

[ ] TBD [ @? ]

Done

[ ] Acceptance Criteria pass
[ ] Designs are up-to date
[ ] Unit Tests pass
[ ] Integration Tests pass
[ ] Code Style & Coverage meets standards
[ ] Changes made to config (default.json) are broadcast to team and follow-up tasks added to update helm charts and other deployment config.
[ ] TBD

Pull Requests:

[ ] TBD

Follow-up:

Dependencies:

Accountability:

Owner: TBC
QA/Review: TBC

mojaloop / project