You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The helm doc tool should represent exact versions of dependencies in addition to the raw dependency string value present in Chart.yaml for clarity
Is your feature request related to a problem? Please describe and/or link to a bug issue.
N/A
Expected Behavior
Add in Chart.lock's metadata reading to retrieve an exact version packaged with a chart when present. It seems this could be roughly similar to the existing pkg/helm/chart_info.go file's parseChartRequirementsFile()
Once read, the requirements table could render into something like:
| Repository | Name | Version | Locked Version ||------------|------|---------|----------------||@stable| nginx-ingress |~0.22.1 | 0.22.6 |
Current Behavior
Currently, when helm docs reads a chart's metadata, it appears to do so only by reading Chart.yaml. It is capable of rendering a requirements section that looks like the following:
## Requirements| Repository | Name | Version ||------------|------|---------||@stable| nginx-ingress | 0.22.1 |
This is appropriate when exact versions are used in a helm chart's definition. However, helm supports version ranges, and locking a particular version by generating a lock file using helm dependency update. In those cases, we might see a version that looks like ~0.22.1 which represents a statement like 0.22.1 <= x < 0.23.0. Therefore, a dependency packaged with the chart could be a number of different versions.
Possible Solution
Add a parseChartLockFile function to ParseChartInformation
General Summary
The helm doc tool should represent exact versions of dependencies in addition to the raw dependency string value present in Chart.yaml for clarity
Is your feature request related to a problem? Please describe and/or link to a bug issue.
N/A
Expected Behavior
Add in Chart.lock's metadata reading to retrieve an exact version packaged with a chart when present. It seems this could be roughly similar to the existing
pkg/helm/chart_info.go
file'sparseChartRequirementsFile()
Once read, the requirements table could render into something like:
Current Behavior
Currently, when helm docs reads a chart's metadata, it appears to do so only by reading Chart.yaml. It is capable of rendering a requirements section that looks like the following:
This is appropriate when exact versions are used in a helm chart's definition. However, helm supports version ranges, and locking a particular version by generating a lock file using
helm dependency update
. In those cases, we might see a version that looks like~0.22.1
which represents a statement like0.22.1 <= x < 0.23.0
. Therefore, a dependency packaged with the chart could be a number of different versions.Possible Solution
Add a parseChartLockFile function to ParseChartInformation
Alternatives you've considered
It seems that the helm-docs tool does not read the Chart.lock file at all. I am not sure there is another alternative
Further Information
No response
The text was updated successfully, but these errors were encountered: