Public Preview: vscode.dev web connection experience

[sevillal]

Public Preview Scope

• Private link support (not required, but desirable) Further context in this comment below
• Non-public clouds support (not required)
• Experience
• VS Code CLI integration
• Telemetry
• Testing
• Performance

Legend

Legend of annotations:

Mark	Description
🏃	work in progress
✋	blocked task
💪	stretch goal for this iteration
🔴	missing issue reference
🔵	more investigation required to remove uncertainty
⚫	under discussion within the team
⬛	a large work item, larger than one iteration

Tasks

VS Code CLI

• Investigate what is needed to move to the VS Code CLI

#1784 (comment)

Telemetry

• Improve telemetry to capture post resolver errors #1867
• Investigate why telemetry tracker id is not captured #1868
• Pass a session ID from the Studio to vscode.dev to trace connection e2e #1869

Testing

• Implement unit test #1870
• Implement E2E test with a web driver #1871
• Set up monitoring tests for vscode.dev clickout #1799

Experience

• [Web] Investigate preserving selected kernel from Studio notebook editor to vscode.dev connected experience #1801
• Preserve active file context when clicking out from notebook editor #1800
• Fix "Open folder" from vscode.dev UI toolbar menu (current workaround: modify URL manually) #1834
• Triage failure to authenticate with Azure Account extension in web #1826
• Improve prompt when disconnected due to idle connection > 3hrs #1814

Performance

• Set performance baselines (alert on performance changes?) #1877

Other

• Reuse auth token if not expired (get it from the token info or request vscode.dev for support) #1876

[tbombach]

Summarizing the meeting this morning with Sean/Leah to confirm Private Link requirements:

Private Link is not a checklist item that gates all AzureML features before they are allowed to release a Public Preview (but is recommended for AzureML features). However for this Clickout to vscode.dev feature, we agreed during the planning stage that Private Link is an important part of the scenario based on the target customers and their requirements for connectivity and security. We re-confirmed today that before this feature moves to Public Preview, we will need to support Private Link.

[sevillal]

Closing this placeholder issue since most of the issues are closed.

Missing issues are added to this quarter's milestone.