Date

7am PST / 4pm CEST

Meeting Link

https://zoom.us/j/994971678

Attendees


Discussion items

TimeItemWhoNotes
5mAgenda and action item reviewJosh Zamor
15mEnabling other services to read requisitions dataSebastian Brudziński
  • Malawi will build a new service that needs to read all/parts of requisitions' data
  • Possible workaround: create user and assign them rights to all programs and SNs (same as reporting stack)
  • Alternative: Enable service-level tokens or API keys to read requisition data
10mBetter determine usage of BASE_URL and VIRTUAL_HOST propertiesMateusz KwiatkowskiMateusz Wedeł (Unlicensed)In Angola, we needed to change BASE_URL property to enable Let's Encrypt with nginx to "nginx-reverse-proxy". This works fine considering communication between services but BASE_URL property is also used i.e. email notifications which results in incorrect URLs send to the users.
10mStock Management behavior with FTAP/Orderables updateSebastian Brudziński

Notes


Requisition Data


New microservice to read data from Requisition data in order to send metrics/indicators to an interop layer.

Problem:  the Requisition API's don't support service level tokens or other api keys meant to pull all data from Requisition.

Use-cases:


Is this a change in how we get data out of services?


BASE_URL and VIRTUAL_HOST


(encoutered in Angola)

Wanted to use Lets Encrpyt and move TLS termination to OpenLMIS Ref Distro component.

Introduced another layer of Nginx (as a reverse proxy and TLS termination)

Change to BASE_URL (this is the most used variable) and VIRTUAL_HOST was needed.

Proposal:  Split the variables, one for services and another for use in sending links. Not proposing ATM the addition of another nginx


Question:

Suggestion:


Stock Management behavior with FTAP/Orderables update


Action Items