It really isn’t about whether the licensing change is going to affect my usage of Terraform or our costs, it’s the principle of the thing. Hashicorp is proving that they are willing to accept free work from the community without giving anything back in return. This is the absolute worst type of open source exploitation and should not be tolerated, period.
Many thanks for all the work you do, really appreciative of all the informaton and insights I gain from the man, the myth, the legend that is Ned. From a question standpoint, I guess I'm not sure how this would affect (if at all) things like, evn0, brainboard, terragrunt etc.? If it's not something that is known now, would be great if that could be asked as the live session you will have doesn't work well with my time-zone. Thanks!
That is definitely something I'd like to address in the live stream. Many of the vendors have released statements already, including Spacelift and env0.
Great concise video just sticking to the facts and no FUD. I personally think that there’s an overreaction in the market about this change mostly by the companies who clearly build competitive offerings against HashiCorp. I don’t remember seen this outcry when MariaDB, Elastic went to a BSL model.
Because not a lot of people heard about the license change for MariaDB, Elastic, Redis etc... And personnally, i won't use those products anymore. Either full open-source, or nothing.
fluxcd team is still investigating the impact of terraform changes to their product, and the flux terraform controller... there's an open issue where they're trying to address the problems
Hi Ned, I completely understand there isn't enough information at this time to really make heads or tails of the real impact. With the change to BSL for Terraform and the comment of this only affects 1% of the Terraform community, I feel like this is an assumption. I have to imagine that more than 1% of the community uses a third party platform like Env0, Spacelift, etc. I also can't imagine that the folks using those platforms won't be affected from a cost perspective. If Hashicorp is going to charge them to use Terraform, I would assume that cost is passed on to their customers and thus affecting all of those people and companies. Do you feel like that is an accurate assumption?
I think you're right that the main impact to those using Terraform is the possibility that their automation platform may have to raise prices. Based on some informal polling I've seen, the most popular Terraform automation platform is... GitHub Actions. Other platforms, like ADO, Code Pipeline, and Jenkins all should be unaffected by this change. I still think my 1% number is pretty close based on platform adoption.
Thank you for clarifying this; there was a lot of misinformation out there. There is a lot of noise with people saying that others should shift to OpenTF. Personally, I don't think people should do it, especially since the individuals promoting this information might have vested interests due to being affected by this change.
No, I'm not constrained by being an Ambassador. HashiCorp has made it clear they support and appreciate our independent viewpoints. My goal was to communicate the facts as I understood them in a concise way. If you're looking for opinions and feelings, you can check out my Day Two Cloud podcast where I talk in some more depth about it: daytwocloud.io/podcast/day-two-cloud-208-hashicorp-licensing-changes-and-the-day-two-cloud-chaos-lever-crossover/
You're certainly welcome to have that opinion. And I agree there is some grey areas that I hope to clarify with Armon. The uncertainty for some is real, but that doesn't mean we don't know anything.
It really isn’t about whether the licensing change is going to affect my usage of Terraform or our costs, it’s the principle of the thing. Hashicorp is proving that they are willing to accept free work from the community without giving anything back in return. This is the absolute worst type of open source exploitation and should not be tolerated, period.
Many thanks for all the work you do, really appreciative of all the informaton and insights I gain from the man, the myth, the legend that is Ned. From a question standpoint, I guess I'm not sure how this would affect (if at all) things like, evn0, brainboard, terragrunt etc.? If it's not something that is known now, would be great if that could be asked as the live session you will have doesn't work well with my time-zone. Thanks!
That is definitely something I'd like to address in the live stream. Many of the vendors have released statements already, including Spacelift and env0.
Thank you for this; I was thinking "Well can I still use it for free?" I do work as a contractor that often involves it.
Yes, you can still use it for free and implement into production, as long as your "use" is not a compete to a Hashicorp product.
For CEST (Central European Summer Time) the stream will be the 25th of August at 8 pm.
Thanks for adding that!
I really don't know how to feel about this change
Great concise video just sticking to the facts and no FUD. I personally think that there’s an overreaction in the market about this change mostly by the companies who clearly build competitive offerings against HashiCorp. I don’t remember seen this outcry when MariaDB, Elastic went to a BSL model.
Because not a lot of people heard about the license change for MariaDB, Elastic, Redis etc...
And personnally, i won't use those products anymore.
Either full open-source, or nothing.
thanks for the clarification! It seems reasonable, could anyone tell me more about what concerns may come?
Best explanation on YT
Great explanation, Ned!
Okay, so I don't have to worry as I just use Terraform to deploy my customer environments to aws and azure.
Correct. Keep calm and Terraform on.
fluxcd team is still investigating the impact of terraform changes to their product, and the flux terraform controller... there's an open issue where they're trying to address the problems
Hi Ned, I completely understand there isn't enough information at this time to really make heads or tails of the real impact. With the change to BSL for Terraform and the comment of this only affects 1% of the Terraform community, I feel like this is an assumption. I have to imagine that more than 1% of the community uses a third party platform like Env0, Spacelift, etc. I also can't imagine that the folks using those platforms won't be affected from a cost perspective. If Hashicorp is going to charge them to use Terraform, I would assume that cost is passed on to their customers and thus affecting all of those people and companies. Do you feel like that is an accurate assumption?
I think you're right that the main impact to those using Terraform is the possibility that their automation platform may have to raise prices. Based on some informal polling I've seen, the most popular Terraform automation platform is... GitHub Actions. Other platforms, like ADO, Code Pipeline, and Jenkins all should be unaffected by this change. I still think my 1% number is pretty close based on platform adoption.
Thank you for clarifying this; there was a lot of misinformation out there. There is a lot of noise with people saying that others should shift to OpenTF. Personally, I don't think people should do it, especially since the individuals promoting this information might have vested interests due to being affected by this change.
I clicked on the video to know how you feel about it. are you constrained by being HashiCorp ambassador?
No, I'm not constrained by being an Ambassador. HashiCorp has made it clear they support and appreciate our independent viewpoints. My goal was to communicate the facts as I understood them in a concise way. If you're looking for opinions and feelings, you can check out my Day Two Cloud podcast where I talk in some more depth about it: daytwocloud.io/podcast/day-two-cloud-208-hashicorp-licensing-changes-and-the-day-two-cloud-chaos-lever-crossover/
Let me tell you what I understand here:
...no one really understands what that change means, but everyone just talks and makes videos for content
You're certainly welcome to have that opinion. And I agree there is some grey areas that I hope to clarify with Armon. The uncertainty for some is real, but that doesn't mean we don't know anything.