Open hollyallen opened 9 years ago
@hollyallen Trying to understand what the value/impact of this story will be. Since we already have all the environments set up, when would a developer need to do this? Is this a nice to have or is this an existing problem that we are facing and critical to future development?
This is a project wellness task, and a step towards full system automation. I think this is more important than "nice to have" but not an immediate threat to the project. It will accelerate future development.
Ideally we'd be using ansible or docker or something to automate the setup and teardown of all our systems, be they test or production or on our local machines. Right now you have to do it all by hand. Automation would save time, greatly enhance reproducibility, encourage rapid testing, and discourage testing setups that are inadvertently different than production. @dnesting called this out as a gap when he joined the project, and I agree.
Right now our non-production environments are hand created. Success in this story is that for non-production environments at least we should have a script to spin up a new environment from scratch automatically. Ideally we do this in the 12-factor way, wrt service configuration process etc.