HashiCorp adopts the Business Source License to ensure continued investment in its community and to continue providing open, freely available products.
That’s where I’m at too. Philosophically its a bummer. For the majority of users of their codebase however, this presents zero changes and the only entity I known of who would be impacted by this change going forward is AWS
Curious, how will AWS be affected? I’m not familiar with all of Hashicorp’s tools. Mostly just Terraform (and obvs AWS had Cloud Formation, then CDK - they even worked with HashiCorp I believe to build CDKTF).
So I was trying to figure out what are they getting defensive against. It was clear in redhat’s case, but I only really found pulumi as some sort of alternative to terraform and I’m not even sure it relies on it. What is the AWS product that’s competing here?
Pulumi relies on Terraform providers, it can actually “plug in” any Terraform provider.
This won’t be much of a problem though, as Hashicorp has pushed the work of developing and maintaining providers to its “partners”. Even providers under the Hashicorp umbrella like AWS is not actively developed by hashicorp personell so there is really no play here, as is reflected by them not touching the license in those repositories.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !programming@programming.dev
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person’s post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
Follow the programming.dev instance rules
Keep content related to programming in some way
If you’re posting long videos try to add in some form of tldr for those who don’t want to watch videos
That’s where I’m at too. Philosophically its a bummer. For the majority of users of their codebase however, this presents zero changes and the only entity I known of who would be impacted by this change going forward is AWS
Curious, how will AWS be affected? I’m not familiar with all of Hashicorp’s tools. Mostly just Terraform (and obvs AWS had Cloud Formation, then CDK - they even worked with HashiCorp I believe to build CDKTF).
So I was trying to figure out what are they getting defensive against. It was clear in redhat’s case, but I only really found pulumi as some sort of alternative to terraform and I’m not even sure it relies on it. What is the AWS product that’s competing here?
Service Catalog has terraform constructs built in now
Pulumi relies on Terraform providers, it can actually “plug in” any Terraform provider. This won’t be much of a problem though, as Hashicorp has pushed the work of developing and maintaining providers to its “partners”. Even providers under the Hashicorp umbrella like AWS is not actively developed by hashicorp personell so there is really no play here, as is reflected by them not touching the license in those repositories.