Martin Atkins

FWIW, I think that last comment overlaps with https://github.com/hashicorp/terraform-provider-aws/issues/44590 , which is describing a similar concern from a provider perspective.

In the little rough sketch I shared with you I think the main point of concurrency contention was the use of the `FETCH_HEAD` symbolic ref as a representation of "the...

This is one of those proposals that's tricky because it sits uncomfortably on the fence between specification and implementation detail. As mentioned above, the concept of "P" is an implementation...

Hi @progloto! Thanks for reporting this. Unfortunately this is a problem with the design of this resource type in the provider plugin, and not something that OpenTofu can directly address...

After thinking about this some more, I suppose there _is_ a way OpenTofu could potentially improve this, in theory: During destroy planning, if the resource instance in question is still...

I think a "real" solution to this problem would involve explicitly classifying certain attributes in the schema of a resource type as being "destroy-time arguments", which I expect is probably...

Hi again, The core maintainers discussed this today, and we had consensus that there doesn't seem to be anything we can do to improve this situation within our current technical...

Thanks for working on this, @topperge! https://github.com/opentofu/opentofu/issues/2026 was labelled as "need-rfc" because we felt that it needed more exploration and decision making before we could move forward with implementation. Your...

To try to answer my own question about the runtime handling of `GODEBUG` I went to dig around in the docs again, and found [FIPS 140-3 Compliance](https://go.dev/doc/security/fips140) which has the...

Hi @ericrichtert, What you've described here is, unfortunately, the intended behavior. The reason is that in Terraform's architecture the idea of a "module registry" is an index separate from the...