v2.19.1 - coder config-ssh deletes entire config
We recently had our Coder server updated to 2.19.1 and upon running
coder config-ssh it just deletes the entire Coder list of sites from the ~/.ssh/config, so can no longer connect to any workspace in VS Code or PHP Storm.
On macOS, and I've tried removing the CLI, reinstalling the CLI, and using coder login to authenticate again.7 Replies
<#1351653284766683276>
Category
Help needed
Product
Coder (v2)
Platform
macOS
Logs
Please post any relevant logs/error messages.
If I hit the "PhpStorm" button in the backend for anyworkspace, it says
The workspace "example"does not have an agenc named "example" where example is the name of my workspaceHi @xan this is a breaking change for how we create and use our config-ssh but our VS Code extension is able to handle this and will provide you the same experience.
Are you not abel to use Coder's VS Code extension?
Not in my current set up, and this breaks a few automations and tools we relied on that read from our ssh config 😦
I posted a feature request in GitHub about maybe possibly filling out the ssh config still with something like
coder config-ssh --no-wildcard
Tinkerwell is a PHP tool that lets you quickly select connections from your ssh config for managing remote PHP environments. Tabby is a popular macOS terminal that had a panel that listed all of your ssh config connections. These tools and then all of our own automations relied on the way Coder was doing it before which provided a sort of universal compatibility with other dev tools.
When creating/destroying tons of workspaces, it's not a lot more painful to manually edit the connection list in so many tools. I could see if I only worked in a few workspaces but my list of workspaces changes frequently and is very large lolThnaks @xan Can we keep this conversation on GitHub . I think it will help us raech more users and decide how many more are impcated.
closing this as it looks like expected behavior of the new wildcard changes to me
@Phorcys closed the thread.