Martin Atkins

Thanks for recording this, @bflad. The "requiredness" is currently handled by mapping the Terraform schema idea of required onto the `Required` field of [`hcldec.AttrSpec`](https://pkg.go.dev/github.com/hashicorp/hcl/v2/hcldec#AttrSpec), which is ultimately what's decoding these...

I can't find any _released_ older version of Terraform which uses `hcldec.ValidateSpec`, so I have to assume that whatever I'm thinking of didn't make it into a stable release. Maybe...

I think our current situation essentially unfolded from us not having a clear model during early v0.12 development of which parts of the work were being handled by Terraform Core...

Root modules in Terraform have unfortunately always been a little different than called modules, and this behavior is a symptom of that since all of Terraform's commands assume that they...

Hi @loicvolle, The other issue you mentioned (#26131) seemed to get stuck because we could not reproduce it locally, suggesting that it was something unique to the requester's system rather...

Hi @xx364! I'm not a maintainer of this provider so I'm just commenting here with some hopefully-helpful additional context from the perspective of Terraform Core and the provider plugin protocol....

Hi all, I believe that provider versions v3.14.0 and later should include additional log messages in the debug output explaining what the provider was trying to return when it encountered...

HCL is not designed for "schemaless" languages. The evaluation model relies on schema to resolve ambiguities such as those in the JSON syntax. `locals` in the Terraform language _does_ have...

I wrote a long comment above with various different concerns in it but I just want to reiterate the main tension in designing this: In situations where the module author...

I showed `network_mirror` in my earlier example just because we'd been talking about the use-case of making requests to `registry.terraform.io` go to a different network host instead, which is what...