It seems that there is an active issue when resuming machines using Vagrant that triggers provisioning scripts on resume and not just when doing the original vagrant up command. EXAMPLE: The issue here is that I already have the build script executed on the original vagrant build of the machine. The scripts may not be idempotent, and could overwrite content …
