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

Allow to directly connect to PWSH in Azure Cloudshell bypassing bash #4987

Open
artisticcheese opened this issue Mar 18, 2020 · 1 comment
Open
Labels
Area-AzureShell Workitems pertaining to the Azure Cloud Shell connection. Issue-Task It's a feature request, but it doesn't really need a major design. Priority-3 A description (P3) Product-Terminal The new Windows Terminal.
Milestone

Comments

@artisticcheese
Copy link

Description of the new feature/enhancement

Currently to launch powershell cloudshell in Windows Terminal one have to launch bash and then within bash you have to launch powershell ending up with shell running inside another shell plus additional time to perform those task on each run.

Proposed technical implementation details (optional)

Do the same what Azure portal offers where you are given a choice which shell you want when you connect to cloudhsell either bash or powershell and go directly into it.

@artisticcheese artisticcheese added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label Mar 18, 2020
@ghost ghost added 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 Mar 18, 2020
@DHowett-MSFT DHowett-MSFT added Area-AzureShell Workitems pertaining to the Azure Cloud Shell connection. Issue-Task It's a feature request, but it doesn't really need a major design. Priority-3 A description (P3) Product-Terminal The new Windows Terminal. and removed Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. labels Mar 18, 2020
@ghost ghost removed the Needs-Tag-Fix Doesn't match tag requirements label Mar 18, 2020
@DHowett-MSFT DHowett-MSFT added this to the Terminal v1.x milestone Mar 18, 2020
@DHowett-MSFT DHowett-MSFT removed the Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting label Mar 18, 2020
@Don-Vito
Copy link
Contributor

Don-Vito commented Nov 9, 2020

I wrote a short PoC where I read the preferred shell from API but instead of opening it immediately, I allow to choose a shell, where empty selection (pressing Enter) continues with a preferred shell. See below.

However, I believe the major issue here is with UX, because this change introduces additional user input. I guess we could somehow prevent this input from appearing every time, by caching it, but this might complicate things as well (Do we cache it as a part of login session? Separately? Might it create inconsistencies).

@DHowett, @cinnamon-msft - WDYT?

Default Shell
image

Custom Shell
image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-AzureShell Workitems pertaining to the Azure Cloud Shell connection. Issue-Task It's a feature request, but it doesn't really need a major design. Priority-3 A description (P3) Product-Terminal The new Windows Terminal.
Projects
None yet
Development

No branches or pull requests

5 participants