Skip to content

Finish the SSH profile generator #15007

@McLavish

Description

@McLavish

maintainer note: hijacking OP to put tasks in here

Originally tracked in #9031
Added in #14042

### Tasks
- [ ] https://github.com/MicrosoftDocs/terminal/issues/641
- [ ] Fix issues that @DHowett found in the parser
- [ ] Something about making the SUI UX easier to use, disable?

Windows Terminal version

1.17.1023

Windows build number

10.0.22621.1413

Other Software

OpenSSH_for_Windows_8.6p1
LibreSSL 3.4.3

Steps to reproduce

  1. Install Windows Terminal (Preview) through the Microsoft Store
  2. Install the OpenSSH client from Windows Optional Features
  3. Create a user OpenSSH config file under %userprofile%.ssh\config:
Host myhost  
    HostName something.domain.com  
    User myuser  
    IdentityFile "C:\Users\myuser\myfolder\id_rsa"
  1. (Optional) Add "disabledProfileSources" : [ ], to settings.json
  2. Open Windows Terminal (Preview)

Note: It appears adding "disabledProfileSources" : [ "Windows.Terminal.SSH" ], produces a Value not accepted warning in VsCode as it's not listed in the profiles schema DynamicProfileSource enum.
bug

Expected Behavior

Docs says that "Windows Terminal version 1.XX+ can dynamically generate profiles to connect to the SSH hosts within your OpenSSH config file"

Actual Behavior

Nothing happens

Metadata

Metadata

Assignees

No one assigned

    Labels

    Area-SettingsIssues related to settings and customizability, for console or terminalHelp WantedWe encourage anyone to jump in on these.In-PRThis issue has a related PRIssue-TaskIt's a feature request, but it doesn't really need a major design.Needs-Tag-FixDoesn't match tag requirementsProduct-TerminalThe new Windows Terminal.

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions