terraform-provider-sops
speakeasy
terraform-provider-sops | speakeasy | |
---|---|---|
4 | 7 | |
461 | 140 | |
- | 13.6% | |
2.8 | 9.8 | |
2 months ago | 4 days ago | |
Go | Go | |
Mozilla Public License 2.0 | GNU General Public License v3.0 or later |
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
speakeasy
-
Generating Code Without Generating Technical Debt?
I’ve built conviction that code generation only gets useful in the long term when it is entirely deterministic, or filtered through humans. Otherwise it is almost always technical debt. Hence LLM code generation products are a cool toy, but no sensible teams will use them without an amazing “Day 2” workflow.
As an example, in my day job (https://speakeasyapi.dev), we sell code generation products using the OpenAPI specification to generate downstream artefacts (language SDKs, terraform providers, markdown documentation). The determinism makes it useful — API updates propagate continuously from server code, to specifications, then to the SDKs / providers / docs site. There are no breaking changes because the pipeline is deterministic and humans are in control of the API at the start. The code generation itself is just a means to an end : removing boilerplate effort and language differences by driving it from a source of truth (server api routes/types). Continuously generated, it is not debt.
We’ve put a lot of effort into trying to make an LLM agent useful in this context. However giving them control of generated code directly means it’s hard to keep the “no breaking changes”, and “consistency” restrictions that’s needed to make code generation useful.
The trick we’ve landed on to get utility out of an LLM in a code generation task, is to restrict it to manipulating a strictly typed interface document, such that it can only do non-breaking things to code (e.g. adjust comments / descriptions / examples) by making changes through this interface.
- 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)
-
OpenAPI v4 Proposal
I'm working on a company https://speakeasyapi.dev/ with the goal helping companies in this ecosystem get great production quality client sdks, terraform providers, cli(s) and all the developer surfaces you may want supported for our API. We also manage the spec and publishing workflow for you so all you have to do is build your API and we'll do the rest.
Feel free to email me at [email protected] or join our slack (https://join.slack.com/t/speakeasy-dev/shared_invite/zt-1cwb...) . We're in open beta and working with a few great companies already and we'd be happy for you to try out the platform for free!
-
Idiomatic Golang Client SDK Generation for OpenAPI APIs
Hi all I am a founding engineer for a API Experience company called Speakeasy - speakeasyapi.dev and we have recently released a Client SDK Generator for APIs using OpenAPI 3.0.X documents (soon to support 3.1). The generator will generate idiomatic Golang SDKs (along with other languages) that feel natural to use, easy to mock, and just work. The generator is free to use and can be run via a standalone golang built CLI with no external dependencies that can be easily installed as a binary or via homebrew (mac & linux). Check it out here https://github.com/speakeasy-api/speakeasy. If you have any questions or want to get in touch to see how Speakeasy can help you improve your APIs, just let me know!
-
Idiomatic SDKs for OpenAPI
The generator has been battle tested on thousands of APIs and we are sharing the results in our github repo. If you want to try it out on your own, download the CLI or brew install and get started in minutes:
What are some alternatives?
sops - Simple and flexible tool for managing secrets
fern - 🌿 Stripe-level SDKs and Docs for your API
terragrunt - Terragrunt is a thin wrapper for Terraform that provides extra tools for working with multiple Terraform modules.
openapi-codegen - A tool for generating code base on an OpenAPI schema.
pre-commit-terraform - pre-commit git hooks to take care of Terraform configurations 🇺🇦
terraform-provider-stateful - Generic abstract stateful resources to manage arbitrary objects by executing arbitrary commands
atlantis - Terraform Pull Request Automation
taxilang - Taxi is a language for describing APIs, data models, and how everything relates
terraform-best-practices - Terraform Best Practices for AWS users
para - Para - community plugin manager and a "swiss army knife" for Terraform/Terragrunt - just 1 tool to facilitate all your workflows.
terraform-null-label - Terraform Module to define a consistent naming convention by (namespace, stage, name, [attributes])
oatx - Generator-less JSONSchema types straight from OpenAPI spec