Skip to content

A flag to NOT use a wildcard in the ssh config #17153

@bpmct

Description

@bpmct

Discussed in #16990

Originally posted by octoxan March 18, 2025
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.

Phases

  • Phase 1: Just change coder config-ssh
  • Phase 2: Add VS Code Setting
  • Phase 3: Add JetBrains Toolbox Setting

Metadata

Metadata

Assignees

No one assigned

    Labels

    cliArea: CLI

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions