Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

what if terraform version is not defined in tf files #16

Closed
rootsami opened this issue Feb 5, 2023 · 0 comments · Fixed by #19
Closed

what if terraform version is not defined in tf files #16

rootsami opened this issue Feb 5, 2023 · 0 comments · Fixed by #19
Labels
bug Something isn't working

Comments

@rootsami
Copy link
Owner

rootsami commented Feb 5, 2023

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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix: Validation if terraform version not defined and Add more tests rootsami/terradrift
1 participant
@rootsami