Shyft SolutionsDev guideImage–config coupling
GitHub
Image–config coupling
Why the quadlet template lives in the app repo — the .tmpl + values.yaml split, the render CLI, and what happens when the template breaks.
Coming soon — stub

This page is a placeholder. The render CLI and template convention haven't shipped yet — see the parent CI/CD for internal apps for the high-level model, or .claude/features/deploy-pipeline/research.md § D9 for the decision rationale.

What this page will cover

  • Conceptual model: why image content and runtime shape must travel together, and which patterns large orgs use to enforce that ("schema label + CI gate", "image carries the manifest", "per-app template + bump", …).
  • The chosen pattern — per-app .tmpl in the app repo, values.yaml in shyft-infra, render at CI time, bump-PR carries the full rendered diff.
  • Template language reference: Go text/template syntax cheat-sheet scoped to what's available — {{ .image }}, {{ .network }}, conditional blocks, ranges.
  • values.yaml schema: required keys, optional keys, defaults, what CI does if a key referenced by the template is missing.
  • The render CLI — how to run it locally to preview a bump-PR's rendered output before tagging, common failure modes.
  • Edge cases: template breaks mid-render, values schema drift, dependency-container shape changes.

Until then

Read § Image–config coupling on the parent page for the model + the "change-shape → where you edit" table.