DevOps Templates¶
Evidence (dated)
This page records observations at a stated revision and date. Re-verify before relying on it; it is not a permanent contract.
Filled 2026-10-09
This page was empty. The inventory below is verified against the repositories; nothing here is a Factory service. Generated pipelines and IaC are Software Factory pack outputs executed by the Execution plane.
What exists¶
| Asset | Where | Notes |
|---|---|---|
| Shared pipeline templates | ConnectSoft.AzurePipelines |
Reused by every repository's azure-pipelines*.yml; includes NuGetAuthenticate@1 and Azure Artifacts publishing conventions |
| Template pack composition | ConnectSoft.BaseTemplate/build/Prepare-ExtendedTemplatePack.ps1, Invoke-TemplateCompose.ps1, azure-pipelines-template.yml |
Real pack-time composition of specialized templates over the base (canonical ADR-00xx) |
| Infrastructure as code | *.InfrastructureModel projects referencing Pulumi.AzureNative in BaseTemplate, Agent and API Gateway templates; DerechHaLev AuthServer and Identity carry Pulumi.yaml with dev and aws-dev stacks |
Pulumi programs; zero .bicep files across the estate (ADR-0004, verified) |
| Container and cluster manifests | Deployment/docker-compose, Deployment/kubernetes in BaseTemplate, Microservice, Worker, Agent and API Gateway templates |
Deployment folders hold manifests, not IaC programs |
| Per-repository pipelines | azure-pipelines.yml, azure-pipelines-documentation.yml and model-specific pipelines in each template repository |
Build, test, pack, publish |
| Documentation pipelines | azure-pipelines-documentation.yml in documentation repositories |
MkDocs site artifact |
| Scripts | ConnectSoft.PowerShell.ToolsAndScripts; ConnectSoft.AzureInfrastructure (no projects, delivery tooling placeholder) |
What a generated pipeline is built from¶
A Factory-generated repository receives the repository's azure-pipelines*.yml referencing the shared templates, its InfrastructureModel Pulumi program, docker-compose and Kubernetes manifests, and the documentation pipeline. Delivery receipts (build, PR, release, promotion) are Execution-plane records; Azure DevOps or GitHub stays the system of record (delivery engine).
Gaps¶
No pipeline-generation agent run, no Factory delivery service, no GitOps reconciler, no supply-chain attestation; the Factory itself provisions nothing yet.