Martin Atkins

Hi @git-benjamin! Thanks for this feature request. Terraform Cloud has an API endpoint which returns content equivalent to the output of `terraform show -json PLANFILE`: https://developer.hashicorp.com/terraform/cloud-docs/api-docs/plans#retrieve-the-json-execution-plan Would the result from...

Hi again @git-benjamin! I'm reading between the lines of your answer here a bit: I assume you are trying to access this "runs" endpoint because your automation wouldn't otherwise know...

It looks like there's an intentional behavior change in the upstream library here which affects the behavior of our `fileset` function. I _think_ it might be bmatcuk/doublestar#28 that accounts for...

I'm no longer at HashiCorp after today, so I won't be able to work on this any further but I'm going to leave it open to keep it visible in...

Thanks for this feature request, @nwmcsween! I've added this to the list of issues for the core team to discuss, and we'll comment again once we've discussed it.

(The following is not an answer on behalf of the core team, since we've not discussed it together yet.) Introducing a new "meta-argument" for `resource`, `data`, `module`, `provider`, or `provisioner`...

As part of revisiting some older issues I've just re-confirmed this with a build from the v1.4 development branch (not actually a tagged release, but it's currently pre-beta at the...

Would a hypothetical new `docker-exec` provisioner suit your use-case? ``` js resource "docker_container" "foo" { // ... provisioner "docker-exec" { inline = [ "echo hello world" ] } } ```

The concept of provisioners has since emerged as largely a mistake: they don't really do anything that a managed resource type can't do and Terraform can't track them well because...

The "communicator" abstraction (which is what `connection` blocks are configuring) is poorly-specified and already very strained from a design standpoint. It was originally designed only for SSH and had WinRM...