Spike on JaVers / Envers
Description
Attachments
Confluence content
QAlity Plus - Test Management
Checklists
Activity
Hi @Brandon Bowersox-Johnson, yes I'm a guy from Poland, it's nice to hear that you work with developers from Gdansk and Gdynia Catch me on https://gitter.im/javers/javers in case of any troubles with JaVers.
Hi @bartosz walacik. Thanks for the offer of help on JaVers! Currently this particular ticket is Done, but we use JaVers for part of our "audit logging" feature inside OpenLMIS. If we have JaVers activity or questions in the future, it's great to know you. If you are based in Poland, you may be interested to know that many OpenLMIS developers are located in Gdansk and Gdynia!
FYI Heads Up to our Architect @Josh Zamor and Software Developer @Ben Leibert who have worked with JaVers in OpenLMIS.
Hi, let me know if you need some help with JaVers (I'm JaVers committer)
Note that Audit Logging of State Changes and Audit Logging of User Activities are currently being used as our business requirements. The former mentions that "our original table should be extended." This is an implementation detail rather than business requirement, however, which needn't be honored.
From discussion with @Mary Jo Kochendorfer, @Ben Leibert and @Josh Zamor we thought we can move ahead with Javers for auditing a single resource in a service for 3.0. For future releases we may revisit the idea of a centralized auditing service.
Created https://openlmis.atlassian.net/browse/OLMIS-1605#icft=OLMIS-1605 to publish the pattern for future work to copy. Moving this to done.
Details
Assignee
Reporter
Story Points
Components
Sprint
Fix versions
Priority
Time Assistant

Short spike on using JaVers or Envers for simple audit logging.
Inform:
recommend JaVers or Envers on basis of activity, license, features
quickly spike in the reference data service to show how the tool would work on a Facility.
examine how audit-logging will be limited cross-service (i.e. what happens to a UUID that's stored in a Requisition when the Facility is updated)
design doc that bullet points which pieces are needed to introduce the tool on an entity, and report on changes in the API