Tfenv: Don't change tfenv version globally when entering a directory with a .terraform-version
Didn't know how to resume it better x)
If you set the tfenv version to 0.11.14 and enter a directory with a .terraform-version that points to 0.12.4, it changes the tfenv version globally. That means that when you go outside that directory, it doesn't revert the tfenv version to 0.11.14, it maintains the 0.12.4 version. I think it should do it as the default behaviour.
PD: tfenv it's very cool, thanks for your work!
alexppg
All 4 comments
Think this ties into another ticket or so addressing how we deal with version files and the use command. It's on the list.
Zordrak
on 29 Oct 2019
On mac, the mechanism of /usr/local/bin/terraform creates this problem. tfenv should be setting PATH or similar for the right version of terraform in the environment rather than creating symlinks or other files on the FS which acts globally.
Doing such things means its not possible to run concurrent terraform invocations with different versions using this tool.
(Sure you knew that anyway, but thats my problem - which means i cant use tfenv at all for CI)
gtmtech
on 30 Jan 2020
Not addressing this (environment manipulation instead of system-level default) in v2.0.0 as 2.0.0 is a significant rewrite that is already stable; will perhaps look at it for v2.1.0.
Two solutions for CI configurations where parallel execution is required:
- You can use .terraform-version files. No
usecommand is required, just executeterraformwith a .terraform-version file that is unique to the CI execution. - Clone the TFENV_ROOT within the CI execution environment as you can have as many tfenv installations as you like, and the one your path points at is unaffected by others. tfenv total size is incredibly small.
Zordrak
on 16 Feb 2020
See https://github.com/tfutils/tfenv/tree/v2.0.0-beta1 for the 2.0.0 release candidate. Now does not overwrite .terraform-version files.
Zordrak
on 16 Feb 2020
Related issues
Constantin07
·
8Comments
dkolb
·
6Comments
ibakayoko
·
6Comments
sthristov
·
5Comments
itsSaad
·
6Comments
Most helpful comment
On mac, the mechanism of /usr/local/bin/terraform creates this problem. tfenv should be setting PATH or similar for the right version of terraform in the environment rather than creating symlinks or other files on the FS which acts globally.
Doing such things means its not possible to run concurrent terraform invocations with different versions using this tool.
(Sure you knew that anyway, but thats my problem - which means i cant use tfenv at all for CI)