v1.7.0: Terraform State Store
Snap CD implements the Terraform HTTP backend protocol directly, so state can live in Snap CD rather than in a separate bucket.
Full notes: 1.7.0 on GitHub.
Storage and access
StateStore and StateFile entities with full CRUD. State blobs are encrypted at rest with AES-256. Access is governed by the same role model as the rest of the product — Owner, Contributor, Reader, IdentityAccessManager on the State Store — so state permissions follow from Snap CD roles rather than a separate cloud IAM policy. Runners authenticate with Service Principal credentials over HTTP Basic.
Versioning
Each write creates a new version rather than overwriting, with configurable retention (MaxStateFileVersions, default 20) and automatic pruning of older versions.
Restore
Restoring extracts the serial from the current latest version, increments it, and writes it into the restored version with a fresh lineage GUID — so the result is a valid successor rather than a rewind Terraform will reject. Serial lives only inside the state JSON, which stays the single source of truth. Corrupted state fails with an explicit error rather than a silent fallback.
Dashboard
Nested version panels with a "Current" chip on the latest; per-version download, restore and delete; per-file rename, force-unlock and delete; a Monaco editor with Snap CD light and dark themes for reading state JSON.
Native runner credentials
A RunnerEnvVars settings section injects environment variables into every task execution. Values can be sourced from externalsettings.json (Key Vault, Secrets Manager) with hot reload. Server-resolved values take precedence over runner-local ones.
Intelligent GitOps for Infrastructure as Code. Automate, orchestrate, and scale your infrastructure deployments with confidence.
© 2026 Snap CD. All rights reserved.