[FOLIO-2583] Spike: Distributed configuration Created: 04/May/20 Updated: 28/Aug/20 |
|
| Status: | Open |
| Project: | FOLIO |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None |
| Type: | Story | Priority: | P3 |
| Reporter: | Craig McNally | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||||||
| Sprint: | CP: Non-roadmap backlog | ||||||||||||
| Development Team: | Core: Platform | ||||||||||||
| Description |
OverviewOne outcome of
An idea was proposed that all modules have a system interface which can be implement (or not), that presents a common interface for accessing configuration specific to various modules. e.g. each module would have the opportunity to implement the "config" interface and implement:
Each of which would be protected by discrete permissions, e.g. mod-foo might have:
Acceptance Criteria
|
| Comments |
| Comment by Taras Spashchenko [ 15/May/20 ] |
|
It looks like I did not comprehend the goal of implementing this distributed configuration. |
| Comment by Craig McNally [ 28/May/20 ] |
|
Taras Spashchenko how would external configuration storage work with permissions? The main challenge we face here is that the permissions in mod-configuration are not granular enough. You're either able to access all config entries, or none of them. By distributing the configuration we're able to better control who can access which configuration entries... i.e. a user might need to access orders configuration but not SAML or email configuration. That's not to say that we the underlying storage can't be some external system, but users shouldn't be able to go directly to that storage to access configuration, otherwise we're back to all or nothing access. |
| Comment by Craig McNally [ 27/Aug/20 ] |
|
See https://folio-org.atlassian.net/wiki/display/DD/Distributed+Configuration |
| Comment by Taras Spashchenko [ 28/Aug/20 ] |
|
Thank you. |