Martin Atkins

Hi @anilkumarmyla! Thanks for reporting this. Input variable values are specified as part of the planning options, and so input variables do not have known values during the validation phase....

Hi @anilkumarmyla, Indeed, this is a quirk of static vs. dynamic configuration constructs. Terraform typically treats arguments inside blocks as a "static" concern, because their presence cannot possibly vary based...

We _have_ decided to show `toset([ ... ])` in some other contexts where things are more ambiguous, such as in `terraform console` and in output values. What makes this situation...

Set elements don't have indices, because there is no stored order for set elements. Sets represent the relatively common case in many remote APIs where there's just a collection of...

This seems related to https://github.com/hashicorp/terraform/issues/31102, which was caused by a similar ambiguity between tuple types and list types. Considering that this has now caused at least two different variations of...

Hi @dansimau! Thanks for sharing this use-case. As you've noted, the typical way to deal with this today is for the provider to explain to Terraform that "update cognito user...

That's an interesting idea, @okaros, and reminds me a bit of functional reactive programming where programs react to events by merging the event data in with a previous value. It...

One example of this pattern that I can think of quickly is in the `hashicorp/aws` provider: There are separate resource types for `aws_s3_bucket` and `aws_s3_bucket_policy`, which allows the policy to...

There is a separate team responsible for the `hashicorp/aws` provider and so I don't know all of what motivates their design decisions, but in this particular case (the S3 operations)...

Hi @stevemckenney! Thanks for sharing that feedback. Could you link to the specific modules you're referring to? I'm not aware of any HashiCorp-maintained modules for either Lambda or EventBridge, and...