-
Notifications
You must be signed in to change notification settings - Fork 9.7k
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.
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
Feature Request: Terraform version requirements in configuration files #1400
Comments
Good idea 👍 , that would be helpful especially in these early days when the API is still changing rapidly, although it goes a bit against the whole Golang-concept which forces all developers to "live on the edge" (as you cannot specify versions in I wouldn't want to see people freezing everything forever and complaining about old bugs that have been fixed x releases after. Also I believe that most of the changes are/should be backward-compatible (unless these are bugfixes). Forcing everyone to live on the edge has the advantage that community will give feedback early, which is important. I understand that not everyone (especially in enterprise corporations) wants to live on the edge though. |
In fact these are two different problems
(2) should be definitely addressed, but I'd be careful about (1) as mentioned above. |
👍 There are also more practical reasons for specifying versions. The main one is to ensure that all engineers working against the same terraform configuration files are forced to use a minimum version of terraform. I'm guessing state files include data format / API version (similar to vagrant configuration files). |
👍 yes I'd like to see this as we are constantly upgrading across a medium size team and wanting to avert problems caused by bugs in earlier versions |
This would be a great feature. Please add it. |
Done in PR #10080 :D |
@mitchellh thank you! this is awesome to see happen |
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. |
I'm starting to work on updating the terraform community modules to take advantage of the new split function, but this will leave users on older versions unable to use the latest versions of these modules.
Being able to put some kind of version constraint as a comment in the configuration file could be useful, as new functions are added in newer versions.
I'm going to do my best to call out the version requirement in the documentation but an additional safeguard would also help.
The text was updated successfully, but these errors were encountered: