Debugging chef recipes without vagrant destroy and re-provision

Question

We are working on chef recipe that builds PHP from source. However, every time we make a change to our recipe and we want to run it again it takes a long time (about 20 minutes).

What we have been doing is making our changes then using:

vagrant destroy

followed by:

vagrant up

It would be nice if somehow we could just re-run our single recipe we are trying to update.

Anyone know how we could do this? Or how vagrant determines our php recipe is already installed/executed?

Answer 1

vagrant provision should do this for you. Chef should take care of only running the things that need to be run...like a changed recipe.