|
|
|
|
|
|
by sofixa
390 days ago
|
|
|
> Additionally, HashiCorp changed the terms of service on the registry, making it only acceptable to use the official terraform binaries to download modules or providers. Why would HashiCorp provide free hosting of providers and modules for projects competing, using HashiCorp's own code at that? Multiple entire companies exist doing little more than providing wrappers around stuff HashiCorp develops. HashiCorp has no obligation to give them everything so they have an easier time at undercutting them (because they don't have to actually develop the main stuff). > But the point here is that Hashicorp took steps that caused the community of terraform users to recognize that closing off the ecosystem would have a tremendous impact on devops. The community of people using alternative products off HashiCorp's efforts, code, and money. Terraform Community Edition is still free and usable for anyone as long as you don't sell it to compete with HashiCorp. |
|
|
If you recall, my point is that “providers were in danger,” and this is a reason in support of that. HashiCorp, of course, has no obligation to host providers for competitors. But, this is one more reason OpenTofu succeeded!
> Terraform Community Edition is still free and usable for anyone as long as you don't sell it to compete with HashiCorp.
Except, it’s rather unclear what “compete with HashiCorp” means, and there’s very little assurance that if you stick with terraform community edition you won’t get screwed over and be forced to pay in 6 months.
You can make all the arguments about “needing to make money”, “free loaders”, etc. HashiCorp is not unique in changing licenses and getting backlash.
But, as someone who joined HashiCorp, in part, because of our open source strategy, and hearing over and over, for years, how it was the reason we were so successful…