Affects Version/s: 6.17.0, 6.19.1
Fix Version/s: 7.12.3
Metadata calculation is failing when YAML file contains Windows line endings (CR LF).
Helm chart kafka-router-1.0.2.tgz was not being indexed in index.yaml and causing below errors in Artifactory logs
Upon investigation, we determined that some of the files in kafka-router-1.0.2.tgz had Windows (CR LF) line endings instead of Unix (LF) line endings.
kafka-router-1.0.2.tgz has templates/configmap.yaml with Windows line endings (CR LF). whereas kafka-router-1.0.3.tgz has templates/configmap.yaml with Unix line endings (LF)
The same was true of other files such as values.yaml, templates/deployment.yaml and .helmignore (though Chart.yaml did have LF line endings).
In the Web UI tree browser, kafka-router-1.0.2.tgz appears correctly alongside other versions with Unix line endings such as chart kafka-router-1.0.1.tgz and chart kafka-router-1.0.3.tgz, however, when you look at the Chart Info it is blank. Indeed, when you look at the Chart Info for kafka-router-1.0.3.tgz and then move to chart kafka-router-1.0.2.tgz, the Chart Info for chart kafka-router-1.0.3.tgz is still displayed. Each time you attempt to load the Chart Info for chart kafka-router-1.0.2.tgz, the following Error 500 is generated and can be seen in the Chrome Developer Console:
1) Artifactory should support Windows line endings.
2) If Helm Chart information cannot be displayed, instead of a hidden Error 500 that won't be seen by users, could more information be provided? It feels wrong that Chart Info for another chart is still displayed when in actual fact an error has occurred.