Open
Description
Background
It is a best practice to always constrain configuration/module to a particular Terraform version. While this doesn't have to be - and probably should not be - as specific as e.g. =1.6.4
the lack of any constraint is generally considered bad practice.
The reason it's bad practice is because it exposes the future maintainers of that configuration to breaking changes, which are very much to be expected certainly between major versions such as 0.12
and v1
or v2
.
Proposal
- Report warning diagnostic for missing requirement entries inside of
terraform
required_version
- Provide
quickfix
code action which addsrequired_version
entries such as~> X.Y
whereX.Y
is the installedMAJOR.MINOR
version