Collection Requirements Violation - Repository Management

[gotmax23]

Hi! The Ansible Community Steering Committee has determined that this collection does not tag its releases in its git repository. This violates the repository management section of the Collection Requirements:

Every collection MUST have a public git repository. Releases of the collection MUST be tagged in said repository. This means that releases MUST be git taged and that the tag name MUST exactly match the Galaxy version number. Tag names MAY have a v prefix, but a collection's tag names MUST have a consistent format from release to release.

Additionally, collection artifacts released to Galaxy MUST be built from the sources that are tagged in the collection's git repository as that release. Any changes made during the build process MUST be clearly documented so the collection artifact can be reproduced.

Note that this requirement has recently been clarified, but its intent remains the same. Please tag at least the previous 1-2 releases of your collection to come into compliance.

Please keep us updated and let us know if you have any questions. Thanks!

[gotmax23]

Has there been any progress here? This collection remains in violation of the Collection Requirements.

[felixfontein]

@cyberark-bizdev can you please take a look?

[gotmax23]

I have opened ansible-community/community-topics#168 about removing this collection from the Ansible community package due to this unresolved Collection Requirements violation.

[ssbarnea]

I find it a little bit hilarious that the only collection that I know about as not doing the tagging is a security related one.

[jtuttle]

Hi there, I'm the manager of the CyberArk Community & Integrations team at CyberArk. We are responsible for most of the OSS repositories but unfortunately this one doesn't fall under our umbrella. This lapse has just been brought to my attention. I will try to get the appropriate person / team working on it ASAP. Sorry for the delay.

[jtuttle]

Update: I reached out to the person that manages @cyberark-bizdev directly and he said he will try to address it in the next few days, which I reckon will be next week sometime since it's Friday. I'll be on vacation next week but will try to hop on at some point to make sure this has been resolved.

[infamousjoeg]

This was fixed 5 days ago in release 1.0.14.