Summary
Add a native Local-to-Cloud bridge so users can move from local wslc image/session workflows to Azure deployment workflows without leaving Porthole.
Problem
Porthole currently excels at local workflows, but users must manually switch tools/contexts to publish images to Azure Container Registry (ACR) and recreate local topology in AKS.
Proposal
Part A: Push local images to ACR
- Add Azure auth/account connection in Porthole (device code + tenant/subscription selection).
- Add context action on local images: Push to ACR.
- Let users select/create target registry + repository/tag mapping.
- Surface push progress, retries, and actionable errors in UI.
Part B: Export running local Session to AKS/IaC
- Add Export to AKS action for an active Session.
- Inspect active Session topology (containers, images, ports, env vars, network mode).
- Generate equivalent scaffold:
- Kubernetes YAML (Deployment/Service/ConfigMap/Secret placeholders), and/or
- Terraform scaffold for AKS deployment artifacts.
- Include warnings for non-portable local-only config.
Scope Notes
- Preserve App/Core/Tray boundaries.
- Keep Azure SDK usage out of WinUI-only layers where possible (service abstraction in Core, implementation in Tray/backend).
- Maintain typed progress reporting and operation envelope patterns over named pipes.
Acceptance Criteria
- User can authenticate to Azure and select ACR target from within Porthole.
- Right-click on local cached image shows Push to ACR and successfully uploads image/tag.
- Running Session shows Export to AKS and emits valid, parseable Kubernetes YAML and/or Terraform files.
- Export captures at least: container images, command/args, env placeholders, ports/services, and network intent mapping.
- UI displays progress and failures with recoverable guidance.
- No regression to existing image/session operations.
Out of Scope (initial cut)
- Full production-grade AKS policy hardening.
- Automatic cloud deployment execution (export/scaffold first).
Suggested Labels
enhancement, cloud, azure, export
Summary
Add a native Local-to-Cloud bridge so users can move from local
wslcimage/session workflows to Azure deployment workflows without leaving Porthole.Problem
Porthole currently excels at local workflows, but users must manually switch tools/contexts to publish images to Azure Container Registry (ACR) and recreate local topology in AKS.
Proposal
Part A: Push local images to ACR
Part B: Export running local Session to AKS/IaC
Scope Notes
Acceptance Criteria
Out of Scope (initial cut)
Suggested Labels
enhancement,cloud,azure,export