Martin Atkins

In addition to what @jbardin said, I'd also note that this is a tricky situation where although we could potentially make a null value just be silently ignored, if we...

I remember back when we were considering which operators to make builtins we had intentionally made the "power of" operation be a function rather than an operator both because it...

Incidentally, I think the `lookup` calls in this example aren't really doing anything because the type constraint already requires both of those arguments to be present in the object; the...

Thanks indeed for pointing this out, @steven-hyland. This particular error message actually belongs to [the HCL codebase](https://github.com/hashicorp/hcl) rather than to Terraform directly, and so if we intend to improve it...

Hi @steven-hyland! Thanks for confirming. I think for the moment we might as well just leave this issue here to avoid creating sprawl. If we follow the path I described...

Hello, It seems like this issue has effectively now transformed into a request for allowing default values for input variables to be dynamic based on other values present in the...

I think this request requires essentially the same internal architecture change as https://github.com/hashicorp/terraform/issues/25609 and so it may be worthwhile to address both of them at the same time if it...

Hi all, I want to be explicit that from the perspective of the stable Terraform language the `defaults` function never existed: it was only ever in an experimental version of...

[(some earlier discussion about this in the Community Forum, just to keep this all connected)](https://discuss.hashicorp.com/t/terraform-test-error-is-unclear-when-you-hit-service-quota-during-build-phase/32620/3)

Hi @skeggse! Thanks for sharing this use-case. The compromise of allowing only static move rules arose from having to work within some other constraints, so I think in order to...