I would agree that there’s not really a good way out the situation. But just to get this clear: I want to remove purestorage.flasharray and purestorage.flashblade from the Ansible Community Package. I think this is important: They’re dead, there won’t be any fixes anymore. Especially not for incompatibilities with future ansible-core releases.
Creating new repos for the old collections would be a possible solution. But I’m not sure if this is really feasible.
How about adding everpure.flasharray and everpure.flashblade to ACP 15, and also purestorage.flasharray 1.45.0 and purestorage.flashblade 1.28.0? This way, we would have the redirects and the new collections they’re pointing to. This would somehow be against stop including new collections in the Ansible community package. But we could argue that the everpure collections aren’t new, just successors to already existing ones. And while it’s not great that the redirects and renaming has been done in a minor release, at least we won’t have this in a minor ACP release but in the next major release.
I didn’t have closer look at the new collections recently, so I can’t say if there are any issues that might prevent us from adding them to the ACP. Just thinking loud loud about what to do to get out of this situation.