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

Opening / connecting to existing tunnels from my extension

Open Simon-Count opened this issue 1 year ago • 2 comments

Trying to connect to an existing remote tunnel from my extension. I already know that GitHub was used to create & authorize the tunnel and I know the tunnel id, because my extension initialised the tunnel.

Does executeCommand('remote-tunnels.connectCurrentWindowToTunnel', args?) take any input args so that I can skip asking the user again for things I already know?

Currently my users have to manually go through this flow again of 1. image 2. image

Even though I know exactly which remote tunnel they are trying to connect to as my web view consist of a list of available remote environments they can initialise tunnels or connect to existing tunnels.
image

Simon-Count avatar May 27 '24 10:05 Simon-Count

I am interested in finding a solution to this issue. I haven't found any solutions online, so perhaps this should be submitted as a feature request.

I found a Stack Overflow question asking if there is a URI scheme for tunnels: Stack Overflow question link.

If such a scheme exists, could we open that remote tunnel using vscode.openFolder() with that URI as an argument?

image

Datata1 avatar Jun 16 '24 17:06 Datata1

@chrmarti or anyone from the remote tunnels team able to provide the parameter structure for these calls?

Simon-Count avatar Jun 17 '24 06:06 Simon-Count