CP4BA Version Control

[Knickkennedy]

Describe the bug
It seems impossible to override the CP4BA version, but every other cloud pak deployer (cp4d, cp4i, etc.) has a version that can be overwritten. I see appVersion: "{{ cp4ba_version }}" as a field, so I know theoretically I can pass -e to the ansible playbook, or to the cpd entrypoint.sh, but I want to do so declaratively, like the other components.

I am unsure if this would be a bug, or a feature request, or if it simply already exists but I don't see it.

[fketelaars]

@Knickkennedy For CP4BA, the installed release is dependent on the release of deployer. You can find a list of releases here: https://github.com/IBM/cloud-pak-deployer/releases. Search for CP4BA to obtain the release that supports a specific version of CP4BA. For example, v3.2.4 installs CP4BA 25.0.0 IF001.

If you're running this from OpenShift, you can pull image quay.io/cloud-pak-deployer/cloud-pak-deployer:v3.2.4.

[Knickkennedy]

Would it be possible to get that added to the documentation on github pages so it's easier to find that information? I could not find any information related to CP4BA and releases or versions, unfortunately. Also, as always Frank, thanks for your awesome and fast replies!

[fketelaars]

Yes, we should absolutely do that.