terraform-provider-sops
roadmap
| terraform-provider-sops | roadmap | |
|---|---|---|
| 4 | 4 | |
| 461 | 371 | |
| - | - | |
| 2.8 | 10.0 | |
| 2 months ago | 8 months ago | |
| Go | ||
| 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.
terraform-provider-sops
-
[Datadog in Kubernetes] Storing secrets in service annotations with secret management
Supposing it's actually stored raw in the service (which I assume it won't be), I plan to just use my current Terraform configuration that uses kubernetes_service and SOPS. I've avoided storing secrets within the code (which is the absolute worst, I know lol), but then they're stored rawly in the service.
-
HashiCorp silently amend Terraform Registry TOS
"https://github.com/carlpett/terraform-provider-sops/releases..."
-
Terraform best practices?
I like using sops + terraform-provider-sops for storing secrets alongside my code in a GitOps fashion. That has been a great workflow for me and allows you to treat your secrets as code which has a lot of benefits.
- A Terraform plugin for using files encrypted with Mozilla sops
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?
sops - Simple and flexible tool for managing secrets
spacectl - Spacelift client and CLI
terragrunt - Terragrunt is a thin wrapper for Terraform that provides extra tools for working with multiple Terraform modules.
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.
pre-commit-terraform - pre-commit git hooks to take care of Terraform configurations 🇺🇦
opentf - OpenTofu lets you declaratively manage your cloud infrastructure. [Moved to: https://github.com/opentofu/opentofu]
atlantis - Terraform Pull Request Automation
terraform-provider-airbyte - Terraform Provider for Airbyte API
terraform-best-practices - Terraform Best Practices for AWS users
terraform-pr
terraform-null-label - Terraform Module to define a consistent naming convention by (namespace, stage, name, [attributes])
github.packages.tf - Bridge between GitHub Releases and Terraform