Loading images with sha instead of tag value in AAKE

Products

• CA Automic Workload Automation - Automation Engine

Issue/Introduction

It is a standard practice to use sha values on externally created images in Google cloud but AAKE only accepts tag values

 

Environment

Release : AAKE 21.x

Resolution

According to Google/GCR both ways (tagging and hashing) seem to be standard - https://cloud.google.com/container-registry/docs/overview#versions_of_images_within_a_registry
At the moment, we harvest the tagging way only since in our HELM chart's values yaml file we 

• point to the general GCR location where all the different (AWI, REST, JCP, CP, WP,...) images are stored
• and additionally state the target version (tag) that applies to all these different needed images

If we went for the hash/digest instead of the tag, we would need to list and/or input somewhere all the different hashes/digests for all the different images.

We are already using one of the two standard ways, but our way is easier to handle and additionally human readable (single product version as tag instead of multiple "human-unreadable" hashes).