Private provider hosting

I use alot of community modules with Though using community modules requires building a docker image with many of the providers rolled into the image. And if an update of a provider is needed, again we must roll a new image. Is there a way to point terraform at a proxy to search for self-maintained providers externally from terraform? Just to mock the behavior of official providers?

Looks like something is in the works?

This is what I was lookin for But from the sounds if (Private provider registry) it doesn’t yet look ready.

Hi @mhumeSF,

Features for this are indeed planned for the 0.13 line of releases, and work is currently underway. The relevant functionality will appear gradually throughout the 0.13 minor releases, with the initial release establishing the new decentralized naming scheme for providers that the other functionality will depend on, so that it can become possible to state in your configuration that you want to use a provider built by someone other than HashiCorp:

terraform {
  required_providers {
    aws = {
      source  = "hashicorp/aws"
      version = "~> 2.4.0"
    example = {
      source  = "third-party/example"
      version = "~> 2.1.0"

The public Terraform Registry at will become capable of indexing community providers in addition to the official providers it already indexes.

If you’re interested in some of the internal details around this, I wrote up some notes about the internal technical design in an article in my personal blog.