Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

The Terraform Registry Terms of Service have been updated

github.com

Post reply on HN
Print view View original

21–30 of 136 posts

Re: The Terraform Registry Terms of Service have been updated

#21

Post by cube2222 »

yuppie_scum wrote: post #19
cube2222 wrote: post #15

Hey! Just wanted to say that this doesn't impact OpenTF too much. It's an extra step we need to take before a stable release, but long-term it'll make us more decoupled, which is great. As someone else commented, all providers and modules other than Hashicorp's are hosted on GitHub and the registry is just a "redirector". We'll do something similar, other than some special handling for Hashicorp's providers. Also, I…

I sure hope that opentf doesn’t just cause a fragmentation in the ecosystem that ruins the user experience, especially for the many people who are happily using unpaid TF and self hosted state stores.

> opentf doesn’t just cause a fragmentation

We're trying to remain as compatible on all fronts as possible, and our registry will too, so I wouldn't be attributing the fragmentation to OpenTF.

Re: The Terraform Registry Terms of Service have been updated

#22

Post by rwmj »

What's the legal theory that allows HashiCorp to control the use of data after downloading it? Is it like if I offered MP4 files on my website that can be downloaded by anyone but added the condition you must view them in VLC only? (which I'm fairly sure would be unenforcible even if the MP4 files were proprietary content)

Re: The Terraform Registry Terms of Service have been updated

#23

Post by benterix »

cube2222 wrote: post #15

Hey! Just wanted to say that this doesn't impact OpenTF too much. It's an extra step we need to take before a stable release, but long-term it'll make us more decoupled, which is great. As someone else commented, all providers and modules other than Hashicorp's are hosted on GitHub and the registry is just a "redirector". We'll do something similar, other than some special handling for Hashicorp's providers. Also, I…

I just wanted to say thank you so much for your efforts and I'm looking forward to seeing some interesting developments with OpenTF.

Re: The Terraform Registry Terms of Service have been updated

#24

Post by cube2222 »

benterix wrote: post #23
cube2222 wrote: post #15

Hey! Just wanted to say that this doesn't impact OpenTF too much. It's an extra step we need to take before a stable release, but long-term it'll make us more decoupled, which is great. As someone else commented, all providers and modules other than Hashicorp's are hosted on GitHub and the registry is just a "redirector". We'll do something similar, other than some special handling for Hashicorp's providers. Also, I…

I just wanted to say thank you so much for your efforts and I'm looking forward to seeing some interesting developments with OpenTF.

Thank you for the kind words, they are very appreciated! I'll make sure to relay them to the rest of the team :)

Re: The Terraform Registry Terms of Service have been updated

#25

Post by geerlingguy »

artyom wrote: post #10
Octabrain wrote: post #5

I 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.

It's sad too, mitchellh used to be fairly active in the HN community but it seems he is not able to for likely professional reasons after the BSL fiasco.

Re: The Terraform Registry Terms of Service have been updated

#26

Post by viraptor »

skywhopper wrote: post #11
jrudolph wrote: post #8

Getting 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?

The AWS Go SDK is the vast majority of that bulk. In general go binaries can get pretty big but AWS has hundreds of services with thousands of APIs and it’s all going to have to get included in the AWS provider.

Also AWS has so many services that the SDKs are mainly generated from json descriptions + nice wrappers on top. That leads to a different and less abstracted type of code than you'd write yourself - which leads to bigger compiled objects.

Ruby had this problem too and at some point split the SDK into multiple gems so you don't have to install everything.

Re: The Terraform Registry Terms of Service have been updated

#27

Post by scrollaway »

geerlingguy wrote: post #25
artyom wrote: post #10

Earlier quoted context omitted.

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.

It's sad too, mitchellh used to be fairly active in the HN community but it seems he is not able to for likely professional reasons after the BSL fiasco.

Mitchell is a wonderful hacker. He’s someone who gets what an open source company is/should be better than many who tried.

I suspect he doesn’t feel great about what’s happening with the company…

Re: The Terraform Registry Terms of Service have been updated

#28

Post by jeremyjh »

jacquesm wrote: post #4

Companies 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 motivate…

I think this damages all commercial OSS projects. Because after Docker and Terraform, any effort to bring in some OSS project as a dependency will be met with "Sure, it's open source now, but what about when...".

Re: The Terraform Registry Terms of Service have been updated

#29

Post by jeremyjh »

scrollaway wrote: post #27
geerlingguy wrote: post #25

Earlier quoted context omitted.

It's sad too, mitchellh used to be fairly active in the HN community but it seems he is not able to for likely professional reasons after the BSL fiasco.

Mitchell is a wonderful hacker. He’s someone who gets what an open source company is/should be better than many who tried. I suspect he doesn’t feel great about what’s happening with the company…

I'm sure he's been well compensated for his hurt feelings.

Re: The Terraform Registry Terms of Service have been updated

#30

Post by jitl »

yuppie_scum wrote: post #19
cube2222 wrote: post #15

Hey! Just wanted to say that this doesn't impact OpenTF too much. It's an extra step we need to take before a stable release, but long-term it'll make us more decoupled, which is great. As someone else commented, all providers and modules other than Hashicorp's are hosted on GitHub and the registry is just a "redirector". We'll do something similar, other than some special handling for Hashicorp's providers. Also, I…

I sure hope that opentf doesn’t just cause a fragmentation in the ecosystem that ruins the user experience, especially for the many people who are happily using unpaid TF and self hosted state stores.

It’s Hashicorp’s license changes that are causing fragmentation, OpenTF is the effect not the cause.
Post reply on HN