Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ability to import/show hosts configured in ~/.ssh/config #12981

Closed
mrtnd opened this issue Apr 26, 2022 · 3 comments
Closed

ability to import/show hosts configured in ~/.ssh/config #12981

mrtnd opened this issue Apr 26, 2022 · 3 comments
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@mrtnd
Copy link

mrtnd commented Apr 26, 2022

Description of the new feature/enhancement

It would be very handy to be able to import the hosts configured in ~/.ssh/config file as profiles. Or to be imported automatically if it detected that there are hosts configured. I have couple servers where i do remote development on, using vscode. And vscode is using the ~/.ssh/config file for the hosts. Which is very handy. Sometime i only need a terminal. But since Windows Terminal is using its own settigns.json file i need to maintain two different config files for my hosts, which is a little inconvenient.

Proposed technical implementation details (optional)

Maybe a switch in the settings that would scan ~/.ssh/config and import hosts if any are configured. Something like:
"importHostsFromSSHConfigFile": true/false,

@mrtnd mrtnd added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label Apr 26, 2022
@ghost ghost added Needs-Tag-Fix Doesn't match tag requirements Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting labels Apr 26, 2022
@zadjii-msft
Copy link
Member

Thanks for the suggestion! This is actually already being tracked by another issue on our repo - please refer to #9031 for more discussion.

/dup #9031

@ghost
Copy link

ghost commented Apr 26, 2022

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost ghost added Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. and removed Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Apr 26, 2022
@mrtnd
Copy link
Author

mrtnd commented Apr 26, 2022

Thanks for the suggestion! This is actually already being tracked by another issue on our repo - please refer to #9031 for more discussion.

/dup #9031

Hi Thank for the reply. I was searching for an similar issue, but for some reason did not find it... That's why I opened a new one. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.
Projects
None yet
Development

No branches or pull requests

2 participants