terraform-provider-sops
terraform-pr
| terraform-provider-sops | terraform-pr | |
|---|---|---|
| 4 | 1 | |
| 461 | - | |
| - | - | |
| 2.8 | - | |
| 2 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
terraform-pr
-
HashiCorp silently amend Terraform Registry TOS
Even though this will likely prevent OpenTF from connecting to registry.terraform.io to get plugins, the source code for most (all?) plugins is still open source and actually stored on GitHub (e.g. https://github.com/terraform-provider-openstack/terraform-pr...).
More work for OpenTF to get up and running, but also feels reasonable that HashiCorp wouldn't allow connecting to their service.
What are some alternatives?
sops - Simple and flexible tool for managing secrets
roadmap
terragrunt - Terragrunt is a thin wrapper for Terraform that provides extra tools for working with multiple Terraform modules.
terraform-provider-stateful - Generic abstract stateful resources to manage arbitrary objects by executing arbitrary commands
pre-commit-terraform - pre-commit git hooks to take care of Terraform configurations 🇺🇦
terraform-provider-airbyte - Terraform Provider for Airbyte API
atlantis - Terraform Pull Request Automation
para - Para - community plugin manager and a "swiss army knife" for Terraform/Terragrunt - just 1 tool to facilitate all your workflows.
terraform-best-practices - Terraform Best Practices for AWS users
terraform-provider-openstack - Terraform OpenStack provider
terraform-null-label - Terraform Module to define a consistent naming convention by (namespace, stage, name, [attributes])
terraform-docs - Generate documentation from Terraform modules in various output formats