pyinfra turns Python code into shell commands and runs them on your servers. Execute ad-hoc commands and write declarative operations. Target SSH servers, local machine and Docker containers. Fast and scales from one server to thousands.
One can use files.put as with regular sftp or other unix commands mv, cp, which allow to ommit file name if the path is directory.
Meta
Include output of pyinfra --support.
oz123@server:~/nesuss-agents$ ./venv/bin/pyinfra --support
--> Support information:
If you are having issues with pyinfra or wish to make feature requests, please
check out the GitHub issues at https://github.com/Fizzadar/pyinfra/issues .
When adding an issue, be sure to include the following:
System: Linux
Platform: Linux-4.4.0-18362-Microsoft-x86_64-with-glibc2.29
Release: 4.4.0-18362-Microsoft
Machine: x86_64
pyinfra: v1.4.14
Executable: ./venv/bin/pyinfra
Python: 3.8.10 (CPython, GCC 9.4.0)
oz123@server:~/nesuss-agents$
+ How was pyinfra installed (source/pip)?
```pip3 install pyinfra```
The issue is actually not with pyinfra, rather with paramiko (I have 2.7.2) see here https://github.com/paramiko/paramiko/issues/1000.
Describe the bug
Using
files.put
as:Results in the following error:
Which is pretty cryptic...
To Reproduce
Use as above.
Expected behavior
One can use
files.put
as with regularsftp
or other unix commandsmv
,cp
, which allow to ommit file name if the path is directory.Meta
Include output of
pyinfra --support
.