Bug 2065726

Summary:	assisted-service repo pin-latest.py script should allow custom tags to be pinned
Product:	Red Hat Advanced Cluster Management for Kubernetes	Reporter:	OpenShift BugZilla Robot <openshift-bugzilla-robot>
Component:	Infrastructure Operator	Assignee:	Omer Tuchfeld <otuchfel>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	low	Docs Contact:	Derek <dcadzow>
Priority:	medium
Version:	rhacm-2.6	CC:	ccrum, mfilanov, trwest, yfirst
Target Milestone:	---
Target Release:	rhacm-2.5
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	2072892 (view as bug list)		Environment:
Last Closed:	2022-10-03 20:21:49 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	2065661
Bug Blocks:	2072892

Description OpenShift BugZilla Robot 2022-03-18 15:05:44 UTC

+++ This bug was initially created as a clone of Bug #2065661 +++

Description of the problem:
When publishing the Infrastructure Operator bundle and catalog to quay for the master branch, we scan the operator's manifests (clusterserviceversion in particular) for the "latest" tag and pin it to a particular image manifest digest. This is done using the pin-latest.py script and the choice of "latest" tag is hardcoded in that script. 

We would like to use the same script for doing similar pinning but for our release branches. In those release branches, the CSV manifest doesn't have :latest tags, it has, for example, ocm-2.5 tags. 

The script should be modified to accept, through an environment variable, a different tag that needs to be pinned, so it can be used in release branch catalog/bundle quay publishing CI jobs.