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
0222 16:19:31.882577 101820 index.go:164] unable to load "kube-prometheus-stack-32.2.1" chart: invalid "grafana-6.21.5" chart dependency: getting grafana-6.21.5 from index file: no chart name found
With the same error for each version it tries to pull. This also happens with other charts with subcharts stored in different registries.
The text was updated successfully, but these errors were encountered:
I am glad you discovered this bug. Sadly, we don't plan to add support for multiple source chart repositories at the moment.
However, we will be happy to review and discuss any possible implementation you can send as PR.
When trying to sync a chart with subcharts in a different remote registry, the sync fails with
no chart name found
.For example, trying to sync kube-prometheus-stack, it fails copying grafana, which is stored in a separate repo.
Example config:
When running
charts-syncer sync
, I get this:0222 16:19:31.882577 101820 index.go:164] unable to load "kube-prometheus-stack-32.2.1" chart: invalid "grafana-6.21.5" chart dependency: getting grafana-6.21.5 from index file: no chart name found
With the same error for each version it tries to pull. This also happens with other charts with subcharts stored in different registries.
The text was updated successfully, but these errors were encountered: