Martin Atkins

Okay... let's do another little code tour of the _plan-time_ version of the data resource handling similar to what I previously analyzed for the apply phase above. Most of the...

At this point I think I've read all of the code from `tofu.Context.Plan` to the postcondition checks at least five times in the hope of finding new leads on where...

Hi @idelsink, From what I can see in your plan output, I think what you are seeing here is not caused by the provider but rather by your configuration itself....

This concern about the ambiguity of what `required_version` means (whether it's a Terraform version or an OpenTofu version) is one of the things that https://github.com/opentofu/opentofu/issues/3300 is intended to solve. The...

Indeed, the primary purpose of the `repository_template` mechanism is to describe how to map from an OpenTofu-style provider address (which always follows the structure `hostname/namespace/type` systematically to any reasonable OCI...

This discussion also reminds me that we had originally considered supporting an additional mechanism where the mapping from OpenTofu-style provider address to OCI Repository address could live on the server...

Thanks for reporting this, @robrankin! I don't think this was _intentionally_ supported in v0.11 and prior and was probably just a side-effect of an implementation detail that has changed now,...

Thanks for capturing that context over in the `go-getter` repository, @salewski! I want to add a little more context here that is Terraform-specific: Terraform handles relative paths to modules already...

Hi @salewski, Regarding the "is local filesystem access desirable?" question: I don't know if this actually matters in practice, but previously it seems like a non-Terraform `go-getter` caller could specifically...

Thanks for sharing this use-case, @engineertdog! With Terraform as currently designed the "best" solution would be to actually describe the structure of IAM policies using Terraform's type system. Of course,...