Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

OpenTofu removed Russian-originated clouds unreasonably explain by sanctions

github.com

Post reply on HN
Print view View original

1–10 of 27 posts

Re: OpenTofu removed Russian-originated clouds unreasonably explain by sanctions

#2

Post by ShakataGaNai »

IANAL but this change doesn't seem to make sense from any sort of "sanctions" perspective. Sure, block sanctioned countries from accessing your website or registry, etc - that makes sense. But removing providers? That doesn't seem to be related.

The thing that makes this *super* f'd up is the fact that #1 - There is no commentary from the group members explaining this or what the policy change is (the few linked TSC documents are just about registry, not about providers). #2 - There is no explanation in the PR and no linked bugs. #3 - The super vague "remove some providers" title.

It's clear OpenTofu devs were trying to slide this change in under the cover of darkness and hope no one noticed. Which makes zero sense for an OPEN source project.

You don't have to like the providers, you don't have to support them. You can even say they are actively deprecated due to the inability to test/support said providers (which totally would make sense). But just to straight out remove functional code with zero warning, notice or explanation? Super scummy.

Re: OpenTofu removed Russian-originated clouds unreasonably explain by sanctions

#3

Post by _lvbh »

Suspicious new account. Russian bot? /s

> so that valuable features and fixes are accepted based on their value to the community, regardless of their impact on any particular vendor. - https://opentofu.org

It’s sad that everything revolves around politics these days. They claim sanctions but it’s quite obvious this is just the personal opinion of the team.

Re: OpenTofu removed Russian-originated clouds unreasonably explain by sanctions

#7

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

Re: OpenTofu removed Russian-originated clouds unreasonably explain by sanctions

#8

Post by wertik12 »

taukanda wrote: post #7

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

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

Re: OpenTofu removed Russian-originated clouds unreasonably explain by sanctions

#10

Post by taukanda »

wertik12 wrote: post #8
taukanda wrote: post #7

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

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

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.

Post reply on HN