(A) I would think it might mean to print (B) which might be fine if it ignored -v
(C) in which case I'd expect print: True to maybe print everything, and it also take a list of attributes? On Fri, Feb 14, 2014 at 1:36 PM, Jesse Keating <jkeat...@j2solutions.net>wrote: > On 2/13/14, 10:56 AM, Rumen Telbizov wrote: > >> Thanks for starting a discussion. >> >> Here is how I see a feature like this. >> How about if we introduce a new keyword called say "print: " similar to >> debug but being an auxiliary keyword rather than the main task. So with >> this you can control some extra output that comes after [changed] >> [servername] => "here's my custom output".If this print keyword exists >> in a task that has a loop then it will basically be printed on every >> iteration. >> > > At first glance, the print: thing seems reasonable and not too confusing. > > > -jlk > > > -- > 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 ansible-project+unsubscr...@googlegroups.com. > To post to this group, send email to ansible-project@googlegroups.com. > For more options, visit https://groups.google.com/groups/opt_out. > -- 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 ansible-project+unsubscr...@googlegroups.com. To post to this group, send email to ansible-project@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
