registry

I've been waiting for https://github.com/opentofu/registry/pull/824 ("Revert commit that removed Russian providers") to be resolved, but it seems to have stalled. Open source does not work as I envisioned, I guess.

R2 and its pricing is quite fantastic. We’re using it to power the OpenTofu Provider&Modules Registry[0][1] and it’s honestly been nothing but a great experience overall. [0]: https://registry.opentofu.org [1]: https://github.com/opentofu/registry Disclaimer: CloudFlare did sponsor us their business plan so we got access to higher-tier functionality

The OpenTofu registries are still standing by their decision to remove and block any resources affiliated with anyone in Russia due to US sanctions. https://github.com/opentofu/registry/pull/824 (https://news.ycombinator.com/item?id=41382437) > In discussing with the Linux Foundation, we understand this is a complex issue with many countries imposing sanctions on Russia and we do not have the community resources to figure this all out right now. Anyone in any geography could provide a similar service locally. Until they revert their (discriminatory and overreaching) policy or the community is supported in migrating towards an alternative registry without this unfortunate political situation, I think it's not wrong to be apprehensive about OT.

Without any Russian providers. Disheartening to see no resolution of this, still https://github.com/opentofu/registry/pull/824

Yep, it is nicely reviewed here: https://github.com/opentofu/registry/pull/824

The main question is not about IPs, but about cloud providers configs. See more details here: https://github.com/opentofu/registry/pull/824

I'm an outsider (not a contributor or related to parties in the suspected "political" origins, and had not created an HN account until now) but it was pretty easy to find the reason behind the change. Scroll down and there's the unanimous decision to block Russian access from registry due to sanctions. https://github.com/opentofu/registry/pull/817#issuecomment-2... https://github.com/opentofu/opentofu/blob/main/TSC_SUMMARY.m... > Sanctions Russia vs registry access > > Add note to README during PR documenting this discussion in TSC_SUMMARY > Block Russian IP Blocks from accessing our registry in Cloudflare > > Decision > Vote: unanimous yes Now if you want to blow this out of proportion you certainly can. Turn on the conspiracy tap of "trying to slid this in under the cover of darkness" but the fact of the matter is the Technical S

Related: https://github.com/opentofu/registry/pull/824

You should just keep using hashicorp providers - there's no changes to your codebase required, generally, as long as you don't specify provider sources in long form (as in, you should specify the source as `hashicorp/aws`, not as `registry.terraform.io/hashicorp/aws`). All providers should be available in our registry, and if you're missing any, just submit it[0]. Though as I said, all should be available. There's also the migration guide you could take a look at[1]. [0]: https://github.com/opentofu/registry/issues/new?assignees=&l... [1]: https://opentofu.org/docs/intro/migration/

CloudFlare pricing is indeed positively ridiculous. At OpenTofu[0] we’re using CloudFlare R2 to host the providers and modules registry[1]. Bandwidth is free, you only pay for requests. This already would be great, but there’s more - you only pay for requests that actually hit R2. So with an almost 100% cache hit ratio, we barely register any billable requests. Recently someone decided to load test us and generated ~1TB of traffic over 1-3 days. All but a few of these requests were cached, so the whole situation probably cost us less than a cent. [0]: https://opentofu.org [1]: https://github.com/opentofu/registry

It is, btw, why it was so easy for us to spin up a quick-and-dirty registry for our alpha release[0] that basically contains all providers and modules - almost everything is hosted on GitHub. Right now we're working on the stable registry[1,2], and that's basically the main blocker left to a full stable release. You can track the progress in our weekly updates[3]. Note: Interim Tech Lead of the OpenTofu project [0]: https://github.com/opentofu/registry [1]: https://github.com/opentofu/opentofu/issues/741 [2]: https://github.com/opentofu/registry-stable [3]: https://github.com/opentofu/opentofu/blob/main/WEEKLY_UPDATE...