tool/charts: versions overwriting each other #508
Assignees
Labels
Comments
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
|
I was just starting to look into how we might waterfall chart versions down dev, qa, prod, etc. without having to put the libs into separate git repos and vendoring the charts in there. I even tried adding a TLDR; we'd be really interested in this! |
julienduchesne
added a commit
that referenced
this issue
Jun 1, 2022
Closes #508 Whenever two charts will end up in the same dir, tanka will exit before doing anything Ex, these two versions would end up in the flagger dir: ```yaml directory: charts repositories: - name: flagger url: https://flagger.app requires: - chart: flagger/flagger version: 1.16.1 - chart: flagger/flagger version: 1.17.0 version: 1 ``` ```console $ tk tool charts vendor Error: Output directory conflicts found: - output directory "flagger" is used twice, by charts "flagger/[email protected]" and "flagger/[email protected]" ``` It checks in both `add` and `vendor` commands to handle the case where someone writes their YAML manually
julienduchesne
added a commit
that referenced
this issue
Jun 2, 2022
Closes #508 Whenever two charts will end up in the same dir, tanka will exit before doing anything Ex, these two versions would end up in the flagger dir: ```yaml directory: charts repositories: - name: flagger url: https://flagger.app requires: - chart: flagger/flagger version: 1.16.1 - chart: flagger/flagger version: 1.17.0 version: 1 ``` ```console $ tk tool charts vendor Error: Output directory conflicts found: - output directory "flagger" is used twice, by charts "flagger/[email protected]" and "flagger/[email protected]" ``` It checks in both `add` and `vendor` commands to handle the case where someone writes their YAML manually
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It is possible to
requirethe same chart at different versions. However, the entry that comes last in therequireslist effectively overwrites the others duringhelm pull.Proposed solution would be a
outputornamekey inRequirementto specify where the downloaded chart shall go. Also Tanka should catch this case duringchart addand request you to specify the above new field.The text was updated successfully, but these errors were encountered: