[Remote-SSH Bug]: Includes not appearing in remote hosts list on Windows (still/again?)

[mboeker]

Is there an existing issue for this bug?

• I have searched the existing issues

Required Troubleshooting Steps

• I have followed these troubleshooting steps
• I have tried both values of the remote.SSH.useLocalServer setting

Connect Locally

It doesn’t connect successfully (different error message)

->

This seems to match #65 which is closed, but part of the issue is not resolved, at least not on Windows.

I have several lists of hosts in separate files. For regular ssh to work I have this in my .ssh/config:

Host *
  IdentityFile ~/.ssh/id_rsa
  UserKnownHostsFile /dev/null
  StrictHostKeyChecking no
  ServerAliveInterval 300
  TCPKeepAlive yes

Include ~/.ssh/my_vms

Because VSC doesn't support / or ~, I have this in my .ssh/config-vs:

Host *
  IdentityFile C:\Users\myuser\.ssh\id_rsa
  UserKnownHostsFile NUL
  StrictHostKeyChecking no
  ServerAliveInterval 300
  TCPKeepAlive yes

Include C:\Users\myuser\.ssh\my_vms

I also tried Include my_vms. Neither of those includes makes the list of targets appear in the remote hosts list. They only appear if I place them directly into config-vs. This is annoying because it means maintaining two lists, one for VSC and one for everything else.

Expected Behavior

.ssh/config should support "Include" and the list of targets should appear in the remote host list, just like it does if all the hosts are specified directly in the config file.

Steps To Reproduce

Windows 11, VSC 1.90

Remote-SSH Log

Does not apply

Anything else?

No response

[FrancoTampieri]

I confirm the issue still on macOS too (Sonoma 14.6.1)

[joshspicer]

The main ask i'm seeing here is to support Include, which is why i'm adding the feature-request tag. Are you also reporting a bug for the Host * config block?

[vs-code-engineering]

This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 10 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation.

Happy Coding!

[vs-code-engineering]

This feature request has not yet received the 10 community upvotes it takes to make to our backlog. 10 days to go. To learn more about how we handle feature requests, please see our documentation.

Happy Coding

[vs-code-engineering]

🙁 In the last 60 days, this feature request has received less than 10 community upvotes and we closed it. Still a big Thank You to you for taking the time to create this issue! To learn more about how we handle feature requests, please see our documentation.

Happy Coding!