vscode-remote-release icon indicating copy to clipboard operation
vscode-remote-release copied to clipboard

Allow arbitrary commands to create SSH sessions to hosts with unknown IPs

Open sebastian-correa opened this issue 1 year ago • 1 comments

First off, thanks for this great extension! I use this almost on the daily to SSH into remote hosts from VSCode.

I tried asking in SO first [ref] and got no response and, given the error I get, I think my question is more of a feature request.

A usual workflow my peers and I use is spinning up a GCE/EC2 instance when I start to work and down when I'm done for the day. I use VSCode to connect via SSH to the instance but, for this to work, I have to grab its public IP (by hand) and change my .ssh/config file manually for this to pop up in VSCode. I want to avoid needing to grab the IP manually.

I can directly SSH from my terminal into the instance with this command for the GCP case: gcloud compute ssh --zone=<zone> --ssh-key-file=~/.ssh/<key-file> <username>@<instance-name> --project=<project-id> -- -A", which works and doesn't require me to go get the IP. However, adding a new connection via VSCode's UI with this command results in an Unknown flag zone error.

This looks like VSCode is only expecting ssh command flags and doesn't directly run the command I give. Is it possible to support the use case I proposed by allowing arbitrary commands?

sebastian-correa avatar Feb 13 '24 20:02 sebastian-correa

Changed the title because the original title made it seem like the IP could change at any time, which could mean calling the command every so often, which is not what I want. The IP is static until I manually switch of the machine, at which point I expect to reconnect manually using VSCode.

sebastian-correa avatar Feb 13 '24 20:02 sebastian-correa

Do I need to do anything else so this issue gets some attention? Maybe I missed something, as the Triage Bot did something with it.

sebastian-correa avatar Feb 29 '24 17:02 sebastian-correa

Can someone lend a hand? Maybe I did something wrong, or maybe this was internally marked as low priority. @chrmarti @connor4312?

sebastian-correa avatar Mar 14 '24 12:03 sebastian-correa

This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 10 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation.

Happy Coding!

vscodenpa avatar Apr 05 '24 00:04 vscodenpa

This feature request has not yet received the 10 community upvotes it takes to make to our backlog. 10 days to go. To learn more about how we handle feature requests, please see our documentation.

Happy Coding

vscodenpa avatar May 25 '24 02:05 vscodenpa

:slightly_frowning_face: In the last 60 days, this feature request has received less than 10 community upvotes and we closed it. Still a big Thank You to you for taking the time to create this issue! To learn more about how we handle feature requests, please see our documentation.

Happy Coding!

vscodenpa avatar Jun 04 '24 02:06 vscodenpa