Open hairmare opened 3 years ago
I would go with not event trying to install library charts. Since it's not possible just skip them.
For anyone looking for a workaround: Create separate config file for install only which excludes library charts.
We have a library chart among other charts, it's quite surprising to see that libraries chart are not supported.
Before discovering this issue, I had also to create an empty values.yaml
otherwise was even failing earlier.
Will try to use a separated config for ct install
but looks really clunky.
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.
bad bot. Still needed.
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.
most likely ct should just skip library charts during ct install
, but it should lint them during ct lint
. I can do this now using two different configs, but keeping those up to date feels error prone and a lot of manual work.
would a change that just makes ct install
skip library charts be a welcome change?
@hairmare I'd say that makes sense. Just skip them and print a warning.
+1 with tests :)
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.
bad bot. Still needed.
bad bot.
Still needed.
Are willing to work on this and open a pr?
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.
Are willing to work on this and open a pr?
No, sorry, no time to spare.
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.
bad bot
@cpanato Could you set an exempt-issue-labels for these kind of issues?
sounds good @lukasz-mitka
Is this a request for help?:
Probably
Is this a BUG REPORT or FEATURE REQUEST? (choose one):
This is a FEATURE REQUEST. I would like to be able to test library charts to some degree using the chart-testing automation.
This will help with maintaining library charts since it could make it easier to change them if they are properly tested.
Version of Helm and Kubernetes:
"latest"
What happened:
I created a library chart on a repo with the chart-testing GitHub Action enabled.
What you expected to happen:
That chart-testing does some sort or more or less meaningful tests on my library chart.
How to reproduce it (as minimally and precisely as possible):
Run the install tests of chart-testing against a
charts/
folder containing a library chart.Anything else we need to know:
I think there are a few reasonable ideas on how to tackle this but wanted to get some input:
ci/
folder and use that for testing