Hello,
In a context of a security project, we would like to have view access control at Collection level to ensure content confidentiality.
Our team may implement this support for our own usage, but we would like to contribute it.
Do you think it may be a feature worth (and not too complex) to implement for the context of on-premise private deployment?
Thank you in advance
Yves
Hello Yves,
That sounds like an interesting idea. I’ll share this with the team in our next backlog refinement meeting (usually Tuesday mornings eastern time US) and report back.
Thanks!
Brian
As a comparison, such security segregation may be implemented with alternative products - For example with JFrog Artifactory, it would require to create a specific repository (with expected permissions) for each Ansible Collection; but with following drawbacks: management overhead and lack of comfortable web interface to discover/review collections.