Closed sugat009 closed 15 hours ago
The issue is that we don't properly check the user input on the prompt for which version you want to run. The request is for a number, not a version string. So for example, if you want to run version 4.6.0
, you should enter 57
:
Which version to you want to run? (ctrl + c to quit)
53) 4.4.2 145) add-funding-json-doc
54) 4.5.0 146) all-view-updates
55) 4.5.1 147) apdex-automation-tests
56) 4.5.2 148) bump-up-version
57) 4.6.0 149) bump-version-4-11
58) 4.6.0-alpha.1 150) check-ci-status
59) 4.7.1 151) cht-deploy-publish
#? 4.6.0
I just tested and confirmed I can install a version of 4.6.0
by entering 57
when prompted. FYI - these numbers change as more versions are added and old branches are removed.
A good fix would be to have the bash script not allow the user to proceed until they enter a valid choice. Right now we're failing open and choosing latest instead of showing an error when they enter a string.
ooof, thanks @mrjones-plip . I was able to run 4.6.0 using the version indexes on the left. Additionally, let's change the prompt message a bit to something like:
Which version do you want to run? (Please enter the index number from the list on the left, not the actual value)
Describe the bug I am unable to create a docked helper instance with an older version of CHT. The latest version of CHT at the time of reporting this bug is 4.15.0 which is the only version that gets chosen to be created even though I specify the exact version of CHT.
To Reproduce Steps to reproduce the behavior:
cht-docker-helper.sh
instance using:n
docker ps
or through the web UI in theupgrades
section from the panel.Expected behavior I should be able to create docker helper instances with older CHT versions.
Logs
Screenshots
Environment
Additional context