The function "get_latest_tag_from_api" will only pull, for example, the latest packages for 3.11. There are times that one environment is deployed and the current version is 3.11.69 (and that environment has its own disconnected-docker-registry), and a new environment is deployed in the future. Sometimes, new '.z' versions are released into Red Hat's container library and is newer than 3.11.69 (for example 3.11.92). It would be beneficial to be able to set a variable, via command line, to specify the full version that you'd like to download.
Perhaps both 'latest' AND the x.y.z release can both be downloaded, asynchronously, first latest, and then x.y.z.
Perhaps via this method:
Duplicate the function "get_latest_tag_from_api", and make modifications in the new function to be able to pull x.y.z (perhaps "get_my_tag_from_api"). x.y.z is defined via command line attribute, if blank/not defined, then only pull latest and do not execute the function to pull x.y.z
garethahealy
commented
4 years ago
The function "get_latest_tag_from_api" will only pull, for example, the latest packages for 3.11. There are times that one environment is deployed and the current version is 3.11.69 (and that environment has its own disconnected-docker-registry), and a new environment is deployed in the future. Sometimes, new '.z' versions are released into Red Hat's container library and is newer than 3.11.69 (for example 3.11.92). It would be beneficial to be able to set a variable, via command line, to specify the full version that you'd like to download.
Perhaps both 'latest' AND the x.y.z release can both be downloaded, asynchronously, first latest, and then x.y.z.
Perhaps via this method: