Pipeline Template Examples
Konstruct ships upstream pipeline templates in the konstructio/konstruct-templates repository. When you register an application, Konstruct applies the selected pipeline template to your repository — copying workflow files and Helm charts as a one-time scaffold.
Two pipeline ecosystems are available:
| Template | Path | Workflows | Environments | Promotion Model |
|---|---|---|---|---|
| Default | templates/workflows | 2 | Configurable stages | Manual dispatch per environment |
| Promotion | pipeline-templates/promotion | 6 | dev, test, stage, prod | GitOps-based progressive promotion |
Choosing a Template
Use Default when you want a simple publish-and-deploy model with a single dispatch workflow that targets any environment by name.
Use Promotion when you need a 4-environment progressive pipeline with artifact traceability — the same validated container and chart flows from dev through prod, with release re-tagging and hotfix support.
Token Replacement
Both templates use <TOKEN> placeholders that Konstruct replaces during app registration:
| Token | Description |
|---|---|
<AWS_REGION> | AWS region for ECR and OIDC |
<ROLE_ARN> | IAM role ARN for OIDC federation |
<ORG_NAME> | GitHub organization name |
<GITOPS_REPO_NAME> | GitOps repository name |
<APP_NAME> | Application name (used in Argo CD manifests) |
<ENVIRONMENT> | Environment names (default template only) |
<REPO_NAME> | Repository/chart name |