starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-04 05:35:20 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Azure cloud shell on dev build #4694

New Issue
Closed
opened 2026-01-30 23:54:20 +00:00 by claunia · 4 comments
claunia commented 2026-01-30 23:54:20 +00:00
Owner
Copy Link

Originally created by @giggio on GitHub (Oct 28, 2019).

Environment

Windows build number: Microsoft Windows [Version 10.0.18362.418]
Windows Terminal version: Dev build from commit `634687ba`

Steps to reproduce

Git clone this repo, and run a release build.

Expected behavior

Cloud shell shows up as a profile.

Actual behavior

Cloud shell does not show up as a profile.

Extra info

I'm also running the preview release from the store. It works there, the cloud shell profile shows up and works.

I tried to manually add to the profiles.json file:

{
  "guid": "{b453ae62-4e3d-5e58-b989-0a998ec441b8}",
  "hidden": false,
  "name": "Azure Cloud Shell",
  "source": "Windows.Terminal.Azure"
}

It doesn't work, nothing shows up.

If I add a configuration without a source, like so:

{
    "acrylicOpacity" : 0.6,
    "closeOnExit" : false,
    "colorScheme" : "Vintage",
    "commandline" : "Azure",
    "connectionType" : "{d9fcfdfa-a479-412c-83b7-c5640e61cd62}",
    "cursorColor" : "#FFFFFF",
    "cursorShape" : "bar",
    "fontFace" : "Consolas",
    "fontSize" : 10,
    "guid" : "{b453ae62-4e3d-5e58-b989-0a998ec441b8}",
    "historySize" : 9001,
    "icon" : "ms-appx:///ProfileIcons/{b453ae62-4e3d-5e58-b989-0a998ec441b8}.png",
    "name" : "Azure Cloud Shell",
    "padding" : "0, 0, 0, 0",
    "snapOnInput" : true,
    "startingDirectory" : "%USERPROFILE%",
    "useAcrylic" : true
}

Then the profile shows up, but it starts blank. This is after I start it:

image

If I add a source attribute to it, it disappears from the profiles dropdown.

Is there a dependent executable that I should have added to the destination directory, or something like that? What am I missing?

Originally created by @giggio on GitHub (Oct 28, 2019). # Environment ```none Windows build number: Microsoft Windows [Version 10.0.18362.418] Windows Terminal version: Dev build from commit `634687ba` ``` # Steps to reproduce Git clone this repo, and run a release build. # Expected behavior Cloud shell shows up as a profile. # Actual behavior Cloud shell does not show up as a profile. # Extra info I'm also running the preview release from the store. It works there, the cloud shell profile shows up and works. I tried to manually add to the `profiles.json` file: ````json { "guid": "{b453ae62-4e3d-5e58-b989-0a998ec441b8}", "hidden": false, "name": "Azure Cloud Shell", "source": "Windows.Terminal.Azure" } ```` It doesn't work, nothing shows up. If I add a configuration without a `source`, like so: ````json { "acrylicOpacity" : 0.6, "closeOnExit" : false, "colorScheme" : "Vintage", "commandline" : "Azure", "connectionType" : "{d9fcfdfa-a479-412c-83b7-c5640e61cd62}", "cursorColor" : "#FFFFFF", "cursorShape" : "bar", "fontFace" : "Consolas", "fontSize" : 10, "guid" : "{b453ae62-4e3d-5e58-b989-0a998ec441b8}", "historySize" : 9001, "icon" : "ms-appx:///ProfileIcons/{b453ae62-4e3d-5e58-b989-0a998ec441b8}.png", "name" : "Azure Cloud Shell", "padding" : "0, 0, 0, 0", "snapOnInput" : true, "startingDirectory" : "%USERPROFILE%", "useAcrylic" : true } ```` Then the profile shows up, but it starts blank. This is after I start it: ![image](https://user-images.githubusercontent.com/334958/67712668-3115ab80-f9a3-11e9-870a-5dfde72d9eff.png) If I add a `source` attribute to it, it disappears from the profiles dropdown. Is there a dependent executable that I should have added to the destination directory, or something like that? What am I missing?
claunia added the Resolution-By-DesignNeeds-Tag-Fix labels 2026-01-30 23:54:20 +00:00
claunia commented 2026-01-30 23:54:21 +00:00
Author
Owner
Copy Link

@gmsantos commented on GitHub (Oct 28, 2019):

I can reproduce this issue on dev build as well.

@gmsantos commented on GitHub (Oct 28, 2019): I can reproduce this issue on dev build as well.
claunia commented 2026-01-30 23:54:21 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Oct 28, 2019):

If you launch that session, you'll see that it doesn't work. You'll need to provide your own Azure client ID (in AzureClientID.h). This is by design.

@DHowett-MSFT commented on GitHub (Oct 28, 2019): If you launch that session, you'll see that it doesn't work. You'll need to provide your own Azure client ID (in AzureClientID.h). This is by design.
claunia commented 2026-01-30 23:54:21 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Oct 28, 2019):

(Thanks for the report!)

@DHowett-MSFT commented on GitHub (Oct 28, 2019): (Thanks for the report!)
claunia commented 2026-01-30 23:54:21 +00:00
Author
Owner
Copy Link

@giggio commented on GitHub (Oct 28, 2019):

If you launch that session, you'll see that it doesn't work. You'll need to provide your own Azure client ID (in AzureClientID.h). This is by design.

@DHowett how do we do that? How does the build in the store does it?

@giggio commented on GitHub (Oct 28, 2019): > If you launch that session, you'll see that it doesn't work. You'll need to provide your own Azure client ID (in AzureClientID.h). This is by design. @DHowett how do we do that? How does the build in the store does it?
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Needs-Tag-Fix Resolution-By-Design
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#4694
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?