Generally test-kitchen is a better approach than using vagrant-berkshelf and vagrant-omnibus. The latter two are somewhat deprecated and are mostly falling behind test-kitchen's features.
On 05/02/2015 06:23 PM, Christopher Hahn wrote:
Pardon the chaff….I am pretty sure that feeding the —debug flag to vagrant, thrumy build.gradle exec block, will tell me what I need to know.
Take care,
Christopher
On May 2, 2015, at 6:00 PM, Christopher Hahn < " target="_blank"> > wrote:
Hello,
I managed to take from the small README that this plugin has on github that it helpsvagrant sync a berkshelf on the Node so that it can then launch chef-solo to provision it.
I would love to find a bit more documentation was to just *what it is doing during vagrant actions*
i.e. what precisely happens between: and the:
17:54:27.468 [INFO] [org.gradle.process.internal.DefaultExecHandle] Starting process 'command '/usr/bin/vagrant''. Working directory: /Users/chahn/Projects/vistacore/cdsdashboard/infrastructure/vagrant/virtualbox/cdsdashboard Command: /usr/bin/vagrant provision cdsdashboard
and the:
Running chef-solo…
I am certain that I am needing to be directed elsewhere…this is just where I know to start.
Thank you,
Christopher
P.S. I did add a comment/question on the hub as well.
Archive powered by MHonArc 2.6.16.