Nick Mills-Barrett

> However, it is not inconceivable to think of a case where you need the stdout of a command that has just run, and there being no way to infer...

@romanchyla I really like this idea and have considered it in the past but never implemented. This could even become the recommended way of writing and executing pyinfra code entirely....

🤦 had not tested the operations with `Path` objects. I've added tests for non-string `StringCommand` bits in https://github.com/Fizzadar/pyinfra/commit/2e4053f28f278e873499f6b716f20e4900dbcd1c and handled them in https://github.com/Fizzadar/pyinfra/commit/b91281e9e00106e4c1860b0209aa3bd8abf0ee19. I have just released this in `v1.4.7`...

This should now be handled properly in https://github.com/Fizzadar/pyinfra/commit/48d6ff7e445856fdc20e971536872dbfcdcf5f4c - `Path` objects should absolutely be supported IMO but the string conversion wasn't in the right place. Have confirmed this is now...

@blarghmatey agreed - the commit fixes unrelated issues but I definitely jumped the gun a bit here! Would be great to chat real-time about this and understand the issue better...

The `@dockerssh` connector implements this kind of thing, but it's not a composable combination of `@ssh` and `@docker` connectors (which would be awesome to have).

This was documented in the README here: https://github.com/Fizzadar/pyinfra/blob/current/CHANGELOG.md#v15. I do need to expand the documentation pages for this though as config is largely ignored.

Hi @phlummox thank you for raising this, will definitely add to the contributing doc ASAP! Also thank you for the changes to show the output; this is actually very similar...

`host.name` should achieve this for you @jmpolom! Will keep this open as a docs issue 👍

One option here is to use the `ENV` config var which would apply to all operations within a deploy; ie: ```py # config.py ENV = { "HOMBREW_DEVELOPER": 1, } #...