[chef] Re: Re: Re: commands output for execute/script resources

[Brian McKelvey < >]

Also, it would be nice if there was some indication of what script is being 
executed that would show up in the log before the Script executes.  I often 
use the script resource for compiling things, and the log doesn't display 
anything until the compilation is complete, so if you're watching the log, it 
feels like the process just hung instead of having an indication of what's 
going on.

Brian

Sent from my iPad

On Nov 2, 2010, at 10:25 AM, Alex Soto 
<
 >
 wrote:

> I'd like to see:
> - the ability to turn on the command output when the command fails instead 
> of the error message Dan mentioned
> - when you tell it to ignore a non-zero result code, I'd like to not 
> display the output
> 
> On Nov 2, 2010, at 9:18 AM, Seth Falcon wrote:
> 
>> Hi,
>> 
>> On Tue, Nov 2, 2010 at 7:55 AM, Vladimir Girnet
>> <
 >
>>  wrote:
>>> Sometimes it is required to see output of a command or a script. I know 
>>> that
>>> "-l debug" will display it, but it will also display a lot of non-required
>>> debug information.
>>> 
>>> Is there a way to display output of a specific "execute", "package" or
>>> "script/bash" resources, except debug mode?
>>> 
>>> Is it possible to add for "execute", "package" and "script/bash" 
>>> resources a
>>> new option "output", which is by default false, but can be set to true to
>>> display execution results?
>> 
>> Is it that you want to process the output of a resource or just see it
>> in the logs in more detail?
>> If I'm understanding right, you just want the output to appear in the
>> log.  I'd like to understand a bit more on the motivation.  Is this
>> for debugging, but where debug -l produces too much info or for
>> another purpose?
>> 
>> + seth
>