As has been discussed previously, the VM image referenced in the
Vagrantfile for local development still seems to be created and updated by hand.
Has there been any more-recent discussion about switching to building it in an automated and documented way?
One major advantage of automating the VM build is to prevent this:
Rebuilding it instead of adding onto the same image over time could be a major advantage.
Given that actually starting up the Vagrant VM uses a bunch of Chef recipes to provision, why not just do the same using Packer and Chef to build the image?
Is the reason just because no one has spent the time on it, or is there something specific that is preventing this from happening?