You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently if terraform version is not defined in tf files, it throws an error.
ERRO[0000] no problems stack=gcp-core-staging
ERRO[0000] running NewTerraform: no suitable terraform binary could be found: NewTerraform: please supply the path to a Terraform executable using execPath, e.g. using the github.com/hashicorp/hc-install module. stack=gcp-core-staging
How to reproduce it:
remove the block and run terradrift against the example stacks
Possible Actions:
Enhance error handling to show what's actually wrong.
Validation if terraform version is not defined.
Defaulting to the latest version is possible, however, it might cause an issue for the user by upgrading the remote state which is out of terradrift scoop by running terraform init with a later tf version
The text was updated successfully, but these errors were encountered:
Currently if terraform version is not defined in tf files, it throws an error.
How to reproduce it:
remove the block and run terradrift against the example stacks
Possible Actions:
terraform init
with a later tf versionThe text was updated successfully, but these errors were encountered: