Remove ibm.qradar from the Ansible Community Package

Project Discussions
,
1

The ibm.qradar collection is deprecated. It’s not said in the announcement, but the README now states that compatibility with ansible-core>2.17 is not guaranteed.

So I think we should remove it from the Ansible Community Package ASAP. Maybe schedule the removal for Ansible 13?

edit: Removing a collection that has been explicitly deprecated or abandoned by its (former) maintainers

edit2: This has also been announced in the latest Bullhorn issue (#197).

2

I think we should remove it from Ansible 13. (While they officially don’t support the ansible-core versions used by Ansible 11 and 12, 11 is already out, and we should avoid breaking changes to 12 IMO.)

3

I agree, but when should we announce that we’ll remove it? Looking at the problems we have with releasing 12.0.0, and that the process demands we vote on this… should we announce the removal in Ansible 12.1.0 or try to get it into 12.0.0? I tend to wait until 12.1.0.

What do you think?

4

I’d start the process soon, and then announce it whenever a new major or minor release is happening, so either 12.0.0 if the decision is early enough (and we aren’t in release candidate land), or 12.1.0 elsewise. And in Ansible 11 we can simply announce it in the next minor release.

5

Regarding timing and which release it gets removed from, I’m happy with whatever you decide.

Is that something we want to start a new thread on to see how we can improve the situation.

6

I’ve read the section again, and I think I was wrong. Removing a collection that has been explicitly deprecated or abandoned by its (former) maintainers doesn’t require a vote.

So I’ve created a draft PR to announce the removal from Ansible 13.

If this looks OK and is merged, I would also announce this in Bullhorn.

7

Makes perfect sense. Thanks for checking that.
I’m +1 to removing