When using different terraform version in atlantis.yaml , it gives an error "Unsupported Terraform Core version"

[khatib-moh]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request. Searching for pre-existing feature requests helps us consolidate datapoints for identical requirements into a single place, thank you!
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.
• If you are interested in working on this issue or have submitted a pull request, please leave a comment.

---

Overview of the Issue

If not already included, please provide the following:

• Atlantis version: v0.20.1 and also i tried it with v0.24.0 and still the same error
• Deployment method: helm
• If not running the latest Atlantis version have you tried to reproduce this issue on the latest version: yes
• Atlantis flags:

Atlantis server-side config file: repos:

• id: /.*/ apply_requirements: [mergeable,approved,undiverged] workflow: default allowed_overrides: [workflow] allow_custom_workflows: true workflows: default: plan: steps:
  • run: set -x; terragrunt-atlantis-config generate --output atlantis.yaml --autoplan --parallel --create-workspace
  • env: name: TERRAGRUNT_TFPATH command: 'echo "terraform${ATLANTIS_TERRAFORM_VERSION}"'
  • run: set -x; terragrunt plan -input=false -out=$PLANFILE
  • run: set -x; terragrunt show -json $PLANFILE | tee output.json $SHOWFILE > /dev/null apply: steps:
  • env: name: TERRAGRUNT_TFPATH command: 'echo "terraform${ATLANTIS_TERRAFORM_VERSION}"'
  • run: terragrunt apply -input=false $PLANFILE

Any other information you can provide about the environment/deployment (efs/nfs, aws/gcp, k8s/fargate, etc) --->

Additional Context

[khatib-moh]

Hi , i think that the description is missing from the issue , i don't know why , anyway my issue is when i use terraform_version in atlantis and use a custom workflow at the same time like the below atlantis.yaml:

version: 3 projects:

• dir: . terraform_version: v1.4.5 workflow: staging workflows:

  staging: plan: steps:

  • run: echo "hi"
  • run: terraform init
  • run: terraform plan

it gives me an error related to the core version , it only works after i add this to the custom workflow

• run: terraform1.4.5 init #### instead of just terraform init .
• run: terraform1.4.5 plan ### instaed of terraform plan . so is there a way that terraform knows the version from terraform_version flag , so i don't have so specify it .

Thanks,

[nokernel]

@khatib-moh Is there a required_version in the terraform module(s) HCL that you are trying to apply?

[artburkart]

I'm experiencing the same thing. I'm trying to figure out why this happens. Unfortunately, we'd upgraded from Atlantis 0.19 to 0.25, so I can't tell where the bug is introduced, but without any changes to our configurations, we're seeing output like this after the upgrade:

Error: Unsupported Terraform Core version

  on remote-config.tf line 2, in terraform:
   2:   required_version = "1.3.5"

This configuration does not support Terraform version 1.5.5. To proceed,
either choose another supported Terraform version or update this version
constraint. Version constraints are normally set for good reason, so updating
the constraint may lead to other errors or unexpected behavior.

[artburkart]

Oh, I think I understand what happened. At some point, between 0.19 and 0.25, I think Atlantis got more strict about the required_version block, and if you have it defined twice, it returns nil for the detected version, and that means it uses the default installed version instead of the one defined in the project.

[jamengual]

yes we did change the behaviour to be more strict but we introduced a bug where the default version is not being selected.