Force Vagrant to reinstall or load a new box on the next vagrancy

Question

If I changed the provisioning scenarios, or worse, the base OS, is there a way to get the stroller to either re-provide or reload the base box? I tried changing config.vm.box and config.vm.box_url , but vagrant up is still loaded to the old one.

I know that I could use vagrant destroy and then vagrant up or vagrant provision only to reinitialize on my own machine, but I'm talking about what automatically forces my command to re-provision / reinitialize (for example, after they will do git pull and then a vagrant up , either reinstall or reinitialize accordingly.)

Answer 1

vagrant box --help gives you several options.
In particular, you can vagrant box remove <name> <provider> remove a field and force a reassignment.

For example, to remove a strollers pattern field:

 vagrant box remove precise32 virtualbox