Terrapod is a free, open-source platform replacement for Terraform Enterprise — the collaboration, governance, state and UI layer around OpenTofu, Terraform, Pulumi and Ansible. This is the sixth 2.0 beta, and the largest: the supply-chain work is now end to end, and there is a documented upgrade path for every behaviour that changed.
Read the upgrade guide before upgrading. Its two pre-flight tables list what to do and what breaks quietly if you do not; this release adds thirteen entries to them.
Highlights
- A supply-chain ledger for everything the caches admit — every artifact records how it was admitted and who vouched for it, keyed on the digest and replicated whole, with an operator-facing view of what is inventoried and what was refused.
- Publisher verification, not just the digest the index published — PEP 740 attestations on PyPI and registry signatures on npm are verified through Sigstore, so an artifact can be attributed to who published it rather than only matched against a hash. Platform tools are verified against their publisher's signature by default, degrading to the checksum when the signing material cannot be reached and refusing only when a signature genuinely fails.
- The Go checksum database is mirrored, so module hashes are verified again. Sealed deployments must warm it before sealing — see the guide.
- Named storage locations — a workspace's objects can live in a separate bucket or account for data segregation, fixed at creation, with a start-up reachability probe that drains a pod rather than crashing the fleet.
- Operator uploads for sealed nodes — the binaries and providers a sealed node cannot fetch can be uploaded from the UI, are resolvable and SDK-reachable, and retention never reaps what it cannot re-fetch.
- Listener CA rotation with dual trust, so rotating is no longer an outage, with listeners identifying by certificate fingerprint and a selectable CA algorithm. A post-quantum inventory documents what is safe, what is compatible and what is not.
- Fixed-name aggregate VCS statuses, so branch protection can gate on Terrapod rather than on per-workspace check names that change.
- Autodiscovery rules gain exclusion and propagation — an edit can be rolled out to the workspaces a rule already created, scoped to the fields that changed and skipping any workspace that has since been customised, with the whole surface reaching the Terraform and Pulumi providers and MCP.
Breaking Changes
Each has an entry in the upgrade guide with the reason and the key that restores the old behaviour where one exists.
- Every cache is always on; the per-cache
enabledflags are removed. Avalues.yamlstill setting one failshelm lint.PackageCacheSource.Enabledis gone from the Go SDK. registry.provider_cache.verify: offis removed — provider verification cannot be switched off.- Cloud-identity minting is strict by default:
require_phaseandrequire_assigned_poolboth default on. If any listener predates v1.10, move it first or set them false until you have. - Terrapod owns the token signing key. A key derived from the database URL is replaced rather than adopted.
- A weak supplied secret now fails startup, with a remedy for the KEK; new wraps are salted and stretched.
- Artifacts cached before 2.0 are re-fetched once to verify them, and operator-uploaded artifacts replicate by default and move to their own prefix. On a sealed deployment, unseal and re-warm before sealing again.
- The web pod gains a
storage-rewriteinit container. If you pinweb.image.tagor mirror images, pull the new web image with the chart: a 2.0 chart with a 1.x web image givesInit:CrashLoopBackOffon every web replica.
Bug Fixes
- npm pull-through cached nothing, ever. The artifact ledger's digest column was
varchar(80)and an npm digest is the 95-character SRI upstream publishes, so every npm admission aborted its transaction and took the cache row with it. Everynpm installre-fetched upstream, a sealed node could not serve npm at all, and no ledger row existed for any npm artifact. - Pulumi and docker get a
Content-Lengthagain. From Next 16.4.5 a route handler cannot emit one, so a plugin download was refused outright and a registry blob HEAD had nothing to read; the filesystem backend's presigned URLs now take an external rewrite. - An
upstream-publisherrow recorded no publisher, dropping the evidence that justified it — and the admin view rendered that strongest state as the weakest, because the panel had no arm for it. - An artifact with no digest collided three ecosystems onto one primary key.
- A misconfigured storage location drains a pod rather than crashing the fleet.
- Sensitive inventory values are masked on the resolved read surface.
- Bulk actions follow the server's answer, and the bulk menu asks whether the user may rather than only whether the run can.
- A filter error from the exclusion report is a 422 rather than a 500, and
status:filters match the workspace's own run status. - The configure log's columns line up and its progress notices tell the truth.
Security
- Provider verification can no longer be disabled, and identity minting is strict by default.
- Every pull-through artifact is verified against its upstream digest; an unattested cached row is re-verified rather than served.
- The cache restricts what it serves, not only where it fetches from.
- Six code-scanning alerts closed, and the accepted-risk register reviewed.
Status
Beta — the 2.0 line is feature-complete and under pre-release review; the upgrade path from 1.x is documented end to end. Not yet recommended for production.
Full Changelog: v2.0.0-beta.5...v2.0.0-beta.6