openlmis-ref-distro

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
changed notification service version to 4.1.2-SNAPSHOT
changed notification service version to 4.1.2-SNAPSHOT
OLMIS-6413: Use orderable versioning in requisition line items
OLMIS-6413: Use orderable versioning in requisition line items
OLMIS-6351: Dropped reference to orderable version from FTAP
OLMIS-6351: Dropped reference to orderable version from FTAP
Are there other location types that we may need to consider? If so, would we want this description to be more general?

Are there other location types that we may need to consider? If so, would we want this description to be more general?

Geographic

Geographic

Is it likely that an ERP system might be the source of truth for this kind of data, rather than OLMIS? I am thinking of a country that wants to use OpenLMIS primarily for the requisition process bu...

Is it likely that an ERP system might be the source of truth for this kind of data, rather than OLMIS? I am thinking of a country that wants to use OpenLMIS primarily for the requisition process but leverage an existing ERP system for inventory-related processes.

Would OpenLMIS be the source of truth for cce or would a monitoring system like NexLeaf?

Would OpenLMIS be the source of truth for cce or would a monitoring system like NexLeaf?

Is bearer tokens the only method that we want to support?

Is bearer tokens the only method that we want to support?

Also, if you add something about smart endpoints/dump pipes, including some detail about what that means in practice would be helpful as well.

Also, if you add something about smart endpoints/dump pipes, including some detail about what that means in practice would be helpful as well.

I would prefer to lowercase device, so it doesn't get confused with FHIR's Device.

I would prefer to lowercase device, so it doesn't get confused with FHIR's Device.

a part

a part

comes from

comes from

Datetimes

Datetimes

Would you be able to add something in here about smart endpoints and dumb pipes? I think it would be helpful.

Would you be able to add something in here about smart endpoints and dumb pipes? I think it would be helpful.

OLMIS-5584, change toc depth to 2
OLMIS-5584, change toc depth to 2
Change base image of openlmis/awscli to alpine

Since openlmis/dev is based on an image based on alpine,

we can reduce the image size by using alpine directly.

By using the same version of alpine as openlmis/dev base java image,

we can keep the benefit of having to download less layers when used in

the same environment as openlmis/dev.

Signed-off-by: Morris Mukiri <morrismukiri@gmail.com>

Merge pull request #70 from OpenLMIS/update-spec

Update spec

Make the orderable ID not unique since an orderable can have multiple programs

Update process groups templates

    • -1190
    • +1207
    /reporting/nifi-flows/OpenLMIS_v3_reference_data.xml
    • -1206
    • +1205
    /reporting/nifi-flows/superset_permissions.xml
Add reference data configs with the jolt spec

    • -0
    • +72
    /reporting/jolt-spec/jolt-spec.json
Update nifi process groups versions