[FOLIO-1606] Add mod-event-config to CI testing builds Created: 01/Nov/18 Updated: 12/Nov/18 Resolved: 08/Nov/18 |
|
| Status: | Closed |
| Project: | FOLIO |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None |
| Type: | Task | Priority: | P3 |
| Reporter: | Oleksii Maksymov | Assignee: | Wayne Schneider |
| Resolution: | Done | Votes: | 0 |
| Labels: | ci, integration, sprint50 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||||||
| Sprint: | |||||||||||||
| Comments |
| Comment by Khalilah Gambrell [ 02/Nov/18 ] |
|
Wayne Schneider - Should Oleksii Maksymov just add mod-event-config to the folio-testing AWS instance given the RAM issues? |
| Comment by Wayne Schneider [ 08/Nov/18 ] |
|
We are adding this as requested to folio-testing.aws.indexdata.com, but not to the folio/testing-backend Vagrant VM due to memory limitations (see
|
| Comment by Wayne Schneider [ 08/Nov/18 ] |
|
I note that the interface defined in the module descriptor has the id of "mod-event" – perhaps this should just be "event"? |
| Comment by Wayne Schneider [ 08/Nov/18 ] |
|
mod-event-config will be included in the next build of folio-testing.aws.indexdata.com. |