I am opening this ticket to start the removal process for cyberark.pas. There have been multiple issues with collection requirements violations (see the list in cyberark.pas 1.0.40 is not tagged in git · Issue #90 · cyberark/ansible-security-automation-collection · GitHub and [Tracker] Serious collection requirements violations that require version pinning · Issue #223 · ansible-community/ansible-build-data · GitHub), and there was no response to the latest issue report that was filed during ~a month ago during the release process for the last Ansible release. If there are no objections, I will start voting for the collection removal in one week.
Related topics
| Topic | Replies | Views | Activity | |
|---|---|---|---|---|
| Collection removal: cyberark.conjur | 1 | 115 | September 18, 2024 | |
| [Vote ended 2024-09-27] Collection removal: sensu.sensu_go | 3 | 177 | October 21, 2024 | |
| Remove ibm.qradar from the Ansible Community Package | 7 | 136 | August 13, 2025 | |
| [Vote ended on 2025-06-13] Collection requirements: declare that Galaxy artifacts must not be deleted once they appear in Ansible releases | 12 | 233 | June 13, 2025 | |
| Add additional steps for removing a collection | 3 | 454 | July 3, 2024 |