2.3.0
Changes
SSHClient
now starts buffering output from remote host, both standard output and standard error, when a command is run.SSHClient.read_output
,SSHClient.read_stderr
and iterating on stdout/stderr fromHostOutput
now read from the internal buffer rather than the SSH channel directly.ParallelSSHClient.join
no longer requiresconsume_output
to be set in order to get exit codes without first reading output.ParallelSSHClient.join
with timeout no longer consumes output by default. It is now possible to usejoin
with a timeout and capture output afterjoin
completes.ParallelSSHClient.reset_output_generators
is now a no-op and no longer required to be called after timeouts.HostOutput.stdout
andstderr
are now dynamic properties.- Added
HostOutput.read_timeout
attribute. Can be used to see what read timeout was whenrun_command
was called and to change timeout when next reading fromHostOutput.stdout
andstderr
. - Added
HostOutput.encoding
attribute for encoding used whenrun_command
was called. Encoding can now be changed for when next reading output. ParallelSSHClient.join
with timeout no longer affectsstdout
orstderr
read timeout set whenrun_command
was called.- LibSSH clients under
pssh.clients.ssh
now allow output to be read as it becomes available without waiting for remote command to finish first. - Reading from output behaviour is now consistent across all client types - parallel and single clients under both
pssh.clients.native
andpssh.clients.ssh
. ParallelSSHClient.join
can now be called without arguments and defaults to last ran commands.ParallelSSHClient.finished
can now be called without arguments and defaults to last ran commands.
This is now possible:
output = client.run_command(<..>)
client.join(output)
assert output[0].exit_code is not None
As is this:
client.run_command(<..>, timeout=1)
client.join(output, timeout=1)
for line in output[0].stdout:
print(line)
Output can be read after and has separate timeout from join.