[PR #8204] 7056: AzureConnection - if preferred cloud shell wasn't set let the user choose rather than crashing #27139

Open
opened 2026-01-31 09:20:14 +00:00 by claunia · 0 comments
Owner

Original Pull Request: https://github.com/microsoft/terminal/pull/8204

State: closed
Merged: No


Summary of the Pull Request

This is an alternative implementation for https://github.com/microsoft/terminal/pull/8197.
In rare occurrences, the shell settings might exist, but have no preferred shell configured.
Usually this will happen if the setting were created with old version of the cloud shell API.
Currently, we crash in such scenarios while trying to read a non-existing value.
This PR allows handles such cases by letting the user choose between PowerShell and Bash.

image

References

See https://github.com/microsoft/terminal/pull/8197 for alternative solution (that simply fails the connection with informative message).

PR Checklist

  • Closes https://github.com/microsoft/terminal/issues/7056
  • CLA signed.
  • Tests added/passed
  • Documentation updated.
  • Schema updated. - Irrelevant
  • I've discussed this with core contributors already. If not checked, I'm ready to accept this work might be rejected in favor of a different grand plan. Issue number where discussion took place: #xxx

Detailed Description of the Pull Request / Additional comments

Validation Steps Performed

  • Manual testing
  • Most of the testing was done with windbg changing the flow as if the preferred shell does not exist, as the problem does not reproduce in my subscriptions anymore
**Original Pull Request:** https://github.com/microsoft/terminal/pull/8204 **State:** closed **Merged:** No --- <!-- Enter a brief description/summary of your PR here. What does it fix/what does it change/how was it tested (even manually, if necessary)? --> ## Summary of the Pull Request This is an alternative implementation for https://github.com/microsoft/terminal/pull/8197. In rare occurrences, the shell settings might exist, but have no preferred shell configured. Usually this will happen if the setting were created with old version of the cloud shell API. Currently, we crash in such scenarios while trying to read a non-existing value. This PR allows handles such cases by letting the user choose between PowerShell and Bash. ![image](https://user-images.githubusercontent.com/4639110/98577037-06ec0e80-22c4-11eb-9401-c655adc90214.png) <!-- Other than the issue solved, is this relevant to any other issues/existing PRs? --> ## References See https://github.com/microsoft/terminal/pull/8197 for alternative solution (that simply fails the connection with informative message). <!-- Please review the items on the PR checklist before submitting--> ## PR Checklist * [x] Closes https://github.com/microsoft/terminal/issues/7056 * [x] CLA signed. * [ ] Tests added/passed * [ ] Documentation updated. * [ ] Schema updated. - Irrelevant * [ ] I've discussed this with core contributors already. If not checked, I'm ready to accept this work might be rejected in favor of a different grand plan. Issue number where discussion took place: #xxx <!-- Provide a more detailed description of the PR, other things fixed or any additional comments/features here --> ## Detailed Description of the Pull Request / Additional comments <!-- Describe how you validated the behavior. Add automated tests wherever possible, but list manual validation steps taken as well --> ## Validation Steps Performed * Manual testing * Most of the testing was done with windbg changing the flow as if the preferred shell does not exist, as the problem does not reproduce in my subscriptions anymore
claunia added the pull-request label 2026-01-31 09:20:14 +00:00
Sign in to join this conversation.
No Label pull-request
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#27139