Releases: folio-org/mod-reporting
Releases · folio-org/mod-reporting
v1.1.0
- Modify permission names for the convenience of Eureka. Each endpoint is now governed my its own permission instead of
ldp.read
governing logs/tables/columns/query/reports. For backwards-compatibility,ldp.read
is retained as an umbrella that contains all five new fine-grained permissions. Fixes MODREP-7. - The
ldp-query
interface version number is incremented from 1.2 to 1.3. (A minor version bump suffices, as the current interface is backwards-compatible with the old.) ldp-config-tool
now serializes object values to strings. This means if you now fetch an object-valued config from mod-ldp, you can set it directly into mod-reporting. Fixes MODREP-10.- Bump default memory allocation from 20 Mb to 100 Mb to allow headroom for bigger query-result sets. Fixes MODREP-12.
v1.0.4
- Remove
env
section from the module-descriptor. This was causing FOLIO snapshot deployment to use a hardwired incorrect specification of the reporting database parameters.
v1.0.3
- Change launch-descriptor
portBindings§ to match the port exposed by
Dockerfile`. Fixes DEVOPS-3304.
v1.0.2
- Re-release to exercise updated GitHub actions. No code changes.
v1.0.1
- Changes to GitHub CI workflows. Supports deployment of mod-reporting to folio-snapshot reference environments. Part of DEVOPS-3304.