Module Intelligence
The Module Intelligence view provides visibility into all external Terraform modules used across your organization — which modules are in use, where they come from, how many repositories consume them, and which versions are deployed.
Overview
As organizations grow, module sprawl becomes a real problem: teams adopt modules independently, versions diverge, and nobody has a clear picture of what's actually in use. Module Intelligence solves this by automatically detecting external module references during post-merge processing and aggregating them into a single, searchable inventory.
Module List
The main view displays all detected external modules, sorted by consumer count (most-used first). Each module shows:
| Column | Description |
|---|---|
| Source Badge | Visual indicator of the module source type (registry, git, S3, GCS, or HTTP) |
| Source URL | Full module source identifier (truncated if longer than 60 characters) |
| Consumers | Number of module references across all repositories |
| Repos | Count of unique repositories using this module |
| Latest Version | Most recent version detected (v-prefixed) |
| Last Seen | Relative timestamp of the most recent detection |
Source Types
Terracotta classifies modules by their source type:
| Source Type | Description | Example |
|---|---|---|
| Registry | Terraform Registry or private registry modules | hashicorp/consul/aws |
| Git | Git repository references (GitHub, GitLab, Bitbucket) | git::https://github.com/org/module.git |
| S3 | AWS S3 bucket sources | s3::https://s3-eu-west-1.amazonaws.com/bucket/module.zip |
| GCS | Google Cloud Storage sources | gcs::https://www.googleapis.com/storage/v1/modules/module.zip |
| HTTP | Generic HTTP/HTTPS URLs | https://example.com/module.zip |
Search & Filter
- Text search: Filter by module source name (case-insensitive)
- Source type filter: Narrow to a specific source type (registry, git, S3, GCS, HTTP)
Filter options are dynamically derived from the modules in your data — only source types that actually appear are shown.
Data Pipeline
Module data is collected automatically during the post-merge processing pipeline:
- When a PR is merged, Terracotta parses all
.tffiles formoduleblocks - Each module's
sourceattribute is classified by type (registry, git, S3, GCS, HTTP) - Module references are stored in the infrastructure graph with version and consumer metadata
- The Module Intelligence view aggregates across all repositories
No additional configuration is required — if you have connected repositories with Terraform modules, data populates automatically after merges.
Agent Voice
The Module Intelligence view includes an AI-generated narrative summarizing your module landscape — highlighting the most-used modules, version spread, and any modules that may need attention (e.g., widely-used modules with no version pinning).
TL;DR
- Module Intelligence inventories all external Terraform modules across your organization
- Sorted by consumer count — most-used modules surface first
- 5 source types: Registry, Git, S3, GCS, HTTP
- Search by module name and filter by source type
- Data populates automatically from post-merge processing — no setup required
- Each module shows consumer count, repo count, latest version, and last seen timestamp
Updated about 8 hours ago