-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ADD Another reason to why care #521
base: main
Are you sure you want to change the base?
Conversation
index.html
Outdated
First, if you want to automate your Terraform process, like you would | ||
with any other code, you are limited to either spending your precious | ||
engineering time and money to build your own solution or using | ||
Terraform Cloud. HashiCorp is removing options from you in how best |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nit: double whitespace.
<p> | ||
How do you know you're not competing with HashiCorp? | ||
Secondly, how do you know you're not competing with HashiCorp? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I guess the third argument is that a license change is a slippery slope. Done once it can be done again if the 1st decision does not yield expected business results. Say you require payment for any production use (so, TF remains free, but for non-production use only).
In that sense what should worry everyday users is not only the current license, but the fact that the license owner is desperately trying to squeeze out more value from it.
Even if you don't care for OpenTF, and want to continue using Terraform under BSL, your best bet is to support OpenTF to remove the incentive for Hashi to further limit your options.
Hope that makes sense.
66f959e
to
33361fa
Compare
Another reason to care is the fallout on the rest of the OSS community as noted in Massdrivers blog post CNCF is spending dev cycles removing/replacing Hashi tools. This will impact those CNCF tools features/fixes as time is spent on swapping tools. Also , CNCF as users of those tools in dev workflows are less likely to commit code to Hashi tools if they don’t use them. Hashi’s change will lead to a vicious cycle of devs ceasing to commit on Hashi tools. Meaning Hashi tool end users will see less and less features and fixes. |
First, if you want to automate your Terraform process, like you would | ||
with any other code, you are limited to either spending your precious | ||
engineering time and money to build your own solution or using | ||
Terraform Cloud. HashiCorp is removing options from you in how best to |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Terraform Cloud. HashiCorp is removing options from you in how best to | |
Terraform Cloud. HashiCorp is removing options from you on how best to |
engineering time and money to build your own solution or using | ||
Terraform Cloud. HashiCorp is removing options from you in how best to |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I feel like this is missing a logical step to help readers connect the dots: why does this license change limit that to the only options? I think you'd have to explain that HashiCorp has explicitly said that any CI / CD solution for TF other than TFC/TFE could be a considered a competitor, so either you build your own, or pay them for theirs. Anything else on the market likely has to disappear.
Also, is that the top reason we think readers should care?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Anything else on the market likely has to disappear.
Including, potentially, existing/upcoming free open-source solutions so if you build your own, there is the added caveat that you may not be able to open-source it and try to make it a solved problem for the industry without monetization being the direct goal.
Every single company/organization may very well have to either sign-up with Hashicorp or solve the problem again on their own.
The focus is often placed on commercial competitors, but lets not forget that the free open-source ecosystem around Terraform can itself become a competitor here.
I know it doesn't seem very friendly to commercial interests, but my take is that the free ecosystem (what I consider solved problems in the industry) should grow and commercial actors should remain creative finding new unexplored niches to commercialize. Anything else (more precisely this new business license here) leads to stagnation (can you imagine where we'd be right now if you had to pay a license to someone and ask for permission for every little thing we now take for granted?).
Hashicorp should not be afraid to let Terraform grow and that includes embracing competition, commercial and otherwise.
No description provided.