Description
I was going through the local setup automation scripts and noticed that
FLW-API is registered in lib/services.conf with its repo URL, port (8081),
and properties file, but there is no [flw] entry in lib/products.conf.
Because of this, running bash start.sh --product=flw doesn't work for
anyone trying to set up the FLW (Front Line Workers) module locally.
What's interesting is that the automation README actually uses FLW as the
example for how to add a new product, so this looks like it was accidentally
left out.
Affected File
amrit-local-setup/automation/lib/products.conf
Expected Behaviour
bash start.sh --product=flw should work the same way other products like
ecd or hl104 do.
Proposed Fix
Add flw to PRODUCT_APIS, PRODUCT_UIS, PRODUCT_DESC, and PRODUCT_ORDER
in products.conf. I checked FLW-API's common_example.properties and it
depends on TM-API and FHIR-API on top of the standard anchors (Common,
Identity, BeneficiaryID).
I would like to work on this if it can be assigned to me. @drtechie
Description
I was going through the local setup automation scripts and noticed that
FLW-API is registered in lib/services.conf with its repo URL, port (8081),
and properties file, but there is no [flw] entry in lib/products.conf.
Because of this, running bash start.sh --product=flw doesn't work for
anyone trying to set up the FLW (Front Line Workers) module locally.
What's interesting is that the automation README actually uses FLW as the
example for how to add a new product, so this looks like it was accidentally
left out.
Affected File
amrit-local-setup/automation/lib/products.conf
Expected Behaviour
bash start.sh --product=flw should work the same way other products like
ecd or hl104 do.
Proposed Fix
Add flw to PRODUCT_APIS, PRODUCT_UIS, PRODUCT_DESC, and PRODUCT_ORDER
in products.conf. I checked FLW-API's common_example.properties and it
depends on TM-API and FHIR-API on top of the standard anchors (Common,
Identity, BeneficiaryID).
I would like to work on this if it can be assigned to me. @drtechie