2017-08-18 06:19:49 +02:00
|
|
|
---
|
|
|
|
layout: "registry"
|
|
|
|
page_title: "Terraform Registry - Private Registry"
|
|
|
|
sidebar_current: "docs-registry-private"
|
|
|
|
description: |-
|
2019-08-07 00:28:03 +02:00
|
|
|
Terraform can load private modules from private registries via Terraform Cloud.
|
2017-08-18 06:19:49 +02:00
|
|
|
---
|
|
|
|
|
2018-02-07 18:15:55 +01:00
|
|
|
# Private Registries
|
2017-08-18 06:19:49 +02:00
|
|
|
|
|
|
|
The registry at [registry.terraform.io](https://registry.terraform.io)
|
2018-02-07 18:15:55 +01:00
|
|
|
only hosts public modules, but most organizations have some modules that
|
|
|
|
can't, shouldn't, or don't need to be public.
|
2017-08-18 06:19:49 +02:00
|
|
|
|
2018-02-07 18:15:55 +01:00
|
|
|
You can load private modules [directly from version control and other
|
|
|
|
sources](/docs/modules/sources.html), but those sources don't support [version
|
2019-03-13 19:07:10 +01:00
|
|
|
constraints](/docs/configuration/modules.html#module-versions) or a browsable
|
2018-02-07 18:15:55 +01:00
|
|
|
marketplace of modules, both of which are important for enabling a
|
|
|
|
producers-and-consumers content model in a large organization.
|
2017-08-18 06:19:49 +02:00
|
|
|
|
2018-02-07 18:15:55 +01:00
|
|
|
If your organization is specialized enough that teams frequently use modules
|
|
|
|
created by other teams, you will benefit from a private module registry.
|
2017-11-01 00:05:22 +01:00
|
|
|
|
2019-08-07 00:28:03 +02:00
|
|
|
## Terraform Cloud's Private Registry
|
2017-11-01 00:05:22 +01:00
|
|
|
|
2019-08-07 00:28:03 +02:00
|
|
|
[Terraform Cloud](https://www.hashicorp.com/products/terraform)
|
2018-02-07 18:15:55 +01:00
|
|
|
includes a private module registry, available at both Pro and Premium tiers.
|
2017-11-01 00:05:22 +01:00
|
|
|
|
2018-02-07 18:15:55 +01:00
|
|
|
It uses the same VCS-backed tagged release workflow as the Terraform Registry,
|
2019-08-07 00:28:03 +02:00
|
|
|
but imports modules from your private VCS repos (on any of Terraform Cloud's supported VCS
|
2018-02-07 18:15:55 +01:00
|
|
|
providers) instead of requiring public GitHub repos. You can seamlessly
|
|
|
|
reference private modules in your Terraform configurations (just include a
|
2019-08-07 00:28:03 +02:00
|
|
|
hostname in the module source), and Terraform Cloud's UI provides a searchable marketplace
|
2018-02-07 18:15:55 +01:00
|
|
|
of private modules to help your users find the code they need.
|
2017-11-01 00:05:22 +01:00
|
|
|
|
2019-08-07 00:28:03 +02:00
|
|
|
[Terraform Cloud's private module registry is documented here.](/docs/cloud/registry/index.html)
|
2017-08-18 06:19:49 +02:00
|
|
|
|
2018-02-07 18:15:55 +01:00
|
|
|
## Other Private Registries
|
2017-08-18 06:19:49 +02:00
|
|
|
|
2018-02-07 18:15:55 +01:00
|
|
|
Terraform can use versioned modules from any service that implements
|
|
|
|
[the registry API](/docs/registry/api.html).
|
|
|
|
The Terraform open source project does not provide a server implementation, but
|
|
|
|
we welcome community members to create their own private registries by following
|
|
|
|
the published protocol.
|
2017-08-18 06:19:49 +02:00
|
|
|
|