113

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

submitted 2 years ago by thewitchofcalamari@bookwormstory.social to c/technology@beehaw.org

22 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

all 29 comments

sorted by: hot top controversial new old

[-] 1984@lemmy.today 50 points 2 years ago* (last edited 2 years ago)

[removed by mod]

[-] rolaulten@startrek.website 12 points 2 years ago

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

[-] jarfil@beehaw.org 10 points 2 years ago

I wonder how many of those "open source developers", are actually employees of the same companies HashiCorp is accusing now of competing against them. No company is going to pay their employees to contribute to a piece of software, that they then have to buy a license for... so this can very well mean that HashiCorp is cutting off contributions from the same people most capable of contributing in the first place.

[-] pkulak@beehaw.org 4 points 2 years ago

No, just new versions.

[-] jherazob@beehaw.org 16 points 2 years ago

We were considering Vault, I guess we'll look into alternatives now, are there any decent Free Software ones in the first place?

[-] thewitchofcalamari@bookwormstory.social 4 points 2 years ago* (last edited 2 years ago)

ive not done secrets management before but i came across this list on hackernews, a few non-cloud ones use open source license https://news.ycombinator.com/item?id=37133054#37151218

but another user there have mentioned that while most of them integrate with Kubernetes and AWS, short lived DB credentials are not in any of those listed

[-] rothaine@beehaw.org 2 points 2 years ago

I'm not an infra dev, but a previous project used SOPS and it seemed alright

[-] devious@programming.dev 2 points 2 years ago

I've been using Infisical recently and I like it a lot.

[-] meteokr@community.adiquaints.moe 13 points 2 years ago

What a shame.

[-] jet@hackertalks.com 12 points 2 years ago* (last edited 2 years ago)

[removed by mod]

[-] robyoung@beehaw.org 5 points 2 years ago

The integrations with other services are implemented in plugins which are separate programs, that are installed separately, and communicate with the core over RPC. I would imagine these plugins can continue to be licensed however their owners choose. I think this license change just applies to core.

[-] Bitrot@lemmy.sdf.org 4 points 2 years ago

I’m not as familiar with MPLv2 but I don’t think they can with contributions to the fork. Since those contributions won’t be part of the original “we own all your work” agreement they couldn’t simply close source those contributions.

[-] jarfil@beehaw.org 1 points 2 years ago

From the BSL FAQ:

Q: I have written a code patch to a BSL project and would like the BSL vendor to maintain the code as part of the BSL project. How do I contribute it?

A: License your code using the “new BSD” license or dedicate it to the public domain. Code contributions under “new BSD” is compatible with BSL. See BSD on Wikipedia.

That would seem to rule out the MPLv2.

[-] Bitrot@lemmy.sdf.org 2 points 2 years ago* (last edited 2 years ago)

That is for continuing contributions to the commercial project, the fork should be using the old license not the BSL.

If HashiCorp is unwilling to switch Terraform back to an open source license, we propose to fork the legacy MPL-licensed Terraform

The question was if HashiCorp could take contributions to the fork and put them into their commercial product.

[-] jarfil@beehaw.org 1 points 2 years ago

That means HashiCorp could only take contributions licensed under the BSD or public domain, or under a CLA. The fork would be none of those.

[-] green_dot@le.fduck.net 6 points 2 years ago

I was hit aggressively by HC sales team last year, we are using TF and Vault, and were looking to add consul, now it is pretty vauge how it will all pan put

[-] yum13241@lemm.ee 5 points 2 years ago

Fuck'em. 'Nuff said.

[-] Sibbo@sopuli.xyz 2 points 2 years ago

Not that I'd know much about this, but can't you easily replace terraform with some script that remotely installs NixOS?

[-] thewitchofcalamari@bookwormstory.social 4 points 2 years ago

i dont think theyre equivalent tools since Terraform is used for things like creating cloud VMs with the selected OS image, configuring subnets and route tables among other things which i dont believe NixOS is meant for

[-] zagaberoo@beehaw.org 2 points 2 years ago

Terraform is great automation, but it really shines over scripts in a few ways:

intrinsic documentation for your infrastructure
much less brittle to differences in the initial state
changing your setup later doesn't require any new script logic, just a simple config change
much better support for collaborative editing

this post was submitted on 19 Aug 2023

113 points (100.0% liked)

Technology

38492 readers

332 users here now

A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.

Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.

Subcommunities on Beehaw:

This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.

founded 3 years ago

MODERATORS

alyaza@beehaw.org

TheRtRevKaiser@beehaw.org

gyrfalcon@beehaw.org

rs5th@beehaw.org

coldredlight@beehaw.org

SemioticStandard@beehaw.org

TheRtRevKaiser@kbin.social

remington@beehaw.org