# Should we deprecate community.general.terraform?

**URL:** <https://forum.ansible.com/t/should-we-deprecate-community-general-terraform/44363>\
**Category:** Project Discussions\
**Tags:** terraform, community-general, deprecation\
**Created:** [August 23, 2025, 7:34pm UTC](https://forum.ansible.com/t/should-we-deprecate-community-general-terraform/44363 "2025-08-23T19:34:38Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![russoz](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/russoz/32/127_2.png) [@russoz](https://forum.ansible.com/u/russoz)\
**Post date:** [August 23, 2025, 7:34pm UTC](https://forum.ansible.com/t/should-we-deprecate-community-general-terraform/44363/1 "2025-08-23T19:34:38Z")

</div>

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?](https://forum.ansible.com/t/what-is-the-difference-between-community-general-terraform-and-cloud-terraform-terraform-module/6102)) going on.

So I would like to [bring back the question: should we deprecate](https://github.com/ansible-community/community-topics/issues/192)`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](https://github.com/ansible-collections/community.general/issues/807#issuecomment-1408097856) that says:

> For anyone looking for a solution, this was implemented in [ansible-collections/cloud.terraform](https://github.com/ansible-collections/cloud.terraform/?rgh-link-date=2023-01-30T07%3A09%3A44.000Z) in version `1.0.0` . `cloud.terraform.terraform` is backwards compatible with `community.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`?

---

<div class="post-metadata">

**Author:** ![felixfontein](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/felixfontein/32/7530_2.png) [@felixfontein](https://forum.ansible.com/u/felixfontein)\
**Post date:** [August 24, 2025, 3:27pm UTC](https://forum.ansible.com/t/should-we-deprecate-community-general-terraform/44363/2 "2025-08-24T15:27:59Z")

</div>

The good thing is that the main question which was blocking [Remove or deprecate community.general.terraform · Issue #192 · ansible-community/community-topics · GitHub](https://github.com/ansible-community/community-topics/issues/192) is now solved: we voted that it’s fine to remove things from community.network/community.general to collections outside of Ansible community package ([[Vote ended on 2024-10-23] Should we allow moving content out of community.general and community.network to collections that are not part of Ansible?](https://forum.ansible.com/t/5738)).