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

131–136 of 136 posts

Re: The Terraform Registry Terms of Service have been updated

#131

Post by berniedurfee »

yjftsjthsd-h wrote: post #49
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…

> Why should they spend money supporting extra load on their infrastructure from people that are not directly paying for that? There same logic applies to users; at this point, I have to assume that the only reason that Hashicorp is providing anything to people who aren't actively giving them money is to try and get money from them later. This is also one of the reasons I'm abandoning them ASAP; now that the money sq…

Not to mention the number of community contributions is going to plummet.

At some point third party and independent module and provider developers will need to decide whether to cross-support both tools.

I don’t think Hashi is going to go out of their way to make life easy for Terrafork. Cross-compatibility won’t last long.

Re: The Terraform Registry Terms of Service have been updated

#132

Post by jen20 »

sam_bristow wrote: post #112
throw16180339 wrote: post #101

Earlier quoted context omitted.

Some of them, however, may want to be acquired by companies that compete with HashiCorp.

Or HashiCorp might acquire a company you compete with.

Red herring. The licensing FAQ from HashiCorp makes it clear that this would not trigger the BSL provisions. [1].

[1]: https://www.hashicorp.com/license-faq#future-competitive-pro...

Re: The Terraform Registry Terms of Service have been updated

#133

Post by jen20 »

candiddevmike wrote: post #18
skywhopper wrote: post #11

Earlier quoted context omitted.

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.

The AWS Go SDK is actually a case study on making everything into pointers

It’s really a case in the abject inadequacy of the Go type system.

Re: The Terraform Registry Terms of Service have been updated

#134

Post by prmoustache »

jeremyjh wrote: post #105
prmoustache wrote: post #100

Earlier quoted context omitted.

Most decision makers aren't impacted nor concerned by Hashicorp's change of licence.

Again, that is not important for my argument. It only matters that some are concerned.

The only one are those that build stuff on top of terraform.

And you know what? It will always be worse building stuff on top of a proprietary technology managed by a company that can decide to discontinue it anytime. Look a all those companies that had build services using twitter api.

Re: The Terraform Registry Terms of Service have been updated

#135

Post by Too »

viraptor wrote: post #26
skywhopper wrote: post #11

Earlier quoted context omitted.

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.

The Azure sdks are the same. Auto generated from some underlying description. Then for backwards compatibility, every previous version is its own complete copy, all included in one single bundle.

Re: The Terraform Registry Terms of Service have been updated

#136

Post by tuananh »

fhaldridge7 wrote: post #128
mdaniel wrote: post #86

Earlier quoted context omitted.

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.

you probably need mirroring anyway. Lots of stuff missing on public ecr. I haven't verified if those on public ecr are legit or not or at least, same as the dockerhub counterpart.
Post reply on HN