Martin Atkins

I think #26838 might be covering the same thing, though with a different underlying use-case. That issue frames the problem as one module passing a template to another in order...

Hi all! Sorry for the long silence here. Yesterday's v1.9.0 alpha release of Terraform CLI included an experimental solution to this feature request, and so it'd be very helpful if...

Hi @SebTardif, I believe the design assumption here is that the state storage region of a particular configuration won't change between runs, except in the rare case where you're explicitly...

I was not involved in the original design of this backend and so I'm just speculating here but I believe the original design idea is to treat differently settings that...

Thanks for confirming, @DJAlPee! The S3 backend is maintained by the AWS provider team rather than the Terraform CLI/Core team (despite also being in this repository) so ultimately that team...

Hi @camlow325! Thanks for sharing this use-case. This is a consequence of the intentional design decision that we treat environment variable values for _primitive-typed_ values as direct literal values, rather...

Changing how environment variables or `-var` command line options get interpreted seems like it would end up violating [the v1.x compatibility promises](https://developer.hashicorp.com/terraform/language/v1-compatibility-promises) without some careful design; we must be careful...

Taking a broad view of versions, it is true that `terraform fmt` in v0.15 would make a v0.11-compatible configuration no longer parseable with Terraform v0.11, so this does seem to...

Since the files to upload are decided by the upstream library go-slug, which is in turn wrapped by another library go-tfe, Terraform CLI itself is not actually directly involved in...

This is an interesting approach. I have some feedback, but really just exploring the idea: --- Given that the connection doesn't really "belong to" the provider, I wonder if we...