atmos terraform cache stats
Report filesystem facts about the registry cache: total size, object count, the provider-vs-module breakdown, and the largest and oldest objects. Counts include only cached registry artifacts (providers and modules) — proxy infrastructure co-located in the cache root, such as the self-signed TLS certificate, is not counted.
These stats describe the registry cache (the proxy-managed cache of provider and module registry traffic), not Terraform's separate provider plugin cache (plugin_cache).
Usage
atmos terraform cache stats [flags]
Flags
--format/-f- Output format:
table(default),json, oryaml.
No hit rate (by design)
stats does not report a cache hit rate. By design, the filesystem is the cache index — there is no persistent hit/miss store, because a hit is a per-run event, not stored state. Per-run hit counts and bytes-saved are surfaced once, by the savings report printed at the end of a terraform/tofu run when bytes were served from cache. Persistent hit-rate reporting would require a future, optional metrics database and is intentionally out of scope.
Examples
atmos terraform cache stats
atmos terraform cache stats --format=json
Try it out
- Install Atmos
- Try the example
Copy the example into a new directory and make it your own:
atmos init examples/caching
cd caching
Inspect the cache statistics. A fresh cache may be empty; the README shows how to populate it.
atmos terraform cache stats
