TopGit
GitHub Repo Review

Terraform: a few loud opinions, mostly old

hashicorp/terraform
TTopGit review image for hashicorp/terraform
Review by Topgit.dev for hashicorp/terraform, with GitHub repository stats and README context.
Quick verdict

Reach for Terraform if you manage infrastructure across more than one provider and want a single declarative workflow with a plan step that shows every change before it happens. Skip it if you're all-in on one cloud (that cloud's native IaC may fit better), or if the 2023 relicense to the Business Source License is a dealbreaker — in which case the OpenTofu fork is the drop-in answer.

Stars
★ 50.2k
Forks
⑂ 10.6k
Contributors
👥 2.3k
Language
Go
License
See repository
Topic
Developer Tools
Updated
Nov 2026
Homepage
GitHub

Terraform has 50212 stars on GitHub, yet the discussion we could collect about it is thin and mostly old: Hacker News comments from 2014, 2015 and 2021, plus a couple of long GitHub issues. That is a sample of how some users talked at a few moments, not a reading of today's mood, and it is the limit of everything below.

The 2021 thread holds the sharpest opinions. @kevincox, 2021-06-08 wrote "I hate Terraform with a passion but it is probably the best tool out there for managing cloud infrastructure so I use it at work with no plans to replace it." Their complaint was specific: "The biggest downsides are the awful half-baked language and the awkwardness of modules". Others disagree about the language. @etxm, 2021-06-08 wrote "I think it’s a great language for infrastructure", and @jamesmishra, 2021-06-09 said "I believe in the Terraform way of doing things." They added that many people who dislike the Terraform language switch to Pulumi to write infrastructure in Python or JavaScript, which they specifically do not want. On speed, @Nilithus, 2021-06-08 pushed back on a claim that performance is bad: "Seems hard to blame a tool who's main execution path is potentially 100's of network IO requests with 3rd party API's." And @chousuke, 2021-06-08 said "I set up Terraform with libvirt for my local VM host; I think it's much better suited for managing infrastructure components than Ansible is."

The 2014 and 2015 comments are about coverage. @cheeseprocedure, 2014-07-28 found "Looks like you can't pass EC2 user-data to a launch config either, which is frustrating", while expecting a quick fix. @sciurus, 2015-01-30 wrote "I'd love to use Terraform but too much of what I use Cloudformation for isn't there."

The tracker is louder than the comment threads. In a GitHub issue opened on 2015-06-06, @shubhambhartiya, 2015-06-06 asked whether an RDS instance created from Terraform files can survive destroying the whole state; the capture lists it as still unresolved, at 169 comments and 2104 reactions. Another issue, #13022 from @glenjamin, 2017-03-23, is about using variables to configure the backend and sits at 315 comments and 1304 reactions. Both are heavily discussed, and the repository now lists 1931 open issues while its last push was 2026-11-11.

One more figure: 10593 forks have accumulated since the 2014-03-13 start of the project. GitHub's license field is empty here, while the README names the Business Source License 1.1 and the project description calls Terraform source-available.

Set against Pulumi, the difference jamesmishra names is the language: Terraform's own configuration syntax versus general-purpose code. Set against Ansible, chousuke's point is scope, with Terraform handling the infrastructure components themselves.

View on GitHub ↗

Related repositories

Source & attribution

Based on the official hashicorp/terraform GitHub repository, including its README and project metadata.

GitHub data · last synced Nov 12, 2026Reviewed by Henry
← Back to TopGit

Still deciding about terraform?

One click hands the question to an AI along with this page — see what it says about terraform.

GitHub