We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Describe the bug The log printed by ScpFileFrom seems to be inaccurate.
It says: Running command /usr/bin/scp -t <DIR> but from examining the source code in practice it runs sudo dd if=<FILE>.
Running command /usr/bin/scp -t <DIR>
sudo dd if=<FILE>
My speculation is that maybe the code evolved at some point to support sudo and thus doesn't actually use scp any more?
To Reproduce Call ssh.ScpFileFrom on an accessible remote host and observe the log output.
ssh.ScpFileFrom(t, sshHost, "path/to/remote/file", kubeConf, useSudo)
Expected behavior The logs should accurately reflect what is happening.
Versions
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
Describe the bug
The log printed by ScpFileFrom seems to be inaccurate.
It says:
Running command /usr/bin/scp -t <DIR>but from examining the source code in practice it runssudo dd if=<FILE>.My speculation is that maybe the code evolved at some point to support sudo and thus doesn't actually use scp any more?
To Reproduce
Call ssh.ScpFileFrom on an accessible remote host and observe the log output.
Expected behavior
The logs should accurately reflect what is happening.
Versions
The text was updated successfully, but these errors were encountered: