[FOLIO-666] Retain previous folio-demo system as folio-demo-last Created: 12/Jun/17 Updated: 18/Jan/19 |
|
| Status: | Open |
| Project: | FOLIO |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None |
| Type: | New Feature | Priority: | P3 |
| Reporter: | Jason Skomorowski | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Sprint: | |
| Development Team: | Core: Platform |
| Description |
|
Rather than discarding the AWS machine for folio-demo when rebuilding it, perhaps it would be cheap insurance to rename it a folio-demo-last just in case? Don't go out of your way, but would be reassuring in situations like now when the demo is being redeployed the day before a review meeting. (Although wouldn't have done much now as folio-demo was fairly broken). |