This is a follow up on a previous request to make SSH, Rsync and SFTP action more flexible:
I have the need to use a jump host and some other “advanced” SSH options not available right now.
For this is would be really useful to have more control over the SSH, rsync and sftp actions.
I need to be able to set a ~/.ssh/config file and activate the ForwardAgent that is used with the SSH commands. With that forward agent, and settings it would be possible to use the ProxyJump option in SSH and rsync.
I would expect that with the following config and setting the hostname to “some-server” I will be logging into the server “some-server” via the jumpserver.
ForwardAgent yes Host jumpserver Hostname 90.XX.XX.XXX User test ControlPersist 3600 Host some-server ProxyJump jumpserver HostName 192.168.1.2
But i get this error:
Resolving host some-server... Resolving host some-server - Failed Server response: DefaultConnectFuture[user@some-server:22]: Failed (UnresolvedAddressException) to execute: null
This all suggest that the SSH client is not using the .ssh/config from ~ or the working directory as suggested in: https://buddy.works/docs/pipelines/ssh-keys
A solution would be to be able to create the .ssh/config file and start the ssh agent before running the SSH/rsync/sftp commands/actions. One extra nice options would be to load multiple keys in that agent before running the action(s).
And as always, thanks for the great product!