[taukanda]

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 Steering Committee decided on something and acted on it, as their role grants them the power to do so. Anything else is just assumption.

[wertik12]

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

[taukanda]

Not a lawyer, but isn't this under the same guidelines as decided by the TSC? no Russian use or access?

Again heavy emphasis on "TSC" as the role.

[wertik12]

In TSC I see IP block is mentioned? What do you mean by "Russian" access? From Russia? By people with Russian passport? By employees of Russian company? What if I live in Kazahstan and want to use Yandex.Cloud datacenter located there: https://yandex.cloud/en/docs/troubleshooting/business/how-to...?

[taukanda]

It's not that complex, unless you want it to be.

Russian geological access or businesses with strong ties to Russia or suspected strong ties to Russia. Every other detail is to be decided by the governing body of the project, which in this case has happened.

[wertik12]

Sorry, but I still don't see a point in your message, how it is related to cloud config files that are in the repo. Open-source projects are not even covered by export control: https://www.linuxfoundation.org/resources/publications/under... If it is some voluntary decision by "governing body of the project" to remove config files that have nothing to do with IP-filtering to access, than it is exactly what I mention as "unreasonably explain by sanctions".