Is your feature request related to a problem?
Add configuration for using a relative path in the IdentityFile config written into .ssh/config. Currently full paths are written to the config file
Example .ssh/config generated via DevSpace
# DevSpace Start backend.bun-minimal.devspace
Host backend.bun-minimal.devspace
HostName localhost
LogLevel error
Port 10118
IdentityFile "/home/acelinkio/.devspace/ssh/id_devspace_ecdsa"
StrictHostKeyChecking no
UserKnownHostsFile /dev/null
User devspace
# DevSpace End backend.bun-minimal.devspace
Which solution do you suggest?
Allow a configuration parameter to set the IdentityFile to use a relative path ~/.devspace/ssh/id_devspace_ecdsa
If this used a relative path, I could symlink my .ssh/config file and .devspace directory. Then I could natively use Windows VSCode to remote in.
Which alternative solutions exist?
A lot of ducktape a bunch of glue together. See below.
Additional context
Using Windows+WSL+VSCode+DevSpaces is a bit of a pain.
Windows is running VSCode. VSCode remotes into my WSL instance for a majority of things. Then I am using DevSpaces in WSL to create remote development containers inside of my Kubernetes cluster. DevSpaces can be configured to setup a remote ssh server inside of the pod and saves the credentials locally in wsl. Here is the workaround I have to do to get everything functioning.
- For ease of use, I symlink my
~/.ssh/config in WSL to Windows host path ~/.ssh/config
- Set VSCode SSH Extension setting
Remote.SSH: Path to the full path to ssh-helper.bat
ssh-helper.bat content
C:\Windows\system32\wsl.exe ssh %*
Is your feature request related to a problem?
Add configuration for using a relative path in the IdentityFile config written into
.ssh/config. Currently full paths are written to the config fileExample .ssh/config generated via DevSpace
Which solution do you suggest?
Allow a configuration parameter to set the IdentityFile to use a relative path
~/.devspace/ssh/id_devspace_ecdsaIf this used a relative path, I could symlink my
.ssh/configfile and.devspacedirectory. Then I could natively use Windows VSCode to remote in.Which alternative solutions exist?
A lot of ducktape a bunch of glue together. See below.
Additional context
Using Windows+WSL+VSCode+DevSpaces is a bit of a pain.
Windows is running VSCode. VSCode remotes into my WSL instance for a majority of things. Then I am using DevSpaces in WSL to create remote development containers inside of my Kubernetes cluster. DevSpaces can be configured to setup a remote ssh server inside of the pod and saves the credentials locally in wsl. Here is the workaround I have to do to get everything functioning.
~/.ssh/configin WSL to Windows host path~/.ssh/configRemote.SSH: Pathto the full path tossh-helper.batssh-helper.batcontentRemote.SSH: Enable enableDynamicForwardingto off.Remote.SSH: Local Server Downloadto off. (This is because SCP cannot be configured like with the ssh-helper.bat Allow configuring SCP similar toRemote.SSH: Pathsetting microsoft/vscode-remote-release#11382)