-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Finish the SSH profile generator #15007
Comments
@McLavish the feature might not be enabled, yet. See details at; Lines 141 to 146 in b9248fa
You could enable it using a branding token and build the terminal. I use To my surprise clicking on that profile opened a SSH connection to a Pi4 box, no errors! |
@elsaco I guess you're right but then it shouldn't be listed as a feature in the windows terminal docs |
@McLavish I agree. There is already been an issue made to get this removed from the docs page which I've assigned myself too: MicrosoftDocs/terminal#641 Thanks for including the screenshot and link to the doc! |
You know what, good callout. We should remove this from the docs until we ship this. Clearly our docs need some love 😅 I'm gonna hijack your OP to track the rest of the work needed to get this across the finish line. |
Any chance this is working now ? |
Nope. The issue is still open. We haven't really had the time to loop back around on this one. We'd love the help if you're interested though! |
maintainer note: hijacking OP to put tasks in here
Originally tracked in #9031
Added in #14042
Tasks
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
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 enum.
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
The text was updated successfully, but these errors were encountered: