The Terraform Registry Terms of Service have been updated
1–10 of 136 posts
Re: The Terraform Registry Terms of Service have been updated
#2Not the OP, but I suspect HN has trimmed the anchor link.
> https://github.com/opentffoundation/roadmap/issues/24#issuec...
That's the comment that made the issue clear -- specifically TOS were amended for https://registry.terraform.io to state:
> You may download providers, modules, policy libraries and/or other Services or Content from this website __solely for use with, or in support of, HashiCorp Terraform.__
ie., it looks like the intent is "You can't use OpenTF with registry.terraform.io".
IMO, that feels a little petty. But, I guess if OpenTF is taking a position of "Use us instead of Terraform", then they shouldn't expect to get the usage of Hashicorps infra.
Re: The Terraform Registry Terms of Service have been updated
#3Even though this will likely prevent OpenTF from connecting to registry.terraform.io to get plugins, the source code for most (all?) plugins is still open source and actually stored on GitHub (e.g. https://github.com/terraform-provider-openstack/terraform-pr...).
More work for OpenTF to get up and running, but also feels reasonable that HashiCorp wouldn't allow connecting to their service.
Re: The Terraform Registry Terms of Service have been updated
#4Companies want the benefits of open source (massive community contributions, lower development costs, better security, community exposure, marketshare) but don't like the downsides (from their perspective: forks, lack of control, freeloaders etc).
TOS changes like this are fine, it's their garden, but ultimately all they'll do is put even more power behind forks and alternatives. Because the people that were motivated to use OpenTF are now also going to offer an alternative registry, which results in further loss of control and community contact and shifts attention away from HashiCorp's offering. It's very difficult to pull off this sort of dual stance without each move that you make impacting some aspect of your operation in a negative way. You need to think this through very well from day one because any change later on could easily be perceived as the beginnings of an attempt to squeeze the installed base and once that is the impression you will lose users rapidly.
Re: The Terraform Registry Terms of Service have been updated
#5I had Hashicorp in my mind as a cool and respectful company. These recent events have made to reconsider and throw them into the same bag as Oracle. I find this pretty sad.
Re: The Terraform Registry Terms of Service have been updated
#6Even though this will likely prevent OpenTF from connecting to registry.terraform.io to get plugins, the source code for most (all?) plugins is still open source and actually stored on GitHub (e.g. https://github.com/terraform-provider-openstack/terraform-pr... ). More work for OpenTF to get up and running, but also feels reasonable that HashiCorp wouldn't allow connecting to their service.
>still open source and actually stored on GitHub
I think that's true, but it's probably hard to recreate large parts of the index. I don't think there's any mandatory manifest or something like that where you can reliably identify a repo as something that appears in their registry. Probably some missing metadata too.
Re: The Terraform Registry Terms of Service have been updated
#7Not the OP, but I suspect HN has trimmed the anchor link. > https://github.com/opentffoundation/roadmap/issues/24#issuec... That's the comment that made the issue clear -- specifically TOS were amended for https://registry.terraform.io to state: > You may download providers, modules, policy libraries and/or other Services or Content from this website __solely for use with, or in support of, HashiCorp Terraform.__ ie.…
[deleted]
Re: The Terraform Registry Terms of Service have been updated
#8Getting a lot of docker hub vibes from this one. HashiCorp is course within their rights. Can't be cheap to run the registry given the obscene size of some terraform providers.
$ ls -lah terraform/providers/registry.terraform.io/hashicorp/aws/5.14.0/darwin_amd64/ total 368M
Anyone have an idea of the reasons terraform needs a 370 MiB binary just to call REST APIs?
Re: The Terraform Registry Terms of Service have been updated
#9I had Hashicorp in my mind as a cool and respectful company. These recent events have made to reconsider and throw them into the same bag as Oracle. I find this pretty sad.
They absolutely were at one point, this is why the BSL move was so upsetting, not because it necessarily stopped people from using it (unless they of course were offering competing services), but because it signaled that the phase of HashiCorp being a cool and respectful company are over.
It's almost a capitalist gut punch. Chasing that dollar, companies will squeeze every last drop of altruism out of a company.
It makes me think that the gov. should provide incentives to keep open source software backed by corporations going by figuring out how to offer a tax break on all of the "lost revenue"... We just need a good way of figuring out what the lost revenue is.
:thinking:
Re: The Terraform Registry Terms of Service have been updated
#10I had Hashicorp in my mind as a cool and respectful company. These recent events have made to reconsider and throw them into the same bag as Oracle. I find this pretty sad.
It actually was a respectable company. But the guy who started it all (Mitchell Hashimoto) isn't there anymore (at least not as a decision maker) so the corporate drones are taking over.