From c6f1942950265bdb59fe9312790bf4227ca60553 Mon Sep 17 00:00:00 2001 From: Max Vojtkov Date: Sun, 9 Aug 2026 12:49:11 +0300 Subject: [PATCH] Clarify which Terraform registry Gitea actually has Gitea lists "Terraform" among its package registries, which reads as if the provider could be published there. It stores remote state for the http backend -- not modules, not providers. --- .goreleaser.yml | 7 ++++--- README.md | 14 +++++++++----- 2 files changed, 13 insertions(+), 8 deletions(-) diff --git a/.goreleaser.yml b/.goreleaser.yml index 441a255..e32e11e 100644 --- a/.goreleaser.yml +++ b/.goreleaser.yml @@ -1,8 +1,9 @@ # Publishes provider binaries to a Gitea release. # -# Gitea has no Terraform provider registry -- that protocol is not one of the -# ~20 package types it implements -- so these archives are consumed through a -# filesystem mirror instead. See "Installing" in the README. +# These archives are consumed through a filesystem mirror, because Gitea cannot +# serve the provider protocol. Its package registry list does include +# "Terraform", but that one stores remote state for the `http` backend -- it is +# neither a module nor a provider registry. See "Installing" in the README. # # The archive names follow HashiCorp's convention # (terraform-provider-NAME_VERSION_OS_ARCH.zip) because a filesystem mirror diff --git a/README.md b/README.md index f494d19..6dc3e6d 100644 --- a/README.md +++ b/README.md @@ -57,11 +57,15 @@ resource "dokploy_domain" "api" { ## Installing This provider is distributed through -[Gitea releases](https://gitea.coolify.vojtkov.dev/usr_unknown/terraform-provider-dokploy/releases), -not a Terraform registry — Gitea implements about twenty package registries, -and the Terraform provider protocol is not one of them. So installation goes -through a **filesystem mirror**, which is Terraform's supported way to use a -provider that no registry serves. +[Gitea releases](https://gitea.coolify.vojtkov.dev/usr_unknown/terraform-provider-dokploy/releases) +and installed through a **filesystem mirror**, which is Terraform's supported +way to use a provider that no registry serves. + +Gitea *does* list "Terraform" among its package registries, which is +misleading here: that one stores [remote +state](https://docs.gitea.com/usage/packages/terraform) for the `http` backend. +It is not a module registry and not a provider registry, and there is no Gitea +endpoint that can serve the provider protocol `terraform init` speaks. ### From a release