# 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:** 1\
**Showing post:** 2

<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)).

---

_[View the full topic](https://forum.ansible.com/t/should-we-deprecate-community-general-terraform/44363)._