Martin Atkins comments

Results 1242 comments of


                                            Martin Atkins

Terraform not allowing to pass nested values (like assume_role.role_arn) to the backend.s3 configuration using cli (-backend-config="KEY=VALUE") and config file (-backend-config=PATH)

In case it's somehow useful, _a long time ago_ I wrote [`github.com/apparentlymart/go-hcl-overlay`](https://pkg.go.dev/github.com/apparentlymart/go-hcl-overlay/hcloverlay) with the goal of supporting stuff like this where a system needs to merge some command line options...

Terraform not allowing to pass nested values (like assume_role.role_arn) to the backend.s3 configuration using cli (-backend-config="KEY=VALUE") and config file (-backend-config=PATH)

Ahh hmm yes I suppose I wrote this long enough ago that the idea of using the attribute syntax in a block-like way hadn't happened yet, and so my old...

Resource block plan detail is hidden due to sensitive values since 1.4

Hi @sjparkinson! Thanks for reporting this. Can you confirm whether it's correct that there is at least one sensitive value in an argument in one of your blocks here? I'm...

Resource block plan detail is hidden due to sensitive values since 1.4

Thanks for the additional information, @sjparkinson! I think this one is going to require a product management call to decide, since both the old and the new behavior cause some...

Resource block plan detail is hidden due to sensitive values since 1.4

The set situation is different because if anything in a set is marked as sensitive then the whole set just becomes sensitive, for the coalescing reason I mentioned. That is...

Resource block plan detail is hidden due to sensitive values since 1.4

It isn't clear how to improve this. The old behavior was just ignoring dynamic sensitivity altogether and thus potentially disclosing sensitive values assigned to arguments that aren't marked as sensitive...

Error 'There is no variable named "local"' when using "local" in for_each in a nested block

Hi @ddelbondio! Thanks for reporting this. The problem here seems familiar to me. If I recall correctly, `dynamic` blocks interact quite poorly with the special [Attributes as Blocks](https://opentofu.org/docs/language/attr-as-blocks/) mode that...

Error 'There is no variable named "local"' when using "local" in for_each in a nested block

I looked into the `hashicorp/azurerm` source code and can confirm that [`ip_rule` is indeed opting in to this special legacy treatment](https://github.com/hashicorp/terraform-provider-azurerm/blob/5dfdc6121a2e43d41a239a8c7755e6f48429f3c6/internal/services/containers/container_registry_resource.go#L184), so I think this is the most likely explanation...

Error 'There is no variable named "local"' when using "local" in for_each in a nested block

In case anyone would like to learn more about the "attributes as blocks" implementation I mentioned above, here's some relevant parts of the OpenTofu code. During config block evaluation, just...

Allow automation to automatically discover what permissions a particular configuration might need

Hi @jamesgeddes! Thanks for sharing this. I must admit that I don't think I'm fully understanding your problem statement yet and so the following is focused only on one part...