-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Overriddes VSCode config for SSH Config Location #10692
Comments
Hey there @Merith-TK, sorry to hear of your troubles. I believe the extension should not alter your SSH config anymore in the latest version. Could you please check what version you are using and try out the pre-release version if you are not currently using it? It should be as simple as clicking the button on the extension's page in VS Code. It should be released in the stable channel soon. |
After use settings remained the same (yay!) Relevant Output logs from SSH extension
|
@jeanp413 have we seen this issue yet with SSH Gateway? |
@Merith-TK could you try using an absolute path to your default ssh config file in the |
I am also seeing this issue as of today on my machine which is macOS Monterey. Even when I remove the gitpod-provided ssh config manually from settings, it just adds it back the next time I launch gitpod, which prevents me from using my local ssh config in other windows. |
@filiptronicek @jeanp413 maybe a simple fix would be to append the gitpod ssh configuration to |
I disabled |
@MilesCranmer you can try |
I'm closing it, please follow #10692 (comment). In the future it is going to become a default. |
Also, please see: https://www.gitpod.io/blog/vscode-desktop-ssh-updates For more information. |
Bug description
this literally changes the vscode global config for this to work, and it is quite annoying to have to switch it back every single time as I have workspaces on remote hardware that I need to be able to access quickly
Steps to reproduce
have
~/.ssh/config
set as your default config locallythen click "open in vscode" on gitpod,
Workspace affected
No response
Expected behavior
No response
Example repository
No response
Anything else?
It is very annoying and I believe there should be an way to not do this, or rather add an tempory config into the pre-defined
.ssh/config
that is then deleted after useThe text was updated successfully, but these errors were encountered: