Terraform Module Reuse and Supply Chain

When to use

Invoke when establishing how Terraform modules are versioned, published, consumed, and trusted; when introducing a module registry; or when auditing/hardening provider and module dependency provenance before reuse scales across teams.

Do not use for: repo/module structure (use terraform-module-and-repository-scaffold), state backend/secret handling (use terraform-state-and-secret-management), pre-merge plan/policy gates (use terraform-plan-gate-and-policy-as-code), or apply/promotion orchestration (use terraform-apply-and-promotion-mechanics).

Inputs

Required:

• An existing repo/module scaffold (from terraform-module-and-repository-scaffold) defining module boundaries and structure.
• Approved architecture/security decisions on dependency provenance, allowed sources, and supply-chain requirements.
• Approved architecture/operations decisions on versioning, deprecation, and change-communication expectations.

Optional: