A flag to NOT use a wildcard in the ssh config #16990
Replies: 1 comment 5 replies
-
|
Hi @octoxan I would like to understand your case and suggest a possible alternative. I wonder why you voted for parsing ssh config instead of using coder CLI and API to get a workspace list? |
Beta Was this translation helpful? Give feedback.
-
|
I already had some existing tools and automations written that used our manual ssh/config entries, so when we switched to Coder they all just worked seamlessly already. By including them in the ssh config, any other tools that lists out your connections as options just work, and don't require an official Coder plugin built into everything. |
Beta Was this translation helpful? Give feedback.
-
|
I agree. Even with the wildcard entry in the config, most tools should be able to connect. So, the only issue I see here is getting a list of available workspaces, which you were parsing from the SSH config. Right? |
Beta Was this translation helpful? Give feedback.
-
|
Yeah, it just helped list them out in a bunch of tools like Tinkerwell, Tabby, our own automations, some database tools, etc. I frequently change between a lot of workspaces and having every workspace already show up in every tool as an option to connect to was very convenient. Now there is a lot more set up to just get started on any project sadly. What was nice about the old method is it provided universal compatibility with a lot of tools that just assume your frequent ssh connections have been added to your ssh/config. |
Beta Was this translation helpful? Give feedback.
-
|
Seems like every since this was switched, our Windows users can't connect with Jetbrains Gateway. On macOS I did finally get it to generate the |
Beta Was this translation helpful? Give feedback.
-
Could you file a separate bug report for this? We will look into it. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
This update breaks our workflow:
#16096
Can we get a flag to not use a wildcard and to add an entry for every workspace? This is blocking me from doing any work currently.
There are a handful of automations we have built that parse the config. As well as not wanting to rely on the VS Code Coder extension for every fresh VS Code install, since I have to fresh install it frequently for something unrelated, and now can't use the built in SSH sidebar.
Perhaps something like
coder config-ssh --no-wildcard? Not sure if that would be wild.Beta Was this translation helpful? Give feedback.
All reactions