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

Session management support #17622

Closed
willzhang opened this issue Jul 28, 2024 · 3 comments
Closed

Session management support #17622

willzhang opened this issue Jul 28, 2024 · 3 comments
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something 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 No-Recent-Activity This issue/PR is going stale and may be auto-closed without further activity.

Comments

@willzhang
Copy link

Description of the new feature/enhancement

Proposed technical implementation details (optional)

Is it possible to support saving historical session connections, because if there are dozens of sessions, it would be very time consuming to manually enter the address each time to connect remotely.

like this:
image

@willzhang willzhang added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label Jul 28, 2024
@microsoft-github-policy-service microsoft-github-policy-service bot 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 Jul 28, 2024
@lhecker
Copy link
Member

lhecker commented Jul 29, 2024

Is there a reason why your shell's command history is insufficient for this?

@zadjii-msft
Copy link
Member

You can always make profiles for each of these. You can then also group them into folders in the newTabMenu.

There is the "auto-detect profiles from .ssh/config" feature (#9031), which never got finished (#15007). But that would auto-generate profiles from the hosts in .ssh/config.

Or I suppose in 1.22 you could add a .wt.json file to your %userprofile% that's got a snippet for each connection. So you could have something like:

{
    "$version": "1.0.0",
    "snippets":
    [
        {
            "input": "ssh 192.168.0.1",
            "name": "my thing",
            "description": "ssh to my thing"
        },
        {
            "input": "ssh 192.168.0.2",
            "name": "another one",
            "description": "you get the picture"
        },
    ]
}

(previous discussion: #13327)

@zadjii-msft zadjii-msft added the Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something label Jul 29, 2024
Copy link
Contributor

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

@microsoft-github-policy-service microsoft-github-policy-service bot added the No-Recent-Activity This issue/PR is going stale and may be auto-closed without further activity. label Aug 2, 2024
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. Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something 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 No-Recent-Activity This issue/PR is going stale and may be auto-closed without further activity.
Projects
None yet
Development

No branches or pull requests

3 participants