tl;dr: Available Terraform/OpenTofu Provider network mirroring service.
Hermit Crab provides a stable and reliable Terraform/OpenTofu Provider network mirror service.
This tool is maintained by Seal.
sequenceDiagram
actor tf as terraform init
participant hc as Hermit Crab
participant tfreg as Terraform Registry
participant stg as Provider Package Storage
tf ->> hc: list available versions
alt not found
hc ->> tfreg: list available versions
tfreg -->> hc:
hc ->> hc: save
end
hc -->> tf: {"versions":{"2.0.0":{},"2.0.1":{}}}
tf ->> hc: list available installation packages
alt not found
par
hc ->> tfreg: find darwin/amd64 provider package
tfreg -->> hc:
hc ->> hc: save
and
hc ->> tfreg: find linux/amd64 provider package
tfreg -->> hc:
hc ->> hc: save
end
end
hc -->> tf: {"archives": {"darwin_amd64":{},"linux_amd64":{}}
tf ->> hc: download platform provider package, like darwin/amd64
alt not found
par not downloading
hc ->> stg: download
stg -->> hc:
hc ->> hc: store
and downloading
hc ->> hc: wait until downloading finished
end
end
hc -->> tf: ***.zip
When we drive Terraform at some automation scenarios, like CI, automatic deployment, etc., we need to download the Provider plugins from the internet by init command.
Depending on Terraform Provider Registry Protocol, we may download a plugin that is not cached from an unstable networking remote.
To mitigate the effect of unstable networking, there are two ways to solve this: Implied Mirroring and Network Mirroring.
As far as Implied Mirroring is concerned, it works well when a Provider matches the Version Constraints. However, this mode fails when the version is not cached in the local file directory.
╷
│ Error: Failed to query available provider packages
│
│ Could not retrieve the list of available versions for provider
What's even more troublesome is that if the version changes, we need to continuously maintain this local file directory.
Network Mirroring, different from Implied Mirroring, can maintain all versions(including the latest) at a nearby network and allows distributed Terraform working agents to share the same mirroring package.
Hermit Crab implements the Terraform/OpenTofu Provider Registry Protocol and acts as a mirroring service.
Hermit Crab can be easily served through Docker.
docker run -d --restart=always -p 80:80 -p 443:443 sealio/hermitcrabHermit Crab saves the mirrored(downloaded) packages in the /var/run/hermitcrab directory by default, which can be persisted by mounting a volume.
docker run -d --restart=always -p 80:80 -p 443:443 \
-v /tmp/hermitcrab:/var/run/hermitcrab \
sealio/hermitcrabHermit Crab manages the archives as the following layer structure, which is absolutely compatible with the output of terraform providers mirror/tofu providers mirror.
/var/run/hermitcrab/data/providers
├── /<HOSTNAME>
│ ├── /<NAMESPACE>
│ │ ├── /<TYPE>
│ │ │ ├── terraform-provider-<TYPE>_<VERSION>_<OS>_<ARCH>.zip
Hermit Crab also can reuse the mirroring providers prepared by terraform providers mirror/tofo providers mirror.
terraform providers mirror /tmp/providers-plugins
docker run -d --restart=always -p 80:80 -p 443:443 \
-v /tmp/providers-plugins:/usr/share/terraform/providers/plugins \
sealio/hermitcrabTerraform/OpenTofu Provider Network Mirror protocol wants HTTPS access, Hermit Crab provides multiple ways to achieve this.
-
Use the default self-signed certificate, no additional configuration is required.
Since Terraform always verifies the certificate insecure or not, under this mode, we need to import the self-signed certificate into the trusted certificate store.
# download the self-signed certificate echo quit | openssl s_client -showcerts -servername <YOUR_SERVER> -connect <YOUR_ADDRESS> 2>/dev/null | openssl x509 -outform PEM >server.pem
-
Using ACME to gain a trusted certificate, need a domain name and a DNS configuration.
docker run -d --restart=always -p 80:80 -p 443:443 \ -e SERVER_TLS_AUTO_CERT_DOMAINS=<YOUR_DOMAIN_NAME> \ sealio/hermitcrab
-
Use a custom certificate.
docker run -d --restart=always -p 80:80 -p 443:443 \ -v /<YOUR_PRIVATE_KEY_FILE>:/etc/hermitcrab/ssl/key.pem \ -v /<YOUR_CERT_FILE>:/etc/hermitcrab/ssl/cert.pem \ -e SERVER_TLS_PRIVATE_KEY_FILE=/etc/hermitcrab/ssl/key.pem \ -e SERVER_TLS_CERT_FILE=/etc/hermitcrab/ssl/cert.pem \ sealio/hermitcrab
Also support to launch from Helm Chart.
# latest version
helm install my-release oci://ghcr.io/seal-io/helm-charts/hermitcrab
# with specific version
helm install my-release oci://ghcr.io/seal-io/helm-charts/hermitcrab --version <VERSION>After setting up Hermit Crab, you can make the Terraform/OpenTofu CLI Configuration File as below to use the mirroring service.
provider_installation {
network_mirror {
url = "https://<ADDRESS>/v1/providers/"
}
}Hermit Crab is not a Terraform Registry, although implementing these protocols is not difficult, there are many options that you can choose from, like HashiCorp Terraform Enterprise, JFrog Artifactory, etc.
Hermit Crab cannot mirror Terraform Module, since obtaining Terraform modules is diverse, like Git, HTTP URLs, S3 Bucket and so on, it's hard to provide a unified way to mirror them.
Hermit Crab doesn't support rewriting the provider hostname, which is a rare case and may make template/module reusing difficult. One possible scenario is that there is a private Terraform Registry in your network, and you need to use the community template/module without any modification.
Hermit Crab automatically synchronizes the in-use versions per 30 minutes, if the information update occurs during sleep, we can manually trigger the synchronization by sending a PUT request to /v1/providers/sync.
Hermit Crab only performs a checksum verification on the downloaded archives. For archives that already exist in the implied or explicit directory, checksum verification is not performed.
Hermit Crab allows downloading the archives matching ^terraform-provider-(?P<type>\w+)[_-](?P<version>[\w|\\.]+)[_-](?P<os>[a-z]+)[_-](?P<arch>[a-z0-9]+)([_-].*)?\.zip$, but it is recommended to follow the Terraform Release Rules.
Copyright (c) 2023 Seal, Inc.
Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at LICENSE file for details.
Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.