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
I've just started working on a team with a repository which has a .terraform-version file in, which is consumed by tfenv. tfenv works in a very similar fashion to tools such as rbenv, in that it wraps installation and management of a particular version of Terraform.
I refactored a bit of our code base to make use of required_version in the terraform block, as per the docs, but wanted to read in the value from the .terraform-version file, which just contains the version:
$ cat .terraform-version
0.9.3
Unfortunately, it seems the required_version parameter doesn't accept string interpolations, so I can't read the version in using:
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
ghost
locked and limited conversation to collaborators
Apr 6, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hello,
I've just started working on a team with a repository which has a
.terraform-version
file in, which is consumed bytfenv
.tfenv
works in a very similar fashion to tools such asrbenv
, in that it wraps installation and management of a particular version of Terraform.I refactored a bit of our code base to make use of
required_version
in theterraform
block, as per the docs, but wanted to read in the value from the.terraform-version
file, which just contains the version:Unfortunately, it seems the
required_version
parameter doesn't accept string interpolations, so I can't read the version in using:Is there a reason
required_version
doesn't accept string interpolations?Cheers,
Andrew
The text was updated successfully, but these errors were encountered: