winrm limitations

Open potchin opened this issue 7 years ago • 1 comments

Not sure if this is a bug or something which has not yet been implemented yet. If the latter it should probably be documented.

I just tried to call a host.file(filename).exists against a windows machine and it failed when it tried to call uname which will obviously fail..

INFO:testinfra:RUN CommandResult(command=u'uname -s', exit_status=1, stdout=None, stderr="'uname' is not recognized as an internal or external command,\r\noperable program or batch file.\r\n")

Which methods are supported when using the winrm backend?

May 31 '18 08:05 potchin

Hello, Indeed, for now the support on windows is limited to running commands with run(), check_output().

I think file module could work if someone write a windows compatible module.

May 31 '18 10:05 philpep