This is basically the setup we've been using with vagrant (and in production) for years. Vagrant launches a bare-bones VM. Local files mount on /vagrant Ch

This is basically the setup we've been using with vagrant (and in production) for years. Vagrant launches a bare-bones VM. Local files mount on /vagrant Chef-zero uses local mount to provision the systems and configurations necessary. On every vagrant reload, this process repeats. Chefs idempotent nature means that any manual drift is automatically repaired. In this setup there's no difference between `vagrant reload` and `vagrant destroy && vagrant up`. It's possible to package this so that it's simultaneously "Infrastructure as Code" while also satisfying "Immutable Infrastructure". Our stab at this is now 6 years old and we're surely not the first to do it.