Martin Atkins

Thanks for raising this! Again I find myself unsure about what we can do here, but it seems worth a try. The challenges with this sort of recovery are always...

I can't speak for what terraform-docs would do when encountering something like this, but FWIW the Terraform language allows you to avoid duplicating the default values for nested attributes by...

Hi @pcj! We've not been able to start any further detailed design work on this yet since we've been focused on the configuration language improvements for v0.12, but we do...

We do not intend to allow providers to write directly to stdout, because that is incompatible with Terraform running in the machine-readable JSON mode. Instead, any output from providers will...

Hi all! It does seem reasonable to support a short-circuit behavior for the logical operators in the Terraform language. These operators are actually implemented upstream in [the HCL library](https://github.com/hashicorp/hcl), which...

In Terraform v0.12.0 we've reserved the variable name `provider` so that in a future release module blocks can contain instance-specific provider configurations when using `for_each` or `count`: ```hcl module "regional"...

Thanks for continuing to share use-cases! I think at this point we can safely generalize all of the variants of "Setting up [any AWS regionalized AWS object] across multiple/all AWS...

So far this issue has, as far as I can see, focused entirely on the problem of dynamically selecting AWS regions. We have not seen any other situations which seem...

That capability to declare providers in non-root modules was already deprecated for several versions before removal in v0.14. That mechanism was fundamentally broken because removing from the configuration any module...

Hi all, I worked on this in https://github.com/hashicorp/terraform/pull/34822 without realizing this issue was open for it. My initial implementation was focused on making it possible to paste in multi-line expressions,...