Hi Abhijeet,
Please check out the upgrading page for all details like this! It is very
thorough (both a blessing and a curse). Specifically, search it for
'output_prefix' which was the name of the old setting controlling that
behavior.
http://docs.fabfile.org/en/latest/upgrading.html
Spoiler: this is one of the larger missing pieces that we'll be working to
figure out in the near term. It may end up being line-by-line prefixes
again, possibly via a logging module; or we might come up with something
else. Suggestions welcome!
Thanks,
Jeff
On Tue, May 15, 2018 at 1:14 AM, Abhijeet Rastogi <abhijeet.1...@gmail.com>
wrote:
> Hi everyone,
>
> I have a use-case where I can't use the Fabric command directly. I run my
> tasks as:-
>
> from fabric import ThreadingGroup as Group
> from fabric.exceptions import GroupException
>
> hosts = ['web1', 'web2', 'web3']
> g = Group(*hosts)
>
> results = g.run('date')
>
> Now, as I don't use "hide=both" with the "g.run" function call, the stdout
> of the command is printed in the terminal directly.
>
> How do I prepend the output with the "fabric.connection.Connection" it's
> associated with, in a streaming way. I know, I can collect the output with
> the "results" that is returned but I want to do that in a streaming way and
> not after all commands are finished executing. (just like it happened with
> the older fabric.api.execute 1.0 version API)
>
> --
> Cheers,
> Abhijeet Rastogi (shadyabhi)
>
> _______________________________________________
> Fab-user mailing list
> Fab-user@nongnu.org
> https://lists.nongnu.org/mailman/listinfo/fab-user
>
>
--
Jeff Forcier
Unix sysadmin; Python engineer
http://bitprophet.org
_______________________________________________
Fab-user mailing list
Fab-user@nongnu.org
https://lists.nongnu.org/mailman/listinfo/fab-user
