[FOLIO-2799] Align Vagrant snapshot build with AWS folio-snapshot build Created: 15/Sep/20 Updated: 24/Feb/21 |
|
| Status: | Open |
| Project: | FOLIO |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None |
| Type: | Task | Priority: | TBD |
| Reporter: | Wayne Schneider | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||||||||||||||
| Sprint: | |||||||||||||||||||||
| Development Team: | FOLIO DevOps | ||||||||||||||||||||
| Description |
|
The mechanism for identifying extra backend modules that are not part of the Stripes platform's dependency graph is different for the Vagrant snapshot build and the AWS folio-snapshot build. The Vagrant build identifies the extra modules in a variables file in folio-ansible, while the AWS build uses the install-extras.json file from the platform-complete repository snapshot branch. The work for AWS was done as ticket
|