openlmis-ref-distro

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
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
Replace join with left join in materialized view

OLMIS-5492, upgrade to debezium 0.9.4

Merge pull request #72 from OpenLMIS/update-registry-versions

Update flows

Updated flows

    • -0
    • +5423
    /reporting/nifi-flows/generate_measure.xml
    • -0
    • +11718
    /reporting/nifi-flows/generate_measure_report.xml
    • -1263
    • +1708
    /reporting/nifi-flows/superset_permissions.xml
Version update for superset permissions flow in nifi registry and adding the measure flows

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

OLMIS-6050 Cap the NiFi Container Resource Usage (#68)

* OLMIS-6050 Cap the NiFi container resource usage

Make the memory limit and reservation for the NiFi container

configurable

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

* OLMIS-6050 make nifi cpu usage limit configurable

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

* OLMIS-6050 Set NiFi JVM Heap Max

Make the JVM Heap Max environment variable configurable.

Co-authored-by: Jason Rogena <jasonrogena@gmail.com>

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

* Update .env

Merge branch 'master' of github.com:OpenLMIS/openlmis-ref-distro