-
Bug
-
Resolution: Unresolved
-
Major
-
CNV v4.15.z, CNV v4.14.z
-
Quality / Stability / Reliability
-
0.42
-
False
-
-
False
-
None
-
-
CNV I/U Operators Sprint 274, CNV I/U Operators Sprint 275, CNV I/U Operators Sprint 276
-
Critical
-
Customer Reported
-
None
Description of problem:
Revised description: Provide customers the ability to get the source code repositories + commit hash for all images we ship in CNV, for any given version. Provide them a mechanism in which they can pass a CNV version that has been released to production, and it will generate a CSV file which contain the columns: - compVendorUrl (the upstream repo in github) - compName (the name of the image) - compVersion (image NVR) - repoCommitId (the commit hash) - compDownloadUrl (a URL from github of the tarball containing the code of the commit. note: this can be constructed based on columns A and D) In order to do so, we need to put the upstream repo url label in every image we build, and also fill the upstream-vcs-ref label (the commit hash) for images that currently don't have it. Then use a simple script that extracts the images list from the redhat-operators catalog and put the information in a CSV file. --- Original description Create Git repositories and have them tagged for every release we build downstream. When sending the operator source code to security scan it should have tag based so that download url can be shared to the security scan
Version-Release number of selected component (if applicable):
4.x
How reproducible:
NA
Steps to Reproduce:
1. 2. 3.
Actual results:
No Tags available for the source code
Expected results:
There should be tagged available for the source code
Additional info:
- is related to
-
ACM-22733 ACM Allignment: Expose upstream repository and commit hash for customers for every component for every future CNV version
-
- New
-