microsoft/Terminal
GitHub で見るWindows Terminal fails to instantiate Azure Shell when it is configured with an isolated VNET
Open
#9,344 opened on 2021年3月2日
Area-AzureShellHelp WantedIssue-BugPriority-2Product-Terminal
Repository metrics
- Stars
- (35,764 stars)
- PR merge metrics
- (平均マージ 27d 19h) (30d で 24 merged PRs)
説明
Environment
Windows build number: Microsoft Windows [Version 10.0.18363.1379]
Windows Terminal version (if applicable): Version: 1.0.1401.0
Any other software? No
Steps to reproduce
Configure Cloud Shell with isolated VNET settings per https://docs.microsoft.com/en-us/azure/cloud-shell/private-vnet Validate correct Cloud Shell behavior with https://shell.azure.com In Windows Terminal attempt to create a new session for Azure Cloud Shell
Expected behavior
Cloud shell opens.
Actual behavior
Cloud shell fails to instantiate with the messages: You have not set up your cloud shell account yet. Please go to https://shell.azure.com to set it up. [process exited with code 1]