Liam Cervante

This happens when we read the changes back from the `json.RawMessage` format they are stored in the json plan file. This is here: https://github.com/hashicorp/terraform/blob/main/internal/command/jsonformat/structured/change.go#L277 Essentially, the numbers are bigger than...

Hi @alexis-renard, thanks for filing this! It's an interesting idea, and I can confirm that this isn't currently supported. Currently, Terraform Test does respect the encapsulation of modules much like...

I'm not particularly sure what is causing those errors, but hopefully they'll go away once I import a real version of HCL :/

`terraform test` is re-performing the validation on variables during the cleanup, when this was already validated during the actual execution of the test. The particular problematic validation is that we...

Hi @MicahKimel, apologies for the delay here - I was away on annual leave. Yes, I think that's fine but we could also update the doc comment for the function...

Hi @brettcurtis, thanks for the feature request. Is there a reason you can't place the test files / test directory within your `global` directory and run `terraform init` and `terraform...

@apparentlymart, I've added support for the apply phase as well and would appreciate another review! Thanks!

Hi @deepbrook, thanks for filing this. This is an issue with our upstream type library, tracked here: https://github.com/zclconf/go-cty-yaml/issues/11. It seems like this behaviour is expected in YAML 1.1: https://yaml.org/type/bool.html. You...

Hi @lorengordon, thanks for the feedback. Currently, `terraform test` will provide a set of diagnostics that describes any state left behind if the destroy action fails. I do like the...

I've considered this a bit further and I will say that we won't see any changes here for the launch of `v1.6`. The test command at the moment doesn't have...