Fast Path Pipeline: Deterministic deploy templates
Maintainers usually reply within 2 days
Nobody has claimed this yet.
- #564 by @gambtho — closed without merging
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 64/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- azure, github-actions, kubernetes, typescript
- Domain
- cloud, devops, infrastructure
Research direction
Start by locating ContainerConfig and the existing aks-devhub workflow pattern, then create fastPathTemplates.ts with the three named pure generators. Add comprehensive tests for the generated workflow and manifests, including the listed permissions, pinned action, paths, substitutions, and configured deployment and service fields; done means config-in strings match the tested templates.
Written by the indexing model from the issue text.
Description
Part of #557
Problem
The Copilot agent generates a different workflow each time — and the generated workflows have recurring bugs: single-job design, missing permissions, unpinned kubelogin, fragile sed-based image substitution, and no explicit Dockerfile path. These are the root causes of most deploy failures.
When we already have the user's config (cluster, namespace, ACR, Dockerfile path, container settings), we can generate a correct workflow and manifests deterministically from tested templates.
Changes
Create fastPathTemplates.ts with three pure functions:
generateDeployWorkflow()— produces a two-job workflow (buildImage+deploy) based on the proven aks-devhub pattern. Fixes all known bugs: pinnedkubelogin-version: 'v0.1.6',Azure/k8s-deploy@v5for image substitution,actions: readpermission, explicitDOCKER_FILEandBUILD_CONTEXT_PATHenv vars,continue-on-erroron annotations.generateDeploymentManifest()— Deployment YAML parameterized from ContainerConfig (replicas, resources, probes, security context, anti-affinity, pipeline annotations)generateServiceManifest()— Service YAML with configured type, ports, and selector
All functions are pure (config in → string out) with comprehensive test coverage.
- Dominant language
- TypeScript
- Stars
- 115
- Forks
- 31
- Avg merge
- 2d 17h
- Merged PRs (30d)
- 16
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Azure/aks-desktop
-
[FEATURE] Change cluster action label from “Delete” to “Remove”Possibly taken @tejhan claimed this 20 days ago. Openenhancement triage
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Azure/aks-desktop#992 · 1 assignee ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Azure/aks-desktop#675 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Azure/aks-desktop#674 ·
Maintainers usually reply within 2 days
-
triage
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Azure/aks-desktop#458 · 1 comment ·
Maintainers usually reply within 2 days
-
enhancement triage
Difficulty 5/5 Over a week Newbie friendliness 35/100
Azure/aks-desktop#1089 ·
Maintainers usually reply within 2 days
All issues in Azure/aks-desktop
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
oxidecomputer/skepsis#102 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
voidzero-dev/void#677 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
kunchenguid/gh-axi#247 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
lidge-jun/opencodex#8101 · 2 comments ·
Maintainers usually reply within 1 day