microsoft / microsoft/vscode-remote-release
DevTunnels: Support SSH-Forwarded Tunnels with remoting
Nobody has claimed this yet.
- Dominant language
- Dockerfile
- Stars
- 4.2k
- Forks
- 469
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 1
Description
CC @connor4312
In VSCode, when remoting via Dev Tunnels to a code tunnel-hosted VSCode Server the devtunnels forwarding only allows for the https external devtunnels address. These often don't work for a lot of https applications, such as Ansible Automation Platform.
Meanwhile, the devtunnels CLI allows to connect to the same port via a localhost SSH forward
And this does work for these apps. So why is there not a toggle to allow me to choose between doing the localhost SSH port forward vs the hosted HTTPS option? The localhost SSH port forward has the additional benefit of not being publicly published (even if it is OAuth-protected)
Since I have devtunnel connect as a workaround, it's not a huge deal, but it would be really nice if this were natively integrated unless I'm missing a setting.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the existing Dev Tunnels forwarding used for remoting and compare it with the devtunnel connect localhost SSH-forward workflow described here. Done means remoting offers a supported localhost SSH-forward option alongside the hosted HTTPS address, with the behavior verified for the affected applications.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- vscode
- Domain
- devtools, networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100