Feature Request: connections via ssh jumphosts

[cepal]

many people don't have direct connection to the serves they want to work on, instead they need to SSH to a jump host, change to a role, and then SSH further on; this is automatable by various methods using traditional SSH clients, but not a chance in Snowflake. What's more, I am not interested in accessing files or list system services on my jump host, but rather I am after these useful built-in features for the destination server - that but could only be achievable if the SSH "jumping" was incorporated in the Snowflake client - as the client needs to be "aware" of the SSH jump and provide the tools not for the jump host, but for the target host (and be able to switch user along the way on the jump host)...

Such a connection would require following fields:
jumphost hostname, port, user/pw or ssh key
jumphost sudo role
target hostname, port (ssh key from jump host is presumed to be used for authentication)

Of course, it would be nice to be able to aggregate multiple target profiles to one jump host's profile in some sort of a tree profile structure, to make the profile tree nicer and easier to navigate through.

Solution of running Snowflake on the jump host and displaying it into my computer's X server is not available to me, though that would be the easiest way indeed. Also, i want to be able to copy filed between my workstation and the target server directly, not by first pushing or pulling them to the jump host.

[mpictor]

Sounds like our bastion servers are a bit different than your jump server. For us there's no changing roles, as that's all determined by the ssh certificate. So that'd need to be optional.

If ssh certs aren't yet supported, that'd be necessary for me. And it'd be nice to have an option to view the cert expiration, and to warn if expiration is approaching.

[eugenov]

Definitely need openssh's ProxyJump here!

[a1ad]

It's just useless without.