120

Terraform, Vault, Nomad etc by HashiCorp moving away from Open Source (thenewstack.io)

submitted 10 months ago by thewitchofcalamari to c/technology@beehaw.org

27 comments fedilink hide all child comments

HashiCorp is moving its products previously licensed as Open Source away from it to Business Source License (BSL) moving forward
Terraform is a popular Infrastructure as Code tool used for provisioning cloud resources like AWS, Azure among others
Terraform version 1.5.5 and earlier are still open source
there is a push for a community maintained open source fork if this decision is not reversed, OpenTF

Gruntwork response on the problem with BSL

https://blog.gruntwork.io/the-future-of-terraform-must-be-open-ab0b9ba65bca?gi=be31818bcbaf
Gruntwork is a creator of the tool Terragrunt which is an open source wrapper around Terraform to provide some additional tools for it

you are viewing a single comment's thread
view the rest of the comments

[-] rolaulten@startrek.website 12 points 10 months ago

I for one am recommending pulumi for any of my teams new infrastructure needs.

[-] 1984@lemmy.today 10 points 10 months ago* (last edited 10 months ago)

I used pulumi but it's much worse than terraform. I didn't used to think so before I learned terraform however.

My main reason to dislike pulumi is that you have to work around it's async behavior in python. Maybe it's better and more natural if you use typescript, but I had to constantly wrap methods in Outputs and other things to get the code to work.

I had to adapt my code to how pulumi worked all the time. With terraform, I just write it and it works.

[-] rolaulten@startrek.website 1 points 10 months ago

So I'm using it with Python. For me it's able to do some stuff that terrafom never would be able to (Ive got a spot where resources are generated for each file/object on disk).

[-] 1984@lemmy.today 1 points 10 months ago

Give me an example... What file on disk are you generating a pulumi resource from?

[-] rolaulten@startrek.website 1 points 10 months ago

We've got it rigged up for aws sso. Each department can make any number of permissions sets (and link to any number of groups). The config for that is all stored in git (with code owners configured so you can only mess up your own stuff).