Martin Atkins

Thanks for confirming, @stefano-franco! I'm going to mark this as "accepted" on the assumption that upgrading to a suitably-new AWS SDK for Go is sufficient to address it, since we...

I just noticed that I carelessly wrote "close" before this issue number in https://github.com/opentofu/opentofu/pull/3364 and so this got auto-closed. I think this probably _is_ now fixed, but I'm going to...

We also today released [v1.11.0-beta1](https://github.com/opentofu/opentofu/releases/tag/v1.11.0-beta1), in case it's easier to test a beta release than a nightly build. 😀 I'm going to preemptively create a PR for the new changelog...

Thanks for keeping at it, @stefano-franco! We're currently optimistically assuming that the AWS SDK upgrade will be enough to make this work and have updated the changelog for the forthcoming...

Thanks for testing that, @stefano-franco! I'm glad it worked. In that case, I'm going to close this issue now. I do want to recognize that the credit for this mainly...

I think this is the same as https://github.com/opentofu/opentofu/issues/2993, so it might already be fixed on the `main` branch.

The problem for https://github.com/opentofu/opentofu/issues/2993 was that the mock mechanism in the test framework was constructing an invalid `cty.Type` whenever it encountered an attribute whose type is given in the `NestedType`...

I hesitated to close this at first since we don't seem to have a reproduction case0 to check with, but given the very strong similarity of the stack trace with...

Thanks for this feature request, @kenielf! The core maintainers will discuss this proposal and make a decision on it, but that can take some time because there is a backlog...

The way I've most commonly seen folks work around the current behavior is to split the sensitive and non-sensitive information into two separate output values, or to not include the...