SshConfig | An SSH config parser library with a fancy API

Keep doing the same steps but instead of sql.Open use

This is impossible; you must use owned data instead of references.

Here's a minimal example:

That seems similar to golang/go/issue 31401 (which then refers to issue 32453: " x/crypto/ssh: semantics around running session.Wait() after calling session.Run(), when EOF messages are sent")

The error is returned because the session has already been closed (by Run()).
The SSH connection leaks because it is never closed — the client object returned from Dial() is discarded, but that's the object that needs to be closed to clean up the underlying TCP connection.

As an aside, this seems to be a subtle API to use correctly.
The session can be closed asynchronously at any time by the other side, and so it's always possible for correctly-written code to get an EOF from Close()

So you might want to test for that particular error, and ignore it in your defer function.

sftp.list returns a promise so you need to await it before using it. Something like this should work

It really does not make sense to add the tunneling function into your code. A simple wrapper shell script prevents you from the necessity to reinvent the wheel:

Use the reflect package to set a field by name:

As the error message states, you need to set user.email and user.name git configs. This information is stored in the commit, git does not work without them.

my sshconfig and keys are correctly configured

This is irrelevant, ssh keys are used when you are pushing existing commits to some remote, not when creating new commits.

for mysql/aurora there custom Ip address if your script running locally on that EC@ then you will be able make connection.

Add one rule with anywhere access and try it. for mysql

You cannot make Paramiko use oursshbinary as an SSH implementation. You cannot even make it use ssh.

Paramiko is ssh itself.

It's same (as you know now), as if you wanted ssh use oursshbinary (it makes no sense). You would have to make Paramiko do what oursshbinary does. But we do not know what oursshbinary does, comparing to ssh.

Response to the previous version of your question:

The -S switch of OpenSSH ssh client creates a connection sharing that can be reused by other instances of ssh or other OpenSSH tools (like sftp).

Paramiko does not support connection sharing. It makes no sense for it to do actually.

Connection sharing makes sense for tools/applications. One instance of a tool creates a connection and other instances of the same or different tool can reuse the connection.

But you do not need that in a script/when programming. You have your SSH session instance. You can use it for multiple purposes throughout your script/program. In other words, you can share your instance.

Specifically, with SSH, the OpenSSH connection sharing opens separate SSH channel for the sharing client. With Paramiko, you can open multiple separated channels over the same SSH connection as well. This is what methods like Transport.open_sftp_client (or SSHClient.open_sftp), Transport.open_session (SSHClient.invoke_shell, SSHClient.exec_command) do. They all internally call Transport.open_channel. You can call all these as many times as you need, for a single SSH session.