crenshaw-dev
commented
1 week ago One possibility to consider is hosting registry-scanner in the image updater repo, but using go workspaces to keep the modules separate and clean. That'll avoid the release overhead that we face with other library repos like argo-ui, pkg, and gitops-engine.
jannfis
[x] Do you wish to host your project repository on https://github.com/argoproj-labs or https://github.com/argoproj ? on https://github.com/argoproj-labs/registry-scanner
[x] Does your project focus on enhancing or providing additional features to one of the existing core projects ? If yes, which of the core projects is your proposed project related to?
Yes, the project would be a integrated with Image Updater repository.
Image Updater provides some functionality that can be reused by other projects, most notably the feature to inspect OCI and Docker registries' contents and pick an image based on some constraints. However, Image Updater is tightly coupled with Argo CD right now and requires consumers to pull in Argo CD as a dependency.
There have been some discussions within the community to decouple this functionality from the parts of the code that interact with Argo CD, i.e. need the Argo CD as requirement. If we can decouple the functionality as a library, without the need for Argo CD as a dependency, we are more likely to attract more consumers for this library and thereby, potentially gaining more contributors. This will likely increase code quality, feature completeness and project popularity.
The new repository is intended to hold this decoupled library for repository scanning and image inspection functionality.
[x] Is it endorsed by any of the Argo subproject maintainers? Please mention sponsors from the subproject. @jannfis, @chengfang, @ishitasequeira
[x] Who will maintain the project going forward? @ishitasequeira, @chengfang and other RedHat developers