Plan files cannot be transferred between different Terraform versions about rover HOT 4 OPEN

This is more a Terraform thing than a rover thing. Under the hood, rover runs a version of terraform show to parse the plan file.

The changes I've implemented in the tfc-integration branch kinda resolves this (c/p from #34 (comment)). This new feature allows you to reference a plan JSON file, which makes it more robust. Rover can parse it, regardless of the current Terraform version you're running locally and in the pipeline.

I'm planning on cutting a release for this feature next week, but if it's urgent, you can build the binary from the tfc-integration branch.

Initial code on tfc-integration branch can take Terraform plan as a JSON, just need to implement pull from the Terraform Cloud API.

I tested it locally using go run . -planJSONPath=plan.json -tfConfigExists=false and verified it worked. To generate JSON configuration in local configuration, first, generate the planfile:

terraform plan -out=plan.out

then, write the planfile into a JSON:

terraform show -json plan.out > plan.json

from rover.

Oh interesting, did you download rover locally on your machine? it defaults to using the same terraform binary you're using to generate your plan 🤔

from rover.

Yeah I am using rover locally, but the plan file is from a pipeline, so a different terraform binary.

from rover.

Any word on this feature being released @im2nguyen ?

from rover.