LoginSign Up
← Back to all sparks
T

Terragrunt

INFRA · APIS
Velocity5.0

Thin wrapper for Terraform providing DRY infrastructure configurations

terragrunt.gruntwork.io ↗

Terragrunt 1.2's last candidate finishes eleven experiments and locks down state buckets.

terraforminfrastructure-as-codeexperimentsrelease-candidatestate-security
◆Current state
Terragrunt v1.2.0-rc3, dated mid-October, is declared the final candidate: unless a blocker appears, v1.2.0 ships with its contents. The cycle completes eleven experiments, among them OCI, block-iteration, azure-backend and optional-hooks. Two changes need attention: base64gzip() now returns the Go 1.27 encoder's output, which can trigger resource replacements, and S3 bootstrapping no longer adds the RootAccess bucket policy statement.
◆Where it's heading
The graduation model has repeated at a larger scale: six experiments in v1.1, eleven in v1.2. The candidates ran as stabilization, with fixes concentrated in the CAS, the catalog and the Provider Cache Server. Each breaking change also ships with an escape hatch, base64gzip_compat() or enable_bucket_root_access, which shows how seriously the project treats its 1.0 guarantees.
◆Prediction
v1.2.0 final is the next release, since rc3 says only regression or urgent fixes will land first. It has not appeared in this feed in the 18 days since rc3.

◆Recent moves

  1. 20d ago

    v1.2.0-rc3: final candidate, nine more bug fixes

    The third and declared final candidate keeps the same eleven experiments and adds nine bug fixes. It freezes the v1.2.0 content, so only regressions or urgent fixes remain before release.

    View source ↗
  2. 28d ago

    v1.2.0-rc2: CAS, catalog and provider cache fixes

    The second candidate adds bug fixes to the same eleven experiments, mostly in the CAS, the catalog, the Provider Cache Server and exclude blocks. It is a stabilization checkpoint with no new scope.

    View source ↗
  3. 1mo ago

    v1.2.0-rc1 completes eleven experiments at once

    The first v1.2 candidate completes eleven experiments, including OCI, block-iteration and azure-backend, and removes the RootAccess statement from new S3 state buckets. It repeats the v1.1 pattern at nearly twice the size.

    View source ↗
  4. 4mo ago

    v1.1.0-rc3

    The third candidate restates the same six graduated experiments and carries bug fixes against them. At this point the notes are unchanged from rc1 and the release is a stabilisation checkpoint.

    View source ↗
  5. 4mo ago

    v1.1.0-rc2

    Carries the same feature list as rc1 plus the first mention of improvements to how releases are published and verified — provenance work being folded into the candidate cycle rather than deferred.

    View source ↗
  6. 4mo ago

    v1.1.0-rc1

    ⚡ SPARK

    The first v1.1.0 candidate, and the release where six experiments graduate at once: stack-dependencies, the content-addressable store, catalog redesign, mark-many-as-read, opt-out-auth and DAG queue display. Everything in rc2 and rc3 is stabilisation of this list.

    View source ↗