[FOLIO-612] Test data could live in a dedicated back-end module Created: 19/May/17 Updated: 18/Jan/19 |
|
| Status: | Open |
| Project: | FOLIO |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None |
| Type: | New Feature | Priority: | P3 |
| Reporter: | Heikki Levanto | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | dublin | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||||||||||
| Sprint: | |||||||||||||||||
| Development Team: | Core: Platform | ||||||||||||||||
| Comments |
| Comment by Heikki Levanto [ 19/May/17 ] |
|
What if we had a back-end module that only loaded test data into the database, using our APIs. The module would of course depend on the back-end modules that implement the storage layer for that kind of data. It would just have its tenant interface plugging the data in, and after that, offer no other services. |
| Comment by Heikki Levanto [ 20/May/17 ] |
|
Adam came with another good example: The "diku-admin" module that only pushes in the diku-admin user and his permissions. (Hmm, can we use module-permissions in the tenant interface? Need to check) |