fix: correctly check for chart directory conflict #30868
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hello,
This PR fix an inconsistency when checking for a directory conflict while expanding a chart. Before we would check for a directory name composed of the chart name and the chart version. This would create a superfluous directory while also not really checking for a conflict because the chart will be expanded in a directory whose name would only be the chart name.
Example:
We end up with a mix of the
8.7.11
and8.7.12
charts.Since we compute the final
chartDir
path from thechartName
found in theChart.yaml
file in theExpand
function, I think the directory conflict check is more reliable if implemented there.Best Regards.