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.

*<--- Cut-n-Paste the entire contents of this description into your new
Epic --->*

Epic Goal

...

Why is this important?

...

Scenarios

...

Acceptance Criteria

...

Dependencies (internal and external)

1. ...

Previous Work (Optional):

1. ...

Open questions:

1. …

Done Checklist

• CI - CI is running, tests are automated and merged.
• Release Enablement <link to Feature Enablement Presentation>
• DEV - Upstream code and tests merged: <link to meaningful PR or GitHub
  Issue>
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub
  Issue>
• DEV - Downstream build attached to advisory: <link to errata>
• QE - Test plans in Polarion: <link or reference to Polarion>
• QE - Automated tests merged: <link or reference to automated tests>
• DOC - Doc issue opened with a completed template. Separate doc issue
  opened for any deprecation, removal, or any current known
  issue/troubleshooting removal from the doc, if applicable.
• Considerations were made for Extended Update Support (EUS)