This message was deleted.
# atlantis-community
s
This message was deleted.
c
Do you have a conflicting version constraint in a module or something?
j
No. Atlantis is the latest helm c hart, latest image. with a default version of 1.5.2
this project, has 1.3.7 declared
c
We have this pop up all the time, a module requires 1.5 or something but the root is locked to 1.3
Hrm.
j
and this was all working, before we upgraded our defualt version from 1.3.7, to 1.5.2
so this existing project, has not actually had a change
m
atlantis is blame free here, the above is a pure Terraform version validation error, it even points to the file needs to be fixed:
Copy code
on <http://backend.tf|backend.tf> line 2, in terraform:
│    2:   required_version = "= 1.3.7"
j
that doesnt answer the question
that is a valid version of TF, and the error started after telling Atlantis its new default version is 1.5.2
YOu have 1 atlantis. with N+1 projects in it. They should not be required to use the same version of TF.
m
you will get the same error even if Atlantis is not used at all. if your modules (based on
Upgrading modules...
) require a version that’s not compatible with what set root/env module (e.g
<http://backend.tf|backend.tf>
) then you will get the same error.
j
they are compatible
this all worked without a problem
until the default TF version of atlantis was upgrade
atlantis should see that the required version is 1.3.7 and use it, since its explicitly set, instead of defaulting to 1.5.2
w
are you using a fairly recent version? edit: I see the comment above about running latest version one thing we came across was this bug, though it’s since been fixed
I’m curious if you use
required_version = "1.3.7"
instead if it works
or even
required_version = "=1.3.7"
j
ill play with it