# Deprecated collection ngine\_io.exoscale

**URL:** <https://forum.ansible.com/t/deprecated-collection-ngine-io-exoscale/2572>\
**Category:** Project Discussions\
**Tags:** resolved, community-wg, collection-exclusion\
**Created:** [November 26, 2023, 3:22pm UTC](https://forum.ansible.com/t/deprecated-collection-ngine-io-exoscale/2572 "2023-11-26T15:22:49Z")\
**Posts on this page:** 10\
**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:** [November 26, 2023, 3:22pm UTC](https://forum.ansible.com/t/deprecated-collection-ngine-io-exoscale/2572/1 "2023-11-26T15:22:49Z")

</div>

It looks like `ngine_io.exoscale` [has been deprecated](https://github.com/ngine-io/ansible-collection-exoscale/commit/f442921cfc8a514c212ccdda1db20355870ef3c5) recently. As far as I understand, the API the collection uses won’t be available after May 1st, 2024.

@resmo is working on implementing a [collection based on the new API](https://github.com/ngine-io/ansible-collection-exoscale/issues/19). But since this would be a _new_ collection and the old API won’t be available after May 1st, 2024, `ngine_io.exoscale` would be useless after then.

So I suggest we consider removing it from Ansible 10. That is if my understanding is correct and the collection won’t be usable in Ansible 10 anymore. Although we might want to wait for the new collection being available so we can mention it in the deprecation announcement.

---

<div class="post-metadata">

**Author:** ![russoz](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/russoz/32/127_2.png) [@russoz](https://forum.ansible.com/u/russoz)\
**Post date:** [November 27, 2023, 1:22am UTC](https://forum.ansible.com/t/deprecated-collection-ngine-io-exoscale/2572/2 "2023-11-27T01:22:13Z")

</div>

Hi @mariolenz, given the upcoming change in the API, the deprecation will occur regardless of the new collection. I would arguewe should keep the two actions uncoupled.

---

<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:** [November 29, 2023, 6:53pm UTC](https://forum.ansible.com/t/deprecated-collection-ngine-io-exoscale/2572/3 "2023-11-29T18:53:09Z")

</div>

Considering that feature freeze will likely be at the end of May 2024 (it’s usually when ansible-core gets released, and that’s planned for 2024-05-20: [Ansible-core 2.17 — Ansible Documentation](https://docs.ansible.com/ansible/devel/roadmap/ROADMAP_2_17.html)), removing it from Ansible 10 makes sense since the collection will be no longer usable by then.

The new collection can be included before or after, whenever it is ready. It needs to pass the inclusion process, but I think this should not be too much of a problem since @resmo knows how to create collections 🙂

---

<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:** [September 29, 2024, 2:50pm UTC](https://forum.ansible.com/t/deprecated-collection-ngine-io-exoscale/2572/4 "2024-09-29T14:50:04Z")

</div>

I’m afraid I forgot about this issue, but I ran into it again now that I’ve started to look at [possibly unmaintained collections in Ansible 11](http://forum.ansible.com/t/9300).

I think we should remove the collection from the Ansible Community Package ASAP. Would it still be possible to remove it from 11?

---

<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:** [September 29, 2024, 6:01pm UTC](https://forum.ansible.com/t/deprecated-collection-ngine-io-exoscale/2572/5 "2024-09-29T18:01:58Z")

</div>

Since the collection apparently no longer works, I think it’s OK to remove it from Ansible 11.

---

<div class="post-metadata">

**Author:** ![russoz](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/russoz/32/127_2.png) [@russoz](https://forum.ansible.com/u/russoz)\
**Post date:** [September 29, 2024, 6:14pm UTC](https://forum.ansible.com/t/deprecated-collection-ngine-io-exoscale/2572/6 "2024-09-29T18:14:45Z")

</div>

I second that. Should we have vote to make it formal?

---

<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:** [September 30, 2024, 10:47am UTC](https://forum.ansible.com/t/deprecated-collection-ngine-io-exoscale/2572/7 "2024-09-30T10:47:24Z")

</div>

`ngine_io.exoscale` is officially deprecated and, according to the former maintainers, inoperable due to changes in the API. I therefor suggest to [remove the collection from Ansible 11](https://github.com/ansible-community/ansible-build-data/pull/462).

Please vote with Accept to deprecate and remove the collection from Ansible 11 or Reject to keep it.

_Poll ([view on site](https://forum.ansible.com/t/deprecated-collection-ngine-io-exoscale/2572/7))_

_Poll ([view on site](https://forum.ansible.com/t/deprecated-collection-ngine-io-exoscale/2572/7))_

---

<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:** [September 30, 2024, 2:58pm UTC](https://forum.ansible.com/t/deprecated-collection-ngine-io-exoscale/2572/8 "2024-09-30T14:58:52Z")

</div>

I don’t think it is necessary to vote on this. [Ansible Community Package Collections Removal Process — Ansible Community Documentation](https://docs.ansible.com/ansible/devel/community/collection_contributors/collection_package_removal.html#removing-a-collection-that-has-been-explicitly-deprecated-or-abandoned-by-its-former-maintainers) does not ask for a vote.

Since the deprecation already happened well during Ansible 10’s release cycle, I think we can simply remove it from Ansible 11.

---

<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:** [September 30, 2024, 4:20pm UTC](https://forum.ansible.com/t/deprecated-collection-ngine-io-exoscale/2572/9 "2024-09-30T16:20:44Z")

</div>

I’ve closed the poll. Feel free to approve and merge [Remove deprecated collection ngine\_io.exoscale](https://github.com/ansible-community/ansible-build-data/pull/462). Or just approve and I merge.

---

<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:** [September 30, 2024, 8:48pm UTC](https://forum.ansible.com/t/deprecated-collection-ngine-io-exoscale/2572/10 "2024-09-30T20:48:34Z")

</div>

(If anyone disagrees with not having a vote, please say so here.)
