| citizen | roadmap | |
|---|---|---|
| 2 | 4 | |
| 609 | 371 | |
| - | - | |
| 4.4 | 10.0 | |
| about 1 month ago | 8 months ago | |
| JavaScript | ||
| Mozilla Public License 2.0 | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
citizen
-
OpenTF Repository is now Public
> Do you mean you'd like a self-contained binary to run a private provider/modules registry?
Yes, indeed. But it seems the problem more was something with Google's algorithm, I swear a month ago this here [1] wasn't on the first page when searching for "terraform private provider registry".
That also answered the second question.
[1] https://github.com/outsideris/citizen
-
Introducing tfmodule.com , A Stand Alone Private Terraform Module Registry
Separately, what does your project offer that e.g. Citizen does not?
roadmap
-
OpenTF Repository is now Public
Good to see, waiting on https://github.com/opentffoundation/roadmap/issues/8 so can do some testing (yes can build from source, but I'd rather use the releases)
-
HashiCorp silently amend Terraform Registry TOS
Not the OP, but I suspect HN has trimmed the anchor link.
> https://github.com/opentffoundation/roadmap/issues/24#issuec...
That's the comment that made the issue clear -- specifically TOS were amended for https://registry.terraform.io to state:
> You may download providers, modules, policy libraries and/or other Services or Content from this website __solely for use with, or in support of, HashiCorp Terraform.__
ie., it looks like the intent is "You can't use OpenTF with registry.terraform.io".
IMO, that feels a little petty. But, I guess if OpenTF is taking a position of "Use us instead of Terraform", then they shouldn't expect to get the usage of Hashicorps infra.
-
OpenTF Announces Fork of Terraform
Making sure there aren't any trademark infringements left, that we have some basic community process in place, etc.
There's unfortunately a bunch of these things we have to do before we can publish. We created a public roadmap repo if you'd like to track the progress[0]. We're doing our best to make it public as soon as possible.
[0]: https://github.com/opentffoundation/roadmap/milestones
Disclaimer: Work at Spacelift, and currently temporary Technical Lead of the OpenTF Project, until it's committee-steered.
What are some alternatives?
Terraform-Guide - Terraform Guide
spacectl - Spacelift client and CLI
opentf - OpenTofu lets you declaratively manage your cloud infrastructure. [Moved to: https://github.com/opentofu/opentofu]
manifesto - The OpenTF Manifesto expresses concern over HashiCorp's switch of the Terraform license from open-source to the Business Source License (BSL) and calls for the tool's return to a truly open-source license.
terralist - Terraform Private Registry for modules and providers manageable from a REST API
boring-registry - Terraform Provider and Module Registry
terraform-provider-airbyte - Terraform Provider for Airbyte API
git-absorb - git commit --fixup, but automatic
terraform-pr
github.packages.tf - Bridge between GitHub Releases and Terraform