Handle docker refs correctly in policy/docker 56/131356/1
authorliamfallon <liam.fallon@est.tech>
Mon, 3 Oct 2022 10:17:55 +0000 (11:17 +0100)
committerliamfallon <liam.fallon@est.tech>
Mon, 3 Oct 2022 10:20:29 +0000 (11:20 +0100)
commit91cae851fb32b3670a54a4ff9120e5690c85aed4
treed5dbdc1a723c536cbd42a4935b2bfe06e946ae1e
parentd31592eebbfbaca118c44f45af0cb3e935b90623
Handle docker refs correctly in policy/docker

The decker references in db-migrator need to be handled specially
because the reference in db-migrator must be set to the new Docker
reference that is to be released rather than the docker reference in the
pf_release_data.csv (which is correct in later phases). This is in
effect a forward reference to the "to-be-released_ docker base image.

Issue-ID: POLICY-4045
Change-Id: Iff3845d06894f7f4c927509fb2fb43f00af3b7ef
Signed-off-by: liamfallon <liam.fallon@est.tech>
integration/src/main/scripts/release/updateRefs.sh