# Unmaintained collection: ngine\_io.cloudstack **URL:** \ **Category:** Project Discussions\ **Tags:** community-wg, collections\ **Created:** [June 28, 2024, 4:21pm UTC](https://forum.ansible.com/t/unmaintained-collection-ngine-io-cloudstack/6840 "2024-06-28T16:21:22Z")\ **Posts on this page:** 9\ **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 28, 2024, 4:21pm UTC](https://forum.ansible.com/t/unmaintained-collection-ngine-io-cloudstack/6840/1 "2024-06-28T16:21:22Z")
The [ngine\_io.cloudstack](https://github.com/ngine-io/ansible-collection-cloudstack) collection looks unmaintained / abandoned, it has: - no new commits since July 2023 (well, there have been some commits but they’ve been from a bot, no person working on it) - no new release since [Dec 4, 2022](https://github.com/ngine-io/ansible-collection-cloudstack/releases) - No reaction on [Migrate the Cloudstack scenario guide](https://github.com/ngine-io/ansible-collection-cloudstack/issues/126) - No reaction on [Consider using true/false for all booleans in docs](https://github.com/ngine-io/ansible-collection-cloudstack/issues/119) Additionally, I don’t see any tests they’re running (although I might be too stupid to find them). ---
**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 29, 2024, 9:06am UTC](https://forum.ansible.com/t/unmaintained-collection-ngine-io-cloudstack/6840/2 "2024-06-29T09:06:06Z")
@resmo Hi, Are you still interested in the `ngine_io.cloudstack` and do have time to maintain it? ---
**Author:** ![resmo](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/resmo/32/470_2.png) [@resmo](https://forum.ansible.com/u/resmo)\ **Post date:** [June 29, 2024, 10:42am UTC](https://forum.ansible.com/t/unmaintained-collection-ngine-io-cloudstack/6840/3 "2024-06-29T10:42:53Z")
Hello - we publish when significant changes have been made. As you mentioned, only updates related to CI etc have been made. So what is the point? Should we make publications … without changes? The collection is in use and works as it is. At the moment there is no effort to further expand api coverage and development as this is not our priority. - No response does not mean no reaction, but that action has been taken that is not visible to anyone. If you want a response, the committee should make it clear in the question that a response is required! - true/false is not a “feature” currently being worked on in the docs. Even in Ansible’s core modules, there are modules that still have a no/yes syntax. If that’s a reason to throw a working collection out of the community package, go for it… I have a strong feeling that this “cleanup” of working and used collections will only lead to Ansible losing relevance. “You can install collections manually”: → Yes, you can, but AFAIK there is no (for years) integrated update mechanism to update collections and roles. So you have to manually check for updates via more and more roles and collections… do we really think this is the way to go? Just my 2 cents. ---
**Author:** ![resmo](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/resmo/32/470_2.png) [@resmo](https://forum.ansible.com/u/resmo)\ **Post date:** [June 29, 2024, 10:49am UTC](https://forum.ansible.com/t/unmaintained-collection-ngine-io-cloudstack/6840/4 "2024-06-29T10:49:12Z")
As far as I can tell, ngine\_io.cloudstack works, and is in use and whenever I see a need, I try to find time to work on it but I am not sure if this fits your definition of “maintained”. ---
**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 29, 2024, 11:49am UTC](https://forum.ansible.com/t/unmaintained-collection-ngine-io-cloudstack/6840/5 "2024-06-29T11:49:43Z")
@resmo Thanks for the quick reply. You are totally correct, I don’t want to encurage any wasteful work. If the collection works and ansible-test still passes against latest version, then the Collection is good, and should stay in the `ansible` community package. A stable collection may go a long time between updates. Nice use of [Scheduled GitHub Actions](https://github.com/ngine-io/ansible-collection-cloudstack/blob/master/.github/workflows/sanity.yml#L6-L7) to ensure CI keeps running. Seems like the only tweak might be to add the previous stable version of `ansible-core` into the [Sanity Test matrix](https://github.com/ngine-io/ansible-collection-cloudstack/blob/master/.github/workflows/sanity.yml#L21-L25). And maybe see why integration tests started to [fail 6 months ago](https://github.com/ngine-io/ansible-collection-cloudstack/actions?page=3) Thanks for suggesting we improve our wording to be clear about “the ask” and clearly defining the question. > [@mariolenz](#): > > Additionally, I don’t see any tests they’re running (although I might be too stupid to find them). At the top of the repo, click `Actions` which takes you to [this page](https://github.com/ngine-io/ansible-collection-cloudstack/actions). ---
**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 29, 2024, 1:09pm UTC](https://forum.ansible.com/t/unmaintained-collection-ngine-io-cloudstack/6840/6 "2024-06-29T13:09:47Z")
> [@resmo](#): > > we publish when significant changes have been made. As you mentioned, only updates related to CI etc have been made. So what is the point? _Since July 2023_. As it looks, the [additional supported\_services in network offering](https://github.com/ngine-io/ansible-collection-cloudstack/pull/123) haven’t been released yet. This might not be a significant change, but it looks like an improvement that is lost to the users of your collection. At least to those who don’t install directly from GitHub. So it’s not _only_ updates to the CI since the last release. Anyway, I’ll take this from my list. Sorry for having bothered you. > [@resmo](#): > > I have a strong feeling that this “cleanup” of working and used collections will only lead to Ansible losing relevance. > > “You can install collections manually”: → Yes, you can, but AFAIK there is no (for years) integrated update mechanism to update collections and roles. So you have to manually check for updates via more and more roles and collections… do we really think this is the way to go? If you see a problem there, maybe you should start a topic here on the forum to discuss this. ---
**Author:** ![flowerysong](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/flowerysong/32/2305_2.png) [@flowerysong](https://forum.ansible.com/u/flowerysong)\ **Post date:** [June 29, 2024, 3:11pm UTC](https://forum.ansible.com/t/unmaintained-collection-ngine-io-cloudstack/6840/7 "2024-06-29T15:11:55Z")
There are some violations of the [inclusion criteria](https://docs.ansible.com/ansible/latest/community/collection_contributors/collection_requirements.html#ci-testing), but it should be pretty simple to address the issues. - “All CI tests MUST run regularly (nightly, or at least once per week)” - Tests have not run since May 28. This is due to GitHub automatically disabling scheduled workflows on inactive repositories. You can [re-enable them manually](https://docs.github.com/en/actions/using-workflows/disabling-and-enabling-a-workflow#enabling-a-workflow) when this happens. - “The results from the regular CI runs MUST be checked regularly.” - Integration tests have been failing for months. This is because of unsafe conditionals in some tests (for example [here](https://github.com/ngine-io/ansible-collection-cloudstack/blob/58075b9831c5cc879c8c5cf3fa357a06dd4d2d6b/tests/integration/targets/cs_portforward/tasks/main.yml#L92)) which are broken by the fix for CVE-2023-5764. This condition should instead be written as `pf.vm_name == cs_portforward_vm`, avoiding the double interpolation. - “You MUST run the `ansible-test sanity` command from the [latest stable ansible-base/ansible-core branch](https://github.com/ansible/ansible/branches/all?query=stable-).” - These tests currently run against `stable-2.14` and are passing for `devel`, you just need to update the CI config. While it’s not an inclusion requirement, it would also be nice if you updated the versions of the CloudStack test container you run tests against; the newest version of CloudStack that’s being tested with your current config is four years old. ---
**Author:** ![flowerysong](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/flowerysong/32/2305_2.png) [@flowerysong](https://forum.ansible.com/u/flowerysong)\ **Post date:** [August 7, 2024, 5:08pm UTC](https://forum.ansible.com/t/unmaintained-collection-ngine-io-cloudstack/6840/8 "2024-08-07T17:08:10Z")
@resmo @mariolenz These issues still have not been addressed. ---
**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:** [August 13, 2024, 12:22pm UTC](https://forum.ansible.com/t/unmaintained-collection-ngine-io-cloudstack/6840/9 "2024-08-13T12:22:45Z")
@resmo If you need any help, please let us know