We definitely have to experiment a lot more with the licenses of OSS but keep in mind that it's going to also require time for projects to use the new licenses and figure out what side effects they have.
I think it's also related to the fact that the US and the UK don't have ID documents the way that a lot of EU countries have and many people don't have passports, so the only other way left that has an API and is checking periodically that you are who you claim is your bank before giving you a fresh credit card
Yeah, it's a shame because otherwise the library is really nice and could have become the default HTTP library, but it feels like someone will manage to inject some weird behaviour soon and half the planet will be compromised
or the mismatch between request and response when using HTTP, or the overhead of using RPCs to protect against the previous scenario, or the issue of updating one microservice and not updating all the dependents
I mean, microservices split the code into smaller chunks but now lots of little pieces communicate over the network and unless you are using some form of RPC, this communication channels are not typed and there's a lot more stuff that could go wrong (packets dropped, DNS not resolving). Plus you could update one microservice and not update its dependents. I think a lot of people jumped on the hype without realising that it's a trade-off
I built a live Terraform visualizer, but users wanted an AI to write and audit their HCL. Here’s how we did it without access to state or secrets
Been writing TF since 0.11 and survived the 0.12 migration. Built multi-cloud architectures (AWS B2B banking, GCP peering, Crossplane self-service). After all this time Terraform never gets much easier, you just build more complicated headaches.
Yes, Terraform is the `right` way of doing things. It allows you to review changes before applying but at the cost of being obscure. Most SWEs don't want to deal with it and even infra engineers will occasionally do some click-ops and then reconcile.
Originally, I built a tool to auto-generate architecture diagrams from Terraform code, mostly because I hated having to manually update diagrams and expected other people did as well. After releasing it and talking to early users, I realised seeing the infrastructure was an issue but it wasn't the main issue. Changing it safely was. As an SRE, I really wanted to create a tool to help devs self-serve infrastructure and to speed up infra changes without having to add another abstraction layer on top. So, we created Grafos.ai and added an agentic layer to explain and modify the code, as well as a policy management system so you can define all of your organisation's policies, automatically run them against the changes, and also update your terraform to match them easily.
We didn’t want to create an invasive and potentially destructive AI and give it to your infrastructure and we didn't want to break your development processes, so we built some ground rules into it.
* Its doesn't do arbitrary code changes, it creates PRs so you can double check your terraform before anything is applied
* Zero state or secret access, so you don’t have to trust it at all, it’s just your terraform code
* Live visualisation so you can instantly see actually what changes are being proposed
* Natural language guardrails and policies so you can make sure all changes are in line with your organisation's guardrails and style guides.
I’d love for you to try it and tear it apart, it’s early days and we’re shipping features and changes literally everyday so any feedback good or bad would be amazing!