[FOLIO-1030] Add module.eholdings.enabled permission to backend builds Created: 15/Jan/18 Updated: 12/Nov/18 Resolved: 17/Jan/18 |
|
| Status: | Closed |
| Project: | FOLIO |
| Components: | Continuous Integration |
| Affects versions: | None |
| Fix versions: | None |
| Type: | Task | Priority: | P3 |
| Reporter: | Mike Taylor | Assignee: | Wayne Schneider |
| Resolution: | Done | Votes: | 0 |
| Labels: | ci, sprint30 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | 30 minutes | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||||||
| Sprint: | |||||||||||||
| Description |
|
Mostly so that the module.eholdings.enabled permission exists, and doesn't need to be laboriously added the manual process at https://github.com/folio-org/stripes-core/blob/master/doc/adding-permissions.md every time I restart the VM. |
| Comments |
| Comment by Mike Taylor [ 16/Jan/18 ] |
|
And don't forget its sibling, settings.eholdings.enabled! |
| Comment by Wayne Schneider [ 16/Jan/18 ] |
|
Permissions have been added to the defaults in folio-ansible, should be set on folio-testing and the Vagrant boxes at next successful build. |
| Comment by Wayne Schneider [ 17/Jan/18 ] |
|
Confirmed: diku_admin user has the permissions in the backend builds. Now we just need the module (
|
| Comment by Mike Taylor [ 17/Jan/18 ] |
|
Thanks, that's great! |