Liam Cervante

I'm closing this issue, as we have now released a redesigned `terraform test` command. Please try it out, and file a new issue if this behaviour has persisted between the...

I think this issue is now obsolete with the release of the finalised test command. If you can reproduce this with the new test configuration then please open a new...

I think this issue is now obsolete with the release of the finalised test command. If you can reproduce this with the new test configuration then please open a new...

Hi everyone and thanks for your interest! Terraform currently evaluates input variables statically, that is to say that they are evaluated in isolation when the configuration is parsed and do...

Hi @KetchupBomb, thanks for filing this! And, thanks for the easy-to-reproduce example configuration. One thing to note is the `create_before_destroy` lifecycle option: ```terraform resource "terraform_data" "child" { // attributes... lifecycle...

Hi @nrv-96, what do you mean by exportable in this context? It's worth noting that sensitive values are still available within the state even after they have been created. This...

Hi @xyl0o, thanks for filing this! I'll just note this behaviour isn't unique to the testing framework. All custom condition checks (including test assertions, pre and post conditions, variable validations,...

The output of functions called inside an expression are not available externally. Terraform simply doesn't have access to the nonsensitive value returned by the `nonsensitive` call inside the expression, and...

This might be a result of the security fix in https://github.com/hashicorp/terraform/releases/tag/v1.9.1. @alexhung, are you including timing of `terraform init` in your local runs and / or in the acceptance tests?

Hi @dnmvisser, thanks for filing this. The error message you linked contains the following explanation: > Terraform assumed that you intended a module registry source address because you also set...