-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
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
refactor: add sshClient function #23893
refactor: add sshClient function #23893
Conversation
@Luap99 as requested in |
7b20ef5
to
8e8582d
Compare
code looks ok to me, couple of questions. |
The ssh options needs some weird parameters like (the raw) uri and machine (insecure), so it is not enough with url and identity. The "secure" query parameter was removed in Podman v4.3, it is now replaced with the "machine" option parameter (InsecureIgnoreHostKey) I think that url.Parse will fail to add any url.Port that is not an integer, so the strconv.Atoi error probably can never happen? But since it is only a validation error and not a connection error, it cannot be wrapped in a ConnectError so that goes into function. Signed-off-by: Anders F Björklund <[email protected]>
8e8582d
to
837755e
Compare
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: afbjorklund, rhatdan The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
The ssh options needs some weird parameters like (the raw) uri and machine (insecure), so it is not enough with url and identity.
i.e. it is not the generic "ssh", but the containers/common "ssh"
The "secure" query parameter was removed in Podman v4.3, it is now replaced with the "machine" option parameter (InsecureIgnoreHostKey)
commit 280f5d8
I think that url.Parse will fail to add any url.Port that is not an integer, so the strconv.Atoi error probably can never happen?
But since it is only a validation error and not a connection error, it cannot be wrapped in a ConnectError so that goes into function.
Does this PR introduce a user-facing change?