- Allow flexibility in the Paramiko dependency version
- Added context managers to both
SSHSession
andSSHSessionManager
- Added multi-threading to
SSHSessionManager.upload_file()
- Added the
should_make_missing_directories
parameter toSSHSessionManager.upload_file()
- Note: v0.3.2 has breaking changes
get_command_output_information_dictionary()
has been renamed toget_command_output_dictionary()
- Some documentation added
- General package / repository cleanup
- Note: v0.3.1 has breaking changes
- Removed cached ping methods - these never really made much sense
- Swapped out custom ping method for ping3, which allows us to
provide a
timeout_in_seconds
parameter to ping methods
- Added ping methods to
SSHSession
andSSHSessionManager
- Note: v0.2.0 has breaking changes
- The
SSHSessionManager
now spins up a separate thread for eachSSHSession
, a change needed to fix the previous strange requirement of having to call aprint_command_output()
in order to keep theSSHSession
from exiting before the command finished. This function no longer exists, blocking happens automatically, and printing out output is set via an input parameter to bothrun_commands_in_all_ssh_sessions()
andrun_command_in_ssh_session()
. SSHSession
s now store standard output, standard error, and the command exit codeSSHSession
no longer provides the ability to capture specific output. Since all output is now captured and saved, it is up to the user to search through it to find what they need.- Removed some code, marked some items as "private" via
__
. - Some functions have been renamed
SSHSession
no longer takes in asession_description
variable in the__init__()
- NOTE: v0.1.0 has breaking changes
- Implemented a system to hold the output of all commands ran on a session. The
SSHSessionManager
holds a dictionary that maps anSSHSession
object to an internal dictionary. This internal dictionary maps theCommand
object to the captured output message. Output is no longer stored in theCommand
objects. - The internal dictionary that holds the captured output, as mentioned above, will now also capture the exit code for the command that ran as well. Execution is now blocked on both the captured output and the exit code of the command, so that the session will not end until both of these are captured (unless the user doesn't request any output to be captured, then execution blocking will only happen on the exit code).
- Added print statements for some errors that were previously being omitted from output.
- Small documentation / repository changes
- Initial release