A lightweight Terraform registry proxy that serves provider releases hosted on GitHub.
terraform-registry is a lightweight proxy registry for Terraform that serves provider releases hosted on GitHub repositories. It enables organizations to host private Terraform provider registries or distribute custom builds of providers from forks by dynamically generating the correct registry responses based on GitHub release assets. The project solves the problem of needing a private, self-hosted registry for Terraform providers without the complexity of running a full registry implementation.
DevOps engineers and platform teams who need to host private Terraform provider registries for internal use or distribute custom provider builds from forks. Organizations using GitHub or GitHub Enterprise for hosting provider binaries will find this particularly useful.
Developers choose terraform-registry because it provides a simple, lightweight alternative to running a full Terraform registry, with minimal configuration and seamless integration with GitHub's release infrastructure. Its proxy-based approach reduces complexity while maintaining full compatibility with Terraform's provider installation protocol.
Terraform registry to serve arbitrary Terraform provider releases hosted on Github
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Dynamically generates registry responses from GitHub releases, eliminating manual metadata management, as described in the 'how it works' section.
Supports GitHub Enterprise Server through environment variables like GITHUB_ENTERPRISE_URL, providing flexibility for corporate environments.
Deploys as a Docker image to any hosting location, minimizing infrastructure overhead, per the deployment instructions.
Enables easy release of custom provider builds from forks, as shown in the example usage for distributing modified versions.
Only supports Terraform providers, not modules, which is a current limitation admitted in the README, restricting comprehensive registry use.
Entirely reliant on GitHub for hosting release assets, making it incompatible with other platforms like GitLab or Bitbucket.
Requires a signkey.asc file with PGP public keys for each release, adding setup and maintenance overhead for teams.