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 group profiles #15721

Closed
chadleywilson opened this issue Jul 18, 2023 · 3 comments
Closed

Ability to group profiles #15721

chadleywilson opened this issue Jul 18, 2023 · 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

@chadleywilson
Copy link

I am not sure if this can already be done, but I could not find the correct search term for it, and apologise in advance if need be.

I have a lot of connection profiles (200+), MS Terminal makes it so much easier to manage them, but could use refinement, scrolling through the list can waste time some days.

Most of my connections are are ssh connections to docker swarms or kubernetes clusters. see my example below.

It would be nice if I could group my connections by cluster or server purpose them and have "sub menus" to better organise these.

Proposed technical implementation details (optional)

Here is sort of a summarized example, a typical cluster would have about 7 servers minimum. This is 3 server cluster example actually names changed and guids probably nonsense as I changed them slightly for the demonstration here , I was thinking something along these lines to group them.

       {
           "groupNameorTag": "Cluster A"
           "Description": "all Cluster A masters and nodes"
         {
                "colorScheme": "Raspberry",
                "commandline": "ssh ubuntu@mst-01",
                "guid": "{4268914b-3bba-5c19-be6f-42893bc5a277}",
                "hidden": false,
                "icon": "C:\\Scripts\\windows-terminal-icons\\icons\\ubuntu.png",
                "name": "ssh mst-01",
                "tabTitle": "mst-01"
            }'
             {
                "colorScheme": "Raspberry",
                "commandline": "ssh ubuntu@node-01",
                "guid": "{4268914b-3bba-5c19-be6f-42893bc5a278}",
                "hidden": false,
                "icon": "C:\\Scripts\\windows-terminal-icons\\icons\\ubuntu.png",
                "name": "ssh node-01",
                "tabTitle": "node-01"
            }'
             {
                "colorScheme": "Raspberry",
                "commandline": "ssh ubuntu@node-0",
                "guid": "{4268914b-3bba-5c19-be6f-42893bc5a279}",
                "hidden": false,
                "icon": "C:\\Scripts\\windows-terminal-icons\\icons\\ubuntu.png",
                "name": "ssh node-02",
                "tabTitle": "node-02"
            }
        }

When you click the drop down arrow, instead of only seeing PowerShell/ cmd / azure cloud shell / PowerShell 7 standard profiles, I would like to be able to have sub menus for docker swarms and Kubernetes clusters and categorize some of the stand alone servers that I connect to on a daily basis.

I have shortened and redacted version attached as a pic, which I took from a older user profile, but it should be enough illustrate what my colleagues and I use on a daily basis.

image

@chadleywilson chadleywilson added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label Jul 18, 2023
@microsoft-github-policy-service microsoft-github-policy-service bot added the Needs-Tag-Fix Doesn't match tag requirements label Jul 18, 2023
@zadjii-msft
Copy link
Member

quick note: we introduced newTabMenu in 1.17. See #1571. There's no docs for it yet though 😢

I'll make a longer reply later

@zadjii-msft
Copy link
Member

Alright, we've got a docs PR out now: MicrosoftDocs/terminal#692

technically, this is a /dup of #1571, so I'll close it as such.

Thanks for giving me the impetus to finally document that!

@zadjii-msft zadjii-msft closed this as not planned Won't fix, can't repro, duplicate, stale Jul 19, 2023
@microsoft-github-policy-service
Copy link
Contributor

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!

@microsoft-github-policy-service microsoft-github-policy-service bot added Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. and removed Needs-Tag-Fix Doesn't match tag requirements labels Jul 19, 2023
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