Closed xuchixc closed 2 months ago
Did some tests, this issue was involved in 10.0.3
[ibmmas/cli:10.0.3]mascli$ which yq /opt/app-root/bin/yq
[ibmmas/cli:10.0.2]mascli$ which yq /usr/bin/yq
@whitfiea It looks like the version of yq being installed via pypi in https://github.com/ibm-mas/cli-base/pull/8 is conflicting with the version of yq installed already via
It is different implementations of yq rather than just different versions. The version installed via pip is this one https://pypi.org/project/yq/ which is the kislyuk
implementation. The yq installed via https://github.com/ibm-mas/cli-base/blob/b293e16a6adf22ee868c69391da7388e048ba9c1/image/cli-base/install/install-yq.sh is the mikefarah
version.
The conflict is that we have code now in the cli that assumes that yq
is the mikefarah version, and code in the gitops
branch that assumes that yq
is the kislyuk version.
We should standardise on the mikefarah version and actually have an issue on the backlog to do that https://jsw.ibm.com/browse/MASCORE-2119
PR to resolve this is here https://github.com/ibm-mas/cli-base/pull/9
In the laest version of MAS CLi container image, the
yq
version is not correct. I found there are twoyq
commands, the correct version ofyq
should bev4.35.1
which is located at/usr/bin/yq
. The current foundyq
version is3.2.2
which is located at/opt/app-root/bin/yq
We need to keep the latest yq versionv4.35.1
, otherwise some existing codes which dependent on yqv4.x
will be failed.