terraform-provider-sops
terraform-provider-stateful
| terraform-provider-sops | terraform-provider-stateful | |
|---|---|---|
| 4 | 1 | |
| 461 | 24 | |
| - | - | |
| 2.8 | 10.0 | |
| 2 months ago | about 3 years ago | |
| Go | Go | |
| Mozilla Public License 2.0 | The Unlicense |
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
terraform-provider-stateful
-
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).
What are some alternatives?
sops - Simple and flexible tool for managing secrets
speakeasy - Speakeasy CLI - Enterprise developer experience for your API
terragrunt - Terragrunt is a thin wrapper for Terraform that provides extra tools for working with multiple Terraform modules.
terraform-pr
pre-commit-terraform - pre-commit git hooks to take care of Terraform configurations 🇺🇦
terraform-provider-openstack - Terraform OpenStack provider
atlantis - Terraform Pull Request Automation
terraform-provider-aws - The AWS Provider enables Terraform to manage AWS resources.
terraform-best-practices - Terraform Best Practices for AWS users
terraform-provider-airbyte - Terraform Provider for Airbyte API
terraform-null-label - Terraform Module to define a consistent naming convention by (namespace, stage, name, [attributes])
para - Para - community plugin manager and a "swiss army knife" for Terraform/Terragrunt - just 1 tool to facilitate all your workflows.