I would like to request the addition of support for SSH ProxyCommand configuration in the Invoker desktop application. This feature would allow users to specify a ProxyCommand in the SSH configuration, enabling the use of intermediate proxy servers or jump hosts when connecting to remote hosts. The configuration could be read from the standard ~/.ssh/config file or set directly within the Invoker application settings.
As part of my workflow, I use devpod to manage devcontainers on a remote SSH host. This setup requires using ProxyCommand to route my SSH connections through an intermediary server. Currently, while I can SSH into the remote host manually using ProxyCommand, Invoker does not support this configuration, making it impossible to integrate it into my development environment.
Is this feature valuable for other users as well and why?
Yes, this feature is valuable for other users as it enhances connectivity for those working in restricted network environments, ensures compliance with organizational security policies, and provides a consistent SSH experience across tools. Additionally, it benefits developers using remote development setups like devpod for devcontainers, allowing for a more integrated and efficient workflow.
Feature Description
I would like to request the addition of support for SSH ProxyCommand configuration in the Invoker desktop application. This feature would allow users to specify a ProxyCommand in the SSH configuration, enabling the use of intermediate proxy servers or jump hosts when connecting to remote hosts. The configuration could be read from the standard ~/.ssh/config file or set directly within the Invoker application settings.
As part of my workflow, I use devpod to manage devcontainers on a remote SSH host. This setup requires using ProxyCommand to route my SSH connections through an intermediary server. Currently, while I can SSH into the remote host manually using ProxyCommand, Invoker does not support this configuration, making it impossible to integrate it into my development environment.
Is this feature valuable for other users as well and why?
Yes, this feature is valuable for other users as it enhances connectivity for those working in restricted network environments, ensures compliance with organizational security policies, and provides a consistent SSH experience across tools. Additionally, it benefits developers using remote development setups like devpod for devcontainers, allowing for a more integrated and efficient workflow.