# Unmaintained collection: vyos.vyos **URL:** \ **Category:** Project Discussions\ **Tags:** community-wg, collections, galaxy-ng\ **Created:** [June 7, 2024, 3:03pm UTC](https://forum.ansible.com/t/unmaintained-collection-vyos-vyos/6244 "2024-06-07T15:03:41Z")\ **Posts on this page:** 11\ **Page:** 1
**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:** [June 7, 2024, 3:03pm UTC](https://forum.ansible.com/t/unmaintained-collection-vyos-vyos/6244/1 "2024-06-07T15:03:41Z")
There has been a deprecation announcement in [The Bullhorn #123](http://forum.ansible.com/t/2568) for the [vyos.vyos](https://github.com/ansible-collections/vyos.vyos) collection. It says there won’t be any more major releases, but I don’t see any minor or even bugfix release either for quite some time. There is no information about deprecation neither in the repo nor on [galaxy](https://galaxy.ansible.com/ui/repo/published/vyos/vyos/). However, I suggest to remove it ASAP. That is in the Ansible Community Package 11. ---
**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:** [June 8, 2024, 12:34pm UTC](https://forum.ansible.com/t/unmaintained-collection-vyos-vyos/6244/2 "2024-06-08T12:34:59Z")
I have created a [Removal from Ansible Community Package](https://github.com/ansible-collections/vyos.vyos/issues/344) issue in the repository. It’s loosely based on the text that I use for the [Identifying and removing an unmaintained collection process](https://docs.ansible.com/ansible/devel/community/collection_contributors/collection_package_removal.html#id6). But since they did announce the removal in The Bullhorn but nowhere else, this doesn’t really fit and I’ve improvised a bit. ---
**Author:** ![briantist](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/briantist/32/130_2.png) [@briantist](https://forum.ansible.com/u/briantist)\ **Post date:** [June 8, 2024, 1:35pm UTC](https://forum.ansible.com/t/unmaintained-collection-vyos-vyos/6244/3 "2024-06-08T13:35:01Z")
> I have created a Removal from Ansible Community Package issue in the repository. vyos con dios ---
**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:** [June 11, 2024, 3:32pm UTC](https://forum.ansible.com/t/unmaintained-collection-vyos-vyos/6244/4 "2024-06-11T15:32:16Z")
FYI someone from VyOS [answered](https://github.com/ansible-collections/vyos.vyos/issues/344#issuecomment-2160492677) my issue. Not sure if this will lead to anything, though. ---
**Author:** ![nilashishc](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/nilashishc/32/3961_2.png) [@nilashishc](https://forum.ansible.com/u/nilashishc)\ **Post date:** [June 13, 2024, 3:30am UTC](https://forum.ansible.com/t/unmaintained-collection-vyos-vyos/6244/5 "2024-06-13T03:30:00Z")
Hello @mariolenz! I’m from the Ansible Network team, that maintains the vyos.vyos collection. This collection was deprecated in December, 2023 and will reach end-of-life on December, 2025. During this period, we will _only_ be doing patch releases for this collection if a critical bug or security vulnerability has been reported. We will continue to run `ansible-test` in CI for ansible-core\<=2.17, \>=2.15 and as such compatibility with ansible-core versions \>2.17 will not be guaranteed. I have opened a PR that fixes the sanity failure with \>=stable-2.16 and also an update to the README mentioning all the above. (Apologies to the Community for not doing that along with the Bullhorn announcement.) Please let me know if the above points would qualify this collection to continue being included in the Ansible Community Package. Thank you! ---
**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:** [June 13, 2024, 3:29pm UTC](https://forum.ansible.com/t/unmaintained-collection-vyos-vyos/6244/6 "2024-06-13T15:29:27Z")
Maybe it’s easier to discuss this in [Several collections have been deprecated by the Ansible Network team](http://forum.ansible.com/t/6360). ---
**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:** [June 20, 2024, 6:38pm UTC](https://forum.ansible.com/t/unmaintained-collection-vyos-vyos/6244/7 "2024-06-20T18:38:09Z")
[Remove frr.frr and openvswitch.openvswitch](https://github.com/ansible-community/ansible-build-data/pull/437) Let’s move the discussion about `vyos.vyos` back here. ---
**Author:** ![gundalow](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/gundalow/32/99_2.png) [@gundalow](https://forum.ansible.com/u/gundalow)\ **Post date:** [June 24, 2024, 2:37pm UTC](https://forum.ansible.com/t/unmaintained-collection-vyos-vyos/6244/8 "2024-06-24T14:37:01Z")
Hi, Ansible Engineering and the VyOS team have just met. The VyOS Team will be become the maintainers of the `vyos.vyos` collection. We’ve got a few things to tidy up (including removing the deprecation notice) then we will release a new version of the collection. The collection WILL be staying in the `ansible` community package. ---
**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:** [June 24, 2024, 3:30pm UTC](https://forum.ansible.com/t/unmaintained-collection-vyos-vyos/6244/9 "2024-06-24T15:30:57Z")
Cool! I’ll tick it off in [Possibly unmaintained collections in Ansible 10](http://forum.ansible.com/t/6162) once there’s a new release. Don’t hesitate to ping me in case I overlook it. BTW since the deprecation has been announced on Bullhorn, it would be great if someone would also announce there that the VyOS team took over and the collection is maintained again / not deprecated anymore. ---
**Author:** ![gundalow](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/gundalow/32/99_2.png) [@gundalow](https://forum.ansible.com/u/gundalow)\ **Post date:** [June 24, 2024, 5:47pm UTC](https://forum.ansible.com/t/unmaintained-collection-vyos-vyos/6244/10 "2024-06-24T17:47:21Z")
> BTW since the deprecation has been announced on Bullhorn, it would be great if someone would also announce there that the VyOS team took over and the collection is maintained again / not deprecated anymore. Good idea, I’ve done this. ---
**Author:** ![nilashishc](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/nilashishc/32/3961_2.png) [@nilashishc](https://forum.ansible.com/u/nilashishc)\ **Post date:** [June 24, 2024, 6:03pm UTC](https://forum.ansible.com/t/unmaintained-collection-vyos-vyos/6244/11 "2024-06-24T18:03:19Z")
FYI - This PR makes all necessary updates for `vyos.vyos` to remain in the Ansible community package: > > > \##### SUMMARY > \- Fixes #344 > \- Maintenance PR to allow vyos.vyos continue to be …a part of Ansible Community Package. > \- Updates all GHA workflows to use ansible-content-actions. > \- 200+ ansible-lint fixes. > \- Removes deprecation notice from README.