- From: Bryan McLellan <
>
- To:
- Subject: [chef] Whyrun verbosity
- Date: Mon, 30 Jul 2012 16:38:06 -0400
Here's an whyrun output where we're only going to change the utime on
a file, but there's still a screen full of output.
You'll notice two outputs, "verbose_logging_true" is what happens by
default. "verbose_logging_false" is what happens if you put
'verbose_logging false' in your client.rb (it disables the processing
messages).
https://gist.github.com/55e296aa501ddad51d2a
Thankfully at the end of the run it tells us that 1 resource was
updated so we know to look back and visually scan for what changed to
ensure it was what we were expecting. This run is only with a couple
cookbooks, and I've seen much more output when running a node with the
wordpress cookbook which has lots of dependencies like apache and
mysql.
Also, there's a missing space between the action and the timestamp.
What do you think? I usually prefer verbose_logging off myself, but
definitely in this situation. Since verbose_logging defaults to true,
I'm not sure if we could optionally default it to false or not for
why-run.
We're starting a bit of a table to encourage folks to work together to
get some test coverage for Whyrun. Head over here to the wiki for more
information:
http://wiki.opscode.com/display/chef/Whyrun+Testing
--
Bryan McLellan | opscode | technical program manager, open source
(c) 206.607.7108 | (t) @btmspox | (b)
http://blog.loftninjas.org
- [chef] Whyrun verbosity, Bryan McLellan, 07/30/2012
Archive powered by MHonArc 2.6.16.