RB

I know it's an old issue. I'm interested in this fix. @willjw1 you'll need to fork the repository, push your branch to the fork, and then open a PR in...

What you probably want to use is `~> 1.3.0` or `= 1.3.9` for `required_version`. https://www.runatlantis.io/docs/terraform-versions.html#via-terraform-config

I think he's saying that he wants to set a global default terraform version using `ATLANTIS_DEFAULT_TF_VERSION` in spite of the `required_version`. Whereas the current workflow in `atlantis` is to override...

Perhaps we need a new flag such as this? ``` ATLANTIS_AUTODOWNLOAD_TERRAFORM=false ``` It can default to true unless specified as false. By enabling this potential flag, atlantis will stop reading...

That is indeed odd. For me, I've been able to use `required_version = "~> 1.3.0"` and have it match `1.3.9` successfully. If you folks think we should have a new...

Another flag that could be added to allow downloading but give it a maximum version so there is a central place where the tf version can be controlled ``` ATLANTIS_AUTODOWNLOAD_TERRAFORM_MAX="1.3.9"...

cc @zhuoyang author of https://github.com/runatlantis/atlantis/pull/3153

this might be a tricky implementation. Let me cc others for their thoughts - @krrrr38 since they implemented pr https://github.com/runatlantis/atlantis/pull/2805 - @rayterrill due to implementing https://github.com/runatlantis/atlantis/pull/2436

@Dawnflash does using `--executable-name` from 0.22.3 reduce or resolve this problem?

Repository rules would be ideal. @edbighead did some sleuthing and found that switching from branch protection to repository rules is not currently possible due to our reliance on GetBranchProtection https://github.com/runatlantis/atlantis/blob/6ff0e2f90e5aa70fc76d8498eeec745306697a7b/server/events/vcs/github_client.go#L417