terragrunt-engine-opentofu v0.2.0: Shared Provider Cache and tf_path

The Terragrunt OpenTofu engine shipped v0.2.0 on October 8, 2026. The headline change: units now share a plugin provider cache, which cuts download time and disk usage when many units use the same providers. Both changes need some setup detail, so here is a quick summary.

The full release notes and the changelog are on the GitHub release page.

Units share a provider cache

With OpenTofu 1.10 or newer, the engine now sets TF_PLUGIN_CACHE_DIR automatically. This matches what Terragrunt already does for tofu processes it runs without the engine, so cache behavior is now consistent across both paths.

If you do not want the shared cache, turn it off in the engine meta block:

engine {
  source = "github.com/gruntwork-io/terragrunt-engine-opentofu"

  meta = {
    tofu_version               = "v1.11.2"
    no_auto_provider_cache_dir = true
  }
}

This release ships a single feature PR, PR #83, which adds the shared plugin cache support. The tf_path option below is covered in the release notes as a new feature as well.

Pick your own OpenTofu binary

A second feature in the notes is tf_path. Set it in the engine meta to run a specific tofu binary, for example one you built or installed outside the normal download flow:

engine {
  source = "github.com/gruntwork-io/terragrunt-engine-opentofu"

  meta = {
    tf_path = "/usr/local/bin/tofu"
  }
}

Without tf_path, the engine uses the first tofu on your PATH, or the version it downloads for the tofu_version you set. This is useful if you want to test a locally built binary against your units.

Upgrade notes

Nothing breaks in this release. The shared cache turns on by default for OpenTofu 1.10 and newer, so the only decision is whether to keep it. Set no_auto_provider_cache_dir = true in meta if you prefer the old behavior.

Where to get it

This is a normal release, not a prerelease. Worth a look if you run many Terragrunt units that pull the same providers.

← All updates