Hi everyone,
This situation with the terraform module has been in my radar (the far hidden corner of it for sure) for a while, and I was just about to write something in the forum when I did the search and found this conversation (What is the difference between community.general.terraform and cloud.terraform.terraform module?) going on.
So I would like to bring back the question: should we deprecate community.general.terraform ?
Skipping the house-keeping PRs from yours truly and @felixfontein , there’s been one PR in May this year to add a no_color option, a handful of PRs in early 2024, mostly dealing with diff output, then another bunch scattered across 2023.
So, there’ s been some maintenance. OTOH, there are 10+ issues pending related directly to TF (as far as I can tell from their summaries), two from 2024, two from 2022 and all the others from 2023. In one of them there is a comment that says:
For anyone looking for a solution, this was implemented in ansible-collections/cloud.terraform in version
1.0.0.cloud.terraform.terraformis backwards compatible withcommunity.general.terraform, at least at the time of release. It also implements diffs, both in check and non-check mode, and planning for destroy operations.
On the cloud.terraform side, since its version 1.0.0 (the git tag is dated Nov 23, 2022), it seems to have published a total of 10 releases, including 3 releases this year. Its latest version is 4.0.0 (Jul 11, 2025). There’s a number of open issues, the oldest one from Dec 2022, but there’s been some being closed as recently as June this year. Something similar with PRs - there are some old ones still hanging on there, but others have been merged in July.
It looks like it is getting considerably more TLC than c.g.terraform.
So, back to question: should we deprecate in favour of cloud.terraform?