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

11–20 of 136 posts

Re: The Terraform Registry Terms of Service have been updated

#11

Post by skywhopper »

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.

Re: The Terraform Registry Terms of Service have been updated

#12

Post by chippiewill »

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?

I think the providers might actually come from GitHub because the registry insists you have them as release assets

Re: The Terraform Registry Terms of Service have been updated

#14

Post by jabiko »

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?

> Can't be cheap to run the registry given the obscene size of some terraform providers.

Some providers are also hosted externally. I guess if traffic is going to be a problem they might also just switch to hosting every provider that is build on GitHub to GitHub releases (and hope that GitHub won't change its policy)

  curl -s https://registry.terraform.io/v1/providers/carlpett/sops/0.7.2/download/linux/amd64 | jq .download_url
  "https://github.com/carlpett/terraform-provider-sops/releases/download/v0.7.2/terraform-provider-sops_0.7.2_linux_amd64.zip"

  curl -s https://registry.terraform.io/v1/providers/hashicorp/helm/2.10.1/download/linux/amd64 | jq .download_url
  "https://releases.hashicorp.com/terraform-provider-helm/2.10.1/terraform-provider-helm_2.10.1_linux_amd64.zip"

Re: The Terraform Registry Terms of Service have been updated

#15

Post by cube2222 »

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 know you want us to finally publish the repo - we're working very hard to make this happen and it should be a matter of days now.

Disclaimer: Work at Spacelift, and currently temporary Technical Lead of the OpenTF Project, until it's committee-steered.

Re: The Terraform Registry Terms of Service have been updated

#16

Post by paulgb »

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

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

It’s totally something they can do, but it seems short-sighted. They had to know that this wouldn’t actually stop the momentum around OpenTF, but just result in HashiCorp giving up the control they have over the canonical namespace.

As precedent, Docker allows Kubernetes and Podman to access its registry, for example.

Re: The Terraform Registry Terms of Service have been updated

#17

Post by candiddevmike »

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.

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

Re: The Terraform Registry Terms of Service have been updated

#18

Post by candiddevmike »

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.

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

Re: The Terraform Registry Terms of Service have been updated

#19

Post by yuppie_scum »

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.

Re: The Terraform Registry Terms of Service have been updated

#20

Post by quickthrower2 »

candiddevmike wrote: post #17
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.

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
Post reply on HN