atlantis: Cannot use `remote` backend on TFC using terraform 0.14.x+
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
I am using the pre-release from 12/26, and I still seem to have the issue with remote execution in Terraform versions greater that 1.1 (I have tried several, from 1.1.2, 1.2, and 1.3.6). I expected this to be fixed by #2793
β Error: Saving a generated plan is currently not supported
β
β The "remote" backend does not support saving the generated execution plan
β locally at this time.
β΅
I was able to work around the issue by overriding the plan workflow with no -out parameter, but the functionality is a bit reduced in Github (the link goes to Atlantis, not terraform cloud)
Reproduction Steps
Using Atlantis image tag v0.22.0-pre.20221226 hooked up to Github, try planning a terraform project that uses terraform cloud as the remote backend, with remote execution enabled. Use terraform 1.3.6 (latest at time of writing)
Logs
I donβt have the logs, as they have already been rotated after implementing the workaround
Environment details
Atlantis v0.22.0-pre.20221226 installed via Helm in K8s Github Terraform Cloud TF Version 1.3.6
Additional Context
There have been several issues related to this. Most are linked in #2793
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Comments: 16 (9 by maintainers)
I understand your frustration. You have created this issue and itβs a real issue even if it no longer affects you. Letβs keep it open and re-title it so everyone knows that this is a problem for terraform 0.14.x and higher.
cc: @lilincmu in case you have run into this issue or you have thoughts on this.