I’ll try: Terraform replaces all the actions you’d do in the AWS (or other cloud provider) console or API with declarative configuration code. This means you can parametrize it, version control it, compose it, etc. and generally treat it like code.
It would be overkill for many things that have a single, fairly static configuration, but for things like ensuring that a dev and prod cluster have the same configuration, it’s a lifesaver.
Re:On the Weaponisation of Open Source
by fxtentacle on Saturday March 19, 2022 @07:01AM
(#30732810)
That is a great summary :) and it highlights the value proposition that I was missing:
Version Control for Cloud Configurations
It is also awesome, easy to use and very convenient. If you are configuring anything through AWS web GUI, you should give Terraform a go, you won't regret it.
(not affiliated in any way, just a happy user)
> 95% of all programmers can't
That's a lot of people who can.
Re:On the Weaponisation of Open Source
by hansel_der on Saturday March 19, 2022 @07:23AM
(#30732922)
about as much as ferrari owners.
i don't know any, but they sure do exist
Case in point, I have no idea. I know it's something related to the cloud but none of my clients are using it.
And their Wikipedia article is filled with buzzwords and no explanation of what it does, which doesn't exactly give me confidence that it'll be useful for regular companies. "Infrastructure as code"... so Ansible or docker compose? In any case, you don't need it if 2 HA bare metal servers do the job.