Why Terramantle has no runners, and never will
Every IaC platform pitch eventually installs an agent with admin-ish credentials and everyone nods. The argument for keeping execution in your own pipelines.
Read the post →Practitioner writing on module and provider distribution, supply-chain scanning, air-gapped deployment, and the Terraform registry protocol. No filler. No AI generated content.
Every IaC platform pitch eventually installs an agent with admin-ish credentials and everyone nods. The argument for keeping execution in your own pipelines.
Read the post →Terrareg, Terralist, Terrakube, and citizen compared on scope, auth, storage, and maintenance, checked against the projects as they stand.
Read the post →Real HTTP transcripts for service discovery, versions, and the X-Terraform-Get download hop, plus the auth mistake that makes a naive registry decorative.
Read the post →Two naming decisions genuinely matter because consumers depend on them; the rest is bikeshedding. Repo names, source addresses, and namespaces.
Read the post →How GitHub Actions OIDC actually works, the AWS IAM parallel you already know, and a full worked publish workflow with nothing stored to leak.
Read the post →The maturity ladder from copy-paste to a registry, what a breaking change actually is in HCL, and the consumer-visibility gap that stalls upgrades.
Read the post →The monorepo-versus-polyrepo fight is a false choice. What teams want is polyrepo semantics at monorepo speed, and the registry is the missing piece.
Read the post →The RUM maths worked through with real numbers, and five escape routes priced fairly, from staying under the cap to self-hosting.
Read the post →