# New vmware.vmware collection and impact on community.vmware

**URL:** <https://forum.ansible.com/t/new-vmware-vmware-collection-and-impact-on-community-vmware/5880>\
**Category:** Project Discussions\
**Tags:** vmware, aws, collections, galaxy-ng\
**Created:** [May 20, 2024, 2:06pm UTC](https://forum.ansible.com/t/new-vmware-vmware-collection-and-impact-on-community-vmware/5880 "2024-05-20T14:06:18Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![mariolenz](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/mariolenz/32/108_2.png) [@mariolenz](https://forum.ansible.com/u/mariolenz)\
**Post date:** [May 20, 2024, 2:06pm UTC](https://forum.ansible.com/t/new-vmware-vmware-collection-and-impact-on-community-vmware/5880/1 "2024-05-20T14:06:18Z")

</div>

You might have seen that there is a new [vmware.vmware collection](https://galaxy.ansible.com/ui/repo/published/vmware/vmware/) (the repository on GitHub is [here](https://github.com/ansible-collections/vmware.vmware)) and wondered what this means for the existing `community.vmware` collection. If you haven’t seen this yet, you probably wonder now 😏

The new collection is maintained and supported by the Ansible cloud team, that is Red Hat, while `community.vmware` continues to be maintained by the community. This is similar to the relationship between [amazon.aws](https://galaxy.ansible.com/ui/repo/published/amazon/aws/) and [community.aws](https://galaxy.ansible.com/ui/repo/published/community/aws/), in case you know those collections.

But what does this mean for `community.vmware`? First things first, this collection will stay! At the moment, there’s a request to include the new collection in the [Ansible community package](https://pypi.org/project/ansible/). Until this hasn’t been approved and implemented, `community.vmware` will just continue as if the new collection doesn’t exist.

But _if_ the new collection is included, we shouldn’t split forces. That is, we don’t want to have modules implementing the same thing in both collections. In this case, modules that are also in `vmware.vmware` will be deprecated in `community.vmware`. Also, we will try to re-use the module utils from `vmware.vmware` in `collection.vmware` where possible. Although this would probably only happen in the first major release of `community.vmware` after `vmware.vmware` has been included in Ansible.

---

<div class="post-metadata">

**Author:** ![mariolenz](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/mariolenz/32/108_2.png) [@mariolenz](https://forum.ansible.com/u/mariolenz)\
**Post date:** [July 19, 2024, 3:43pm UTC](https://forum.ansible.com/t/new-vmware-vmware-collection-and-impact-on-community-vmware/5880/2 "2024-07-19T15:43:53Z")

</div>

FYI vmware.vmware has been added to the [Ansible Community Package 10.2.0](https://github.com/ansible-community/ansible-build-data/blob/main/10/CHANGELOG-v10.rst#added-collections).