I usually use -n in SSH commands when doing any kind of host management, to make it safer to deal with stdin in the surrounding shell script. But sometime in the last few months deploy-rs seems to have stopped working because of this, and I get a result like this:
$ deploy --debug-logs --boot --skip-checks --ssh-opts="-n -o BatchMode=yes -o ConnectTimeout=10" .#some-hostname
[…]
🚀 ℹ️ [deploy] [INFO] Copying profile `system` to node `some-hostname`
error: unexpected end-of-file
error: cannot connect to '10.62.87.26'
🚀 ❌ [deploy] [ERROR] Failed to push profile to node some-hostname: some-hostname
Do recent versions of deploy-rs use stdin for pushing the profile? If so, it might be worth a quick caveat in the docs.
I usually use
-nin SSH commands when doing any kind of host management, to make it safer to deal with stdin in the surrounding shell script. But sometime in the last few months deploy-rs seems to have stopped working because of this, and I get a result like this:Do recent versions of deploy-rs use stdin for pushing the profile? If so, it might be worth a quick caveat in the docs.