# Keycloak modules in community.general

**URL:** <https://forum.ansible.com/t/keycloak-modules-in-community-general/41746>\
**Category:** Project Discussions\
**Tags:** middleware, keycloak, community-general, awx\
**Created:** [April 15, 2025, 5:30pm UTC](https://forum.ansible.com/t/keycloak-modules-in-community-general/41746 "2025-04-15T17:30:49Z")\
**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:** [April 15, 2025, 5:56pm UTC](https://forum.ansible.com/t/keycloak-modules-in-community-general/41746/2 "2025-04-15T17:56:14Z")

</div>

Regarding the process: I wrote that down for community.proxmox here: [What's up with proxmox.community? - #2 by felixfontein](https://forum.ansible.com/t/41697/2) For a Keycloak collection it would be the same, up to updating the names in that process 😉

If there is one or more maintainer who wants to maintain that collection, that’s perfect! From c.g’s point of view, there’s no reason to not move the modules. The main reasons to not move content out of community.general in the past have been:

1. There haven’t been maintainers for collections for a set of modules/plugins. (That’s still the main reason why it is not happening more often.)
2. We had a rule that content from collections included in Ansible can only be moved to collections that are also part of Ansible. That prevented some moves, but [we removed that rule anyway](https://forum.ansible.com/t/5738/13). So this is no longer preventing anything.

---

_[View the full topic](https://forum.ansible.com/t/keycloak-modules-in-community-general/41746)._