Martin Atkins

From looking closely at the TRACE logs for the apply step, I can see why `terraform apply` didn't catch this in v1.1.9: ``` 2022-05-12T11:51:32.980-0700 [DEBUG] pruneUnusedNodes: local.maybe (expand) is no...

I did try to reproduce this with `for_each` instead of a local value but ended up blocked by the usual error that `for_each` itself cannot be unknown: ``` ╷ │...

@FernandoMiguel do you have a sense of why `var.fargate_create` was unknown when you tried with v1.2.0-rc2 but apparently known when you tried with v1.1.9? I'm assuming that must be the...

Hi @FernandoMiguel! Thanks for sharing that. I'm sorry I wasn't clear about what I was asking; I was actually hoping to see the assignment of an expression to that variable...

Thanks for that extra context, @FernandoMiguel! I'm not yet understanding how "`var.fargate_create` is a bool, known only after apply" in the original error message if it's just set to a...

Hi @asaba-hashi, In the Terraform language an object type constraint accepts any value that has _at least_ the attributes specified. Any additional attributes are discarded during type conversion. Therefore this...

Indeed, unfortunately it is the fact that blocks are "more difficult to work with" that makes it reasonable to do the stricter validation we've historically done for them: the arguments...

(I no longer work on Terraform at HashiCorp, so the following is just me posting as an individual and not in the voice of the Terraform team.) For what it's...

Hi @samschlegel, The `-state` and `-state-out` options are supported only for the local backend, as a legacy way to override its settings for backward compatibility for earlier versions of Terraform...

Hi all! I just wanted to add some clarity here since my last comment left it a bit ambiguous what this issue was representing, while I was awaiting the response...