-
Notifications
You must be signed in to change notification settings - Fork 69
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Question about Helm version used in unit tests #156
Comments
Hello @lsolovey, The intent of the different versions, was more related to the helm version itself, not the engine within the unittest plugin. Some companies are using a specific cliënt version, and the different versions would give the option to use the preferred cliënt version. With the version 0.3.0 available in the original helm-unittest/helm-unittest, the images only contain the latest version, aligned with the helm unittest engine. Greetings, |
Hi @quintush,
first of all - thank you so much for maintaining this great plugin!
I have a question about actual version of the Helm engine used while running unit tests. You publish multiple Docker images for the same version of
helm-unittest
, e.g. the latest version0.2.8
has images: https://hub.docker.com/r/quintush/helm-unittest/tags?page=1&name=0.2.8As far as I understand - the intent is to allow running unit tests using different versions of Helm engine? However it seems that actual version of Helm engine is statically set in https://github.com/quintush/helm-unittest/blob/master/go.mod#L26
E.g. for the latest tag 0.2.8 - Helm version is set statically to 3.7.1. Then what these different tags mean:
3.7.0-0.2.8
,3.6.3-0.2.8
, etc. ?When I run tests as follows I expected that it would use Helm version
3.5.4
but it's still using3.7
:docker run -ti --rm -v %cd%/mychart:/apps quintush/helm-unittest:3.5.4-0.2.8 --helm3 -o test-output.xml --output-type JUnit /apps
I used the following Helm template to verify the version of Helm engine in use:
The text was updated successfully, but these errors were encountered: