Configuration-based installation of OpenShift and Cloud Pak for Data/Integration/Watson AIOps on various private and public cloud infrastructure providers. Deployment attempts to achieve the end-state defined in the configuration. If something fails along the way, you only need to restart the process to continue the deployment.
Is your feature request related to a problem? Please describe.
I manage a few pipelines that use the Cloud Pak Deployer for CP4D reservations on TechZone, and it would be beneficial to me if there was a specific version of the Cloud Pak Deployer that I could pull from when using it in a reservation. This would be a precautionary measure to safeguard the reservation from an erroneous update to either the Cloud Pak Deployer or any of its dependency images (cpd-cli, olm-utils-v2, ect) as right now always pulling from latest creates a potential single point of failure for all of my reservations.
Describe the solution you'd like
A way for me to pull a version locked Cloud Pak Deployer image that I can test before adding it to a reservation and know that it won't change after I've tested it.
Is your feature request related to a problem? Please describe. I manage a few pipelines that use the Cloud Pak Deployer for CP4D reservations on TechZone, and it would be beneficial to me if there was a specific version of the Cloud Pak Deployer that I could pull from when using it in a reservation. This would be a precautionary measure to safeguard the reservation from an erroneous update to either the Cloud Pak Deployer or any of its dependency images (cpd-cli, olm-utils-v2, ect) as right now always pulling from latest creates a potential single point of failure for all of my reservations.
Describe the solution you'd like A way for me to pull a version locked Cloud Pak Deployer image that I can test before adding it to a reservation and know that it won't change after I've tested it.