...
Meetings: TBDMonday 10-11 EST (16-17 German time)
Meeting room: https://meet.lrz.de/tcdistributedvscentralized or Zoom / Slack Huddle.
| Table of Contents |
|---|
...
Configuration and customization in FOLIO discusses the problems with mod-configuration and outlined possible approaches to resolving them (independent implementations, a Java library, a FOLIO module), tentatively concluding that fixes to mod-configuration might be the best approach.
Fixing the security problem in mod-configuration discusses in more detail what changes would be needed to mod-configuration in order for it to become a reasonable choice for configuration, making a concrete proposal and outlining how the old and new APIs would co-exist.
- The mod-settings README describes what actually got implemented: because mod-configuration is based on the outdated RMB foundation and contains a lot of obsolescent code, it turned out to be easier to leave it as it is for present (maintaining compatibility for code that uses it) and implement the new, secure, scope-based API in a new module instead.
Porting your module from mod-configuration to mod-settings is a detailed practical guide to switching from the old module to its replacement, based on Mike's experiences doing this with ui-ldp. Contains links to the updated code, which can act as an example for people porting other apps.
A user-interface for FOLIO customization is a proposal for how we could use centralized configuration to provide a means for librarians and administrators to configure FOLIO in a centralized manner.
Scope of the group /deliverables
This group will limit its remit to configuration stored within FOLIO itself.
- Settings stored in Okapi's /_/env APIs should be excluded.
Settings stored in Rancher's config maps and secrets should be excluded.
Settings stored in module container environment variables should be excluded.
Settings stored in the stripes front-end (stripes.config.js, etc.) should be excluded.
We should limit to settings back-end modules store in the database.
Questions to be answered:
- Shall tenant level configuration stored in a central module or distributed in modules.
...
- Pros / cons of approaches
- Level of relative effort to accomplish the solution, what is the transition way.
- Eventually give guidance when to use central or distributed configuration.
RFC or only a DR?
Types of configurations
System settings (the same for all Tenants, all modules)
...