Hi,

I'm using vagrant-aws while developing cookbooks to use on Amazon Linux. 
I'm also using vagrant-berkshelf for cookbook dependency mapping.

I'm finding that running *vagrant up *works as intended but running *vagrant 
provision *does not actually update the cookbooks on the instance. Is this 
supposed to work or is it not currently a supported feature of vagrant-aws? 
I've just been using destroy + up to apply changes.

If it is supported then I figured it was something to do with my workflow 
with berkshelf. Has anyone got this working?

Regards,
Yoshi

-- 
You received this message because you are subscribed to the Google Groups 
"Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to