Skip to main content

Release notes

The current release of the BuiltForProd repositories is version 1.0.0 in every edition, as the README of each infrastructure and code repository states, and its layout is Terragrunt Stacks: every unit is defined once under units/, every account, subscription, project, region or stage is described by a terragrunt.stack.hcl, and Terragrunt generates the deployable tree. This page lists what ships in that release for the AWS, Azure and GCP Enterprise Baselines and their blueprints, and the exact versions each pins.

What ships​

AWS edition​

RepositoryVersionContents
acme-aws-platform-baseline1.0.0The landing zone: Organization, 15 accounts in two OUs, SCPs and tag policy, hub-and-spoke network with IPAM, security services, identity, GitHub OIDC, state backend, three workflows
acme-aws-blueprint-webapp-infra1.0.0Web platform per stage: EKS with Karpenter and Cluster Autoscaler, DocumentDB, ElastiCache, load balancer controller, CloudFront, ArgoCD, External Secrets, Fluent Bit (16 units per stage)
acme-aws-blueprint-webapp-code1.0.0Flask API and React frontend, Dockerfile, CI and the three delivery workflows
acme-aws-blueprint-webapp-gitops1.0.0Helm chart and per-stage values ArgoCD syncs
acme-aws-blueprint-etl-infra1.0.0Data platform per stage: S3 data lake, Lake Formation, Glue, Lambda trigger (6 units per stage)
acme-aws-blueprint-etl-code1.0.0Glue job script and Lambda container with CI and CD
acme-aws-blueprint-secrets1.0.0SOPS-encrypted secrets per stage, synced to SSM Parameter Store

Azure edition​

RepositoryVersionContents
acme-azure-platform-baseline1.0.0The landing zone: three management groups, 15 subscriptions, Azure Policy guardrails, hub VNet with Azure Firewall, DNS, Defender for Cloud, immutable audit storage, Entra RBAC, federated identities, Container Apps runners, state backend, four workflows
acme-azure-blueprint-webapp-infra1.0.0Web platform per stage: AKS with Node Auto Provisioning, managed ingress, Front Door, Cosmos DB for MongoDB vCore, Azure Managed Redis, application Key Vault, Application Insights, External Secrets, cert-manager, ArgoCD (13 units per stage)
acme-azure-blueprint-webapp-code1.0.0Flask API and React front end, Dockerfile, CI and the delivery workflows
acme-azure-blueprint-webapp-gitops—Helm chart and per-stage values ArgoCD syncs
acme-azure-blueprint-etl-infra1.0.0Data platform per stage: ADLS Gen2 lake, Azure Databricks workspace, Unity Catalog, Databricks job, Event Grid and Container Apps trigger (5 units per stage)
acme-azure-blueprint-etl-code1.0.0PySpark transform and trigger container with CI and CD
acme-azure-blueprint-secrets—SOPS-encrypted secrets per stage, synced to the application Key Vault of each stage

GCP edition​

RepositoryVersionContents
acme-gcp-platform-baseline1.0.0The landing zone: organization, three folders, 15 projects, organization policies and an IAM deny policy, Shared VPC with firewall policies and Cloud NAT, DNS, Security Command Center, aggregated audit logs, groups and Privileged Access Manager, Workload Identity Federation, Artifact Registry, state backend, five workflows
acme-gcp-blueprint-webapp-infra1.0.0Web platform per stage: GKE, External Secrets, external-dns (public and internal), cert-manager, ArgoCD, Firestore, Memorystore for Valkey, the Cloud Run front end and the API edge (11 units per stage)
acme-gcp-blueprint-webapp-code1.0.0Flask API and React front end, Dockerfile, CI and the delivery workflows
acme-gcp-blueprint-webapp-gitops—Helm chart with the GKE Gateway and per-stage values ArgoCD syncs
acme-gcp-blueprint-etl-infra1.0.0Data platform per stage: Spark identity, Cloud Storage lake, BigQuery datasets, Dataplex, Eventarc-driven Cloud Run trigger (5 units per stage)
acme-gcp-blueprint-etl-code1.0.0PySpark transform and trigger service with CI and CD
acme-gcp-blueprint-secrets—SOPS-encrypted secrets per stage, synced to Secret Manager in each stage project

The GitOps and secrets repositories carry no version line in their README; they ship with the release of their blueprint.

The Terragrunt Stacks layout​

Every repository defines each unit type once and describes each folder with a stack file. Templates group the units a workload stage always has:

TemplateAWS editionAzure editionGCP edition
Workload stage of the Baselinestacks/plat-account (seven units)stacks/plat-subscription (eight units)stacks/plat-project (four units)
Shared includesstacks/includes/account-commonstacks/includes/subscription-common, subscription-linkstacks/includes/project-common
Web App Blueprint stagestacks/webapp-stage (sixteen units)stacks/webapp-stage (thirteen units)stacks/webapp-stage (eleven units)
Data and ETL Blueprint stagestacks/etl-stage (six units)stacks/etl-stage (five units)stacks/etl-stage (five units)

Terragrunt generates the units into git-ignored .terragrunt-stack/ folders, and root.hcl keeps every state key equal to the folder path. scripts/check-stack-layout.py guards the layout in pre-commit and CI, and the plan and apply workflows upload a JSON run report per run. The concept is explained under Terragrunt units and stacks.

Pinned versions​

AWS edition tools and providers​

ComponentVersionWhere it is pinned
OpenTofu1.12.6root.hcl (>= 1.12.6, < 2.0.0); TF_VERSION in every workflow
Terragrunt1.1.6root.hcl (>= 1.1.6); TG_VERSION in every workflow
AWS provider~> 6.65root.hcl generate "versions", repeated in module versions.tf files that need aliases or extra providers
Helm provider~> 3.3Module versions.tf (web platform)
Kubernetes provider~> 3.2Module versions.tf (web platform)
tflintv0.64.0plan.yml (landing zone)
tflint AWS ruleset0.48.0.tflint.hcl
SOPS3.13.3SOPS_VERSION in the secrets workflows
GitHub ActionsCommit SHA per action, version in the trailing comment.github/workflows/*.yml in every repository

Azure edition tools and providers​

ComponentVersionWhere it is pinned
OpenTofu1.12.6root.hcl (>= 1.12.6, < 2.0.0); TF_VERSION in every workflow; the runner image
Terragrunt1.1.6root.hcl (>= 1.1.6); TG_VERSION in every workflow; the runner image
hashicorp/azurerm~> 5.7root.hcl generate "versions" in every infrastructure repository
hashicorp/azuread, Azure/azapi~> 3.10, ~> 2.13root.hcl (Baseline)
hashicorp/time~> 0.13Four Baseline module versions.tf files
hashicorp/helm, hashicorp/kubernetes~> 3.3, ~> 3.2Module versions.tf (web platform)
hashicorp/random~> 3.7root.hcl (web platform)
databricks/databricks~> 1.135Module versions.tf (data platform)
tflintv0.64.0plan.yml
tflint-ruleset-azurerm0.32.0.tflint.hcl
SOPS, yq3.13.3, v4.47.1SOPS_VERSION, YQ_VERSION in the secrets workflows; the runner image
kubectl, Helm, kubeloginv1.36.5, v3.22.0, v0.2.20runner-image/Dockerfile, checksum-verified
GitHub ActionsCommit SHA per action, version in the trailing comment.github/workflows/*.yml in every repository

GCP edition tools and providers​

ComponentVersionWhere it is pinned
OpenTofu1.12.6root.hcl (>= 1.12.6, < 2.0.0); TF_VERSION in every workflow
Terragrunt1.1.6root.hcl (>= 1.1.6); TG_VERSION in every workflow
hashicorp/google, hashicorp/google-beta~> 8.5root.hcl generate "versions", repeated in module versions.tf files with aliases
hashicorp/helm~> 3.3Module versions.tf (Baseline runners, web platform)
hashicorp/kubernetes~> 3.2Module versions.tf (web platform)
tflintv0.64.0plan.yml
tflint-ruleset-google0.40.0.tflint.hcl
SOPS, yq3.13.3, v4.47.1SOPS_VERSION, YQ_VERSION in the secrets workflows
GitHub ActionsCommit SHA per action, version in the trailing comment.github/workflows/*.yml in every repository

Registry modules (AWS edition)​

ModuleVersionWhere it is used
terraform-aws-modules/vpc/aws6.7.3units/vpc-hub, units/vpc-spoke, units/vpc-runner; modules/vpc-endpoints submodule (landing zone)
terraform-aws-modules/transit-gateway/aws3.3.1units/transit-gateway (landing zone)
terraform-aws-modules/ecr/aws3.2.1modules/ecr (landing zone)
terraform-aws-modules/s3-bucket/aws5.16.1modules/s3 (landing zone, ETL); modules/frontend-cdn (web platform)
github-aws-runners7.11.0modules/github-runner (landing zone)
terraform-aws-modules/eks/aws21.25.1modules/eks and its karpenter submodule in modules/karpenter (web platform)
terraform-aws-modules/eks-pod-identity/aws2.9.0modules/alb-controller, app-namespace, cluster-autoscaler, external-dns, external-secrets (web platform)
terraform-aws-modules/elasticache/aws1.11.1modules/elasticache (web platform)
terraform-aws-modules/cloudfront/aws6.7.1modules/frontend-cdn (web platform)
terraform-aws-modules/lambda/aws8.8.2modules/lambda (ETL)

The design decisions record every pin as the latest release as of 2026-09-19. The landing zone pins vpc and transit-gateway in the unit definitions; every other registry module is pinned in the module's main.tf.

The Azure and GCP repositories use no registry modules: every module is custom and lives in its repository, so there are no module versions to track.

Runtime versions set in the units​

Component (AWS edition)VersionWhere
Kubernetes (EKS)1.36units/eks (web platform)
DocumentDB engine5.0.0units/documentdb
ElastiCache Redis engine7.1units/elasticache
Glue4.0, PySparkmodules/glue-job (ETL)
Component (Azure edition)VersionWhere
Kubernetes (AKS)1.36 at creation, then the patch channelunits/aks (web platform)
Cosmos DB for MongoDB vCore server8.0modules/mongo-cluster (web platform)
ArgoCD chart9.5.22modules/argocd (web platform)
cert-manager chartv1.21.2modules/cert-manager (web platform)
External Secrets chart2.6.0modules/external-secrets (web platform)
Databricks runtimeThe latest long-term-support releasemodules/databricks-job (data platform)
Component (GCP edition)VersionWhere
Kubernetes (GKE)1.35 minimum at creation, then the REGULAR release channelunits/gke and modules/gke (web platform)
Memorystore for ValkeyVALKEY_8_0modules/valkey (web platform)
ArgoCD chart10.9.6modules/argocd (web platform)
cert-manager chartv1.21.2modules/cert-manager (web platform)
external-dns chart1.23.0modules/external-dns (web platform)
External Secrets chart2.11.0modules/external-secrets (web platform)
Dataproc Serverless runtime2.3 (Spark 3.5, Python 3.11)stacks/etl-stage and modules/cloud-run-trigger (data platform)

The Azure and GCP Baseline version pages list every GitHub Action and pre-commit hook revision of the Baseline repositories.

How versions change​

Pins are updated one component at a time, planned in dev before staging and prod, with a risk level and an approver per kind of change; see the versioning policy. The procedures that keep a running deployment current are indexed under upgrade guides.