[FOLIO-1515] folio-ansible: update okapi-tenant-modules role Created: 18/Sep/18 Updated: 12/Nov/18 Resolved: 26/Sep/18 |
|
| Status: | Closed |
| Project: | FOLIO |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None |
| Type: | Task | Priority: | P2 |
| Reporter: | Wayne Schneider | Assignee: | Wayne Schneider |
| Resolution: | Done | Votes: | 0 |
| Labels: | ci, q3-2018, sprint47 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||
| Sprint: | |||||||||
| Description |
|
The okapi-deploy service has outlived its usefulness for managing modules. It would be better to have modules deployed using the /_/discovery endpoint and allow Okapi to manage module persistence and (optionally) dependencies. The okapi-tenant-modules role has much of this in place, maybe it can just be enhanced to be able to be used for snapshot builds? |
| Comments |
| Comment by Wayne Schneider [ 25/Sep/18 ] |
|
Work to date merged into q3-release branch of folio-ansible. Yet to do (not needed for Q3 release):
|
| Comment by Wayne Schneider [ 26/Sep/18 ] |
|
We'll use
|