terraform-provider-sops
terraform-provider-airbyte
| terraform-provider-sops | terraform-provider-airbyte | |
|---|---|---|
| 4 | 2 | |
| 461 | 36 | |
| - | - | |
| 2.8 | 7.1 | |
| 2 months ago | 9 days ago | |
| Go | Go | |
| Mozilla Public License 2.0 | 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.
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-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?
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.
para - Para - community plugin manager and a "swiss army knife" for Terraform/Terragrunt - just 1 tool to facilitate all your workflows.
pre-commit-terraform - pre-commit git hooks to take care of Terraform configurations 🇺🇦
terraform-pr
atlantis - Terraform Pull Request Automation
terraform-provider-stateful - Generic abstract stateful resources to manage arbitrary objects by executing arbitrary commands
terraform-best-practices - Terraform Best Practices for AWS users
speakeasy - Speakeasy CLI - Enterprise developer experience for your API
terraform-null-label - Terraform Module to define a consistent naming convention by (namespace, stage, name, [attributes])
terraform-provider-hashicu