Martin Atkins

Thanks to the work in https://github.com/opentofu/opentofu/pull/3493 we learned that the design for this feature in the Go runtime is effectively mandatory, and so it's available from OpenTofu v1.10 onwards even...

Hi again, everyone. The core maintainers discussed this again today, based on the new information I described in my earlier comments. After some consideration our conclusion is that we still...

FWIW, I think the `moved` block variation of this would be treated as a no-op (possibly with a warning?) rather than an error. The rule for `moved` blocks was that...

Looking at the example from the original issue, I'd note that as currently written that test ought to also fail for a different reason, because: - `var.root_disk` is declared as...

Hi @MohnJadden! Sorry for this strange behavior, and thanks for reporting it. Unfortunately since this issue relates to an object in your Azure account I think we will need more...

Thanks for sharing that trace log, @MohnJadden! Based on that I see that the Terraform interpreted the command line like this (using Go's conventions for printing a slice of strings):...

Thanks @MohnJadden! Unfortunately this leaves me quite stumped about what to try next. The fact that this message appears very early after you start running the command makes me wonder...

Some of the discussion above talked about defining composite literals as effectively a shorthand for a series of assignments, and alluded to the consequences of that, but I was left...

It could potentially be significant if the output values are consumed elsewhere using `terraform_remote_state`, so perhaps another way to proceed here would be to use similar annotations as we use...

What's happening here is that Terraform is noticing that the two arms of your conditional expression have different types and so rather than immediately returning an error Terraform is trying...