Hi,
I was wondering if can be used RunTerraformCommandE which will return an error and output

https://github.com/gruntwork-io/terratest/blob/master/modules/terraform/cmd.go#L68

Hi @denis256 yes that would be a possibility, I have realised that actually if we do use InitAndPlanE(...) we do get the standard output already, so if we know that the terraform plan won't be executed (as this is my use case) we can use these methods and forget about those calls that return PlanStruct without the logs.
I think it may be still useful to both have the plan parsed and the log. But it is not necessary for this use case.

Ok, now I have realised what is the issue with the use of the approach you have proposed. A common test case may be that we execute terraform plan and we expect the plan to fail. Hence we want to do the following:

• check the exit code
• check the log for some specific message
  at present time we have methods for doing this independently, but if we choose one way, we aren't able to do get the other.

We can rewrite in our testing logic the implementation of:

This may not be very good over time as we depend on the internal implementation of the method.

I would imagine that having the ability to get back both the exit code and the stdout/stderr (perhaps as two separate strings) would a generally useful feature.