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

121–130 of 136 posts

Re: The Terraform Registry Terms of Service have been updated

#121

Post by StopHammoTime »

paulgb wrote: post #103
throwaway103xx wrote: post #45

Earlier quoted context omitted.

If you look at it from a proprietary software company (which is what Hashicorp is now), it's totally expected and understandable. Why should they spend money supporting extra load on their infrastructure from people that are not directly paying for that? It makes perfect sense. Is it short-sighed? If you think they will go down in market share from now on, yes. But Hashicorp probably thinks it won't or it wouldn't ha…

From my point of view, controlling the canonical namespace is a form of soft power in the ecosystem. Since as the post says, the actual files are hosted on GitHub, the cost of the extra load on their infrastructure is real but probably not material to a company of their size -- as I understand it, it's more like running a DNS service than a file host. So it _seems_ (the word I used above as well) from my perspective…

I published a terraform provider when the registry in beta while working at a startup. They do some “value ads” like code signing and such, but you’re right - it can functionally be replaced by the GitHub release page.

Re: The Terraform Registry Terms of Service have been updated

#122

Post by sneak »

laserlight wrote: post #72
scrollaway wrote: post #27

Earlier quoted context omitted.

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…

> He’s someone who _gets_ what an open source company is/should be better than many who tried. I would have expected him to put in place mechanisms making the license change impossible, if he got that well what an open source company should be.

The license change is only for future changes. The existing codebase cannot be relicensed as HC does not own full copyright on 100% of contributions AIUI.

Re: The Terraform Registry Terms of Service have been updated

#123

Post by solomatov »

I don't exactly understand how you could use it for commercial use in the original license quoted in the thread:

>You may download or copy the Content (and other items displayed on the Services for download) for personal non-commercial use only, provided that you maintain all copyright and other notices contained in such Content. You shall not store any significant portion of any Content in any form.

Does personal non-commercial use allow use for work purposes somehow?

P.S. Just curious.

Re: The Terraform Registry Terms of Service have been updated

#124

Post by cstejerean »

jeremyjh wrote: post #28
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...".

The answer is "then a viable fork will sprout up and we can switch to that instead" which is what has happened for every notable widely used OSS project I can think of.

And it's not like you have to sit idly while that's happening. A small company might not be able to fork and maintain their own fork but they can pitch in with other companies by providing some development time, or money or infrastructure to help make an OSS fork successful as a community project.

Re: The Terraform Registry Terms of Service have been updated

#125

Post by paulddraper »

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?

https://github.com/hashicorp/terraform-provider-aws/issues/3...

The size is what you get when you add every single AWS Go client into one binary.

Each service client like 1-2MB. But when you have 200 services....

Re: The Terraform Registry Terms of Service have been updated

#126

Post by paulddraper »

hk1337 wrote: post #71

Silently infers they're trying to sneak something in without everyone knowing but the discussion has been going on for a few weeks now, iirc? They just finally made the change they said there going to make or is this something else?

The modified date was supposedly not updated. (But now it is?)

Re: The Terraform Registry Terms of Service have been updated

#127

Post by thedougd »

quickthrower2 wrote: post #20
candiddevmike wrote: post #17

Earlier quoted context omitted.

Who knows, maybe Oracle will acquire them someday, they seem to be heading towards acquisition/buy out.

They got MySQL and Java so Terraform would be a good one to bag

I believe Oracle uses Terraform as their OCI CloudFormation equivalent.

Re: The Terraform Registry Terms of Service have been updated

#128

Post by fhaldridge7 »

mdaniel wrote: post #86
sebazzz wrote: post #79

Earlier quoted context omitted.

> As precedent, Docker allows Kubernetes and Podman to access its registry, for example. Don’t give them any ideas. Nothing would stop them, though it is probably hard to actually enforce on a public repo.

I haven't tried every single one, but the AWS public ECR has a bunch of the "library" images from Docker Hub (e.g. public.ecr.aws/docker/library/golang:1.21 ) and as the "public" part implies, no creds required to access it They do have a search interface, if one wanted to look for their favorite: https://gallery.ecr.aws/

We switched many images to use the ecr.aws registry because we were getting rate-limited on dockerhub. Our k8s cluster was on EKS and it worked out very well.

Re: The Terraform Registry Terms of Service have been updated

#129

Post by laserlight »

sneak wrote: post #122
laserlight wrote: post #72

Earlier quoted context omitted.

> He’s someone who _gets_ what an open source company is/should be better than many who tried. I would have expected him to put in place mechanisms making the license change impossible, if he got that well what an open source company should be.

The license change is only for future changes. The existing codebase cannot be relicensed as HC does not own full copyright on 100% of contributions AIUI.

IANAL, but I don't think anyone can change license of something that has already been published. Doing so would defeat the purpose of having a license, in the first place.

Re: The Terraform Registry Terms of Service have been updated

#130

Post by berniedurfee »

martypitt wrote: post #2

Not 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.…

Very petty. I’ve been a longtime advocate and evangelist for Hashicorp products, but jeez.

I felt they were ‘one of the good ones’ making great tech just to make great tech. Success and profit followed making great tech.

How the mighty have fallen. Long live Terrafork I guess. Hashifork all their other stuff too I suppose. Very disappointing.

Post reply on HN