Hey Mike! Hope all is well, wondering if there any updates on outputting stdout/stderr ?
Thanks! On Thursday, 4 July 2013 08:03:38 UTC-4, Michael DeHaan wrote: > > Async mode could be upgraded to capture intermediate stdout/stderr as it > comes in, possibly. > > I don't want this done for non-async modes as it wouldn't make > architectural sense. > > > > > On Thu, Jul 4, 2013 at 3:58 AM, Dmitry Horbach <[email protected] > <javascript:>> wrote: > >> Hi All. >> >> Did anyone looked at having stdout printing as it comes or it is still >> hard to implement? >> When it comes to calling third-party bash scripts - not being able to >> show its output is quite limiting when implementing any deployment process >> (some legacy scripts run 1-2 hours for example giving lot of output which >> can't be returned as json) >> >> >> On Tuesday, November 13, 2012 7:14:22 PM UTC+3, Michael DeHaan wrote: >>> >>> It's currently not possible. The closest thing we have is the way >>> async can poll in a playbook. It may be possible to fiddle with >>> async_wrapper >>> to get it to do something like this. It will probably have to pass >>> in some additional flags over to the async command or feed them to >>> async_wrapper >>> somehow. >>> >>> I will warn you that the async code is not trivial and has warped my >>> brain on many occasions. However, I think this may make it more fun >>> to work on :) >>> >>> --Michael >>> >>> On Tue, Nov 13, 2012 at 10:52 AM, Yun Zheng Hu <[email protected]> >>> wrote: >>> > Is it possible to follow the stdout/stderr output as it comes in? >>> Instead >>> > for waiting for the command to finish I want to see the output as it >>> comes >>> > in (preferably line buffered). >>> > >>> > For instance, grepping for something in a large log file or on several >>> > machines or maybe even tail -f a log file. >>> > If it's currently not possible I would be interested to add this >>> feature >>> > myself :) >>> > >>> > Regards, >>> > Yun >>> > >>> > -- >>> > >>> > >>> >> -- >> You received this message because you are subscribed to the Google Groups >> "Ansible Project" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] <javascript:>. >> For more options, visit https://groups.google.com/groups/opt_out. >> >> >> > > > > -- > Michael DeHaan <[email protected] <javascript:>> > CTO, AnsibleWorks, Inc. > http://www.ansibleworks.com/ > > -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/953edad5-1063-434d-b0bc-918ab06acb73%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
