fix: use Terraform-supported tfenv instead of ours #846
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Before we've been using our own version of this tool, but I've been getting this error. They have recommendations, but the easiest thing I could think of is upgrading this tfenv dependency to the latest supported version. By manually tweaking this value, I could run
make applyandmake planwithout any blocking popups.The only difference between the czi version and the official one is this change, but I don't know if this change matters or not. If it doesn't and we use the tfutils repo, we can archive the czi repo.
Test Plan
Say unittests, or list out steps to verify changes.
References
https://support.hashicorp.com/hc/en-us/articles/13177506317203
https://www.storagetutorials.com/solved-terraform-will-damage-your-computer/