Unmaintained collection: Removal from Ansible (community) package

[mariolenz]

It looks like this collection is effectively unmaintained. According to the current community guidelines for collections, we will consider removing it in a future version of the Ansible community package. Please see Unmaintained collection: netapp.storagegrid for more information.

At least one month after this announcement appears here and on Bullhorn, the Ansible Community Steering Committee will vote on whether this collection is considered unmaintained and will be removed, or whether it will be kept. If it will be removed, this will happen earliest in Ansible 11. Please note that people can still manually install the collection with ansible-galaxy collection install netapp.storagegrid even when it has been removed from Ansible.

[vardhanv]

Hello, this collection is being tracked and used. There are issues that we are looking to fix. Request that this collection not be removed in a future community package.

[mariolenz]

@vardhanv Well, in that case the main problems I see are the failing CI and that it hasn't run at all for over a year. And that you're not testing with 2.14 to 2.16:

netapp.storagegrid/.github/workflows/main.yml

Lines 10 to 22 in 7c09668

	sanity:
	name: Sanity (${{ matrix.ansible }} on storagegrid
	runs-on: ubuntu-latest
	strategy:
	fail-fast: false
	matrix:
	ansible:
	- stable-2.9
	- stable-2.10
	- stable-2.11
	- stable-2.12
	- stable-2.13
	- devel

However, this is a requirement:

You MUST run CI against each of the “major versions” (2.10, 2.11, 2.12, etc) of ansible-base/ansible-core that the collection supports.

BTW you might consider dropping support for older / EOL versions of ansible-core (< 2.14). This is up to you, but I think a lot of collections already did this. Of course dropping support for ansible-core versions is considered a breaking change, so would require a new major release of your collection.

[joshedmonds]

@mariolenz These items have now been addressed in the latest release.
Tests with 2.14 and 2.15 are passing. runtime.yml specifies >=2.14

[mariolenz]

@mariolenz These items have now been addressed in the latest release. Tests with 2.14 and 2.15 are passing. runtime.yml specifies >=2.14

Your CI still fails for 2.16. Although this might not be a problem of your code but of the CI.

The CI also seems to fail for 2.10 to 2.13... but since you've dropped support for those versions, I wonder why you are still testing with them.

BTW it might be a good idea to join the discussion in the forum.