-
Spike
-
Resolution: Done
-
Undefined
-
None
-
None
-
None
-
8
-
False
-
None
-
False
-
SECFLOWOTL-124 - Image Updater: Decouple registry and image inspection functionality from updating functionality
-
-
-
GitOps Tangerine - Sprint 3264
Story / Background
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.
The initial plan was to create a new repository that will host the new registry-scanner library. When we raised a request in argoproj community for creating a new repository, one good suggestion was made by Michael of using go workspaces and keeping the code as part of image updater itself instead of creating a new repository. https://github.com/argoproj-labs/community/issues/14#issuecomment-2388957314
As part of this SPIKE, we would want to explore the option of go workspaces and see if we can create a separate image for registry-scanner library from the image-updater repository itself.
Acceptance Criteria
- Come up with a document that would describe the effort and challenges we would face for using the go workspaces approach
- Highlight the pros and cons for the approaches of go workspace vs new repository