terraform-provider-stateful
Generic abstract stateful resources to manage arbitrary objects by executing arbitrary commands (by ashald)
terraform-provider-sops
A Terraform provider for reading Mozilla sops files (by carlpett)
terraform-provider-stateful | terraform-provider-sops | |
---|---|---|
1 | 4 | |
24 | 461 | |
- | - | |
10.0 | 2.8 | |
over 3 years ago | 3 months ago | |
Go | Go | |
The Unlicense | Mozilla Public License 2.0 |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.
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-stateful
Posts with mentions or reviews of terraform-provider-stateful.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-08-31.
-
HashiCorp silently amend Terraform Registry TOS
It's... effort consuming, but is doable and more like a 1-time effort.
A while ago I built an alternative plugin manager for Terraform (https://github.com/paraterraform/para) and explored the idea of distributed indices (where you just host a file in the repo as seen in https://github.com/ashald/terraform-provider-stateful/blob/m...).
So at the end of the day, it's either about the effort to inventory the current registry and find sources that are available, or do this on an ongoing as-needed basis (eg something like para would allow an index to be hosted in a github repo managed with PRs).
terraform-provider-sops
Posts with mentions or reviews of terraform-provider-sops.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-08-31.
-
[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
What are some alternatives?
When comparing terraform-provider-stateful and terraform-provider-sops you can also consider the following projects:
speakeasy - Speakeasy CLI - Enterprise developer experience for your API
sops - Simple and flexible tool for managing secrets