roadmap
terraform-provider-airbyte
| roadmap | terraform-provider-airbyte | |
|---|---|---|
| 4 | 2 | |
| 371 | 36 | |
| - | - | |
| 10.0 | 7.1 | |
| 8 months ago | 13 days ago | |
| Go | ||
| - | MIT License |
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.
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.
terraform-provider-airbyte
- Show HN: OpenAPI to Terraform Provider Code Generation
-
HashiCorp silently amend Terraform Registry TOS
In my mind the analagous behaviour would be if the golang checksum database added in license terms that stated "you need to abide by a BSL to use data from this service". What that actually would mean is so nebulous that it feels threatening.
[0] Source: https://registry.terraform.io/v1/providers/airbytehq/airbyte...
[1] Source: https://github.com/airbytehq/terraform-provider-airbyte/tree... gzipped : ~300 resources, ~300 data sources
(NB: in airbyte's case the TF Provider was generated from a ~150Kb OpenAPI spec via https://speakeasyapi.dev: implying docs could be compressed even more)
What are some alternatives?
spacectl - Spacelift client and CLI
terraform-provider-sops - A Terraform provider for reading Mozilla sops files
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.
para - Para - community plugin manager and a "swiss army knife" for Terraform/Terragrunt - just 1 tool to facilitate all your workflows.
opentf - OpenTofu lets you declaratively manage your cloud infrastructure. [Moved to: https://github.com/opentofu/opentofu]
terraform-pr
terraform-provider-stateful - Generic abstract stateful resources to manage arbitrary objects by executing arbitrary commands
github.packages.tf - Bridge between GitHub Releases and Terraform
speakeasy - Speakeasy CLI - Enterprise developer experience for your API
git-absorb - git commit --fixup, but automatic
terraform-provider-hashicu