Hey - I spent some time after getting stuck on issue #8 digging into the differences between the ChartMuseum API and the Harbor API. This PR adds an optional harbor_api value to the source, which plays nicer with Harbor. If the value isn't added, nothing changes, and the resource would still (I expect) work with ChartMuseum.
It's working nicely with my Harbor install, but I haven't validated it against ChartMuseum.
Wow. First of all: thanks for the PR.
I assume Harbor is the widely used on-premises Helm Chart Repo and therefore the value added is really appreciated!
Hey - I spent some time after getting stuck on issue #8 digging into the differences between the ChartMuseum API and the Harbor API. This PR adds an optional
harbor_api
value to the source, which plays nicer with Harbor. If the value isn't added, nothing changes, and the resource would still (I expect) work with ChartMuseum.It's working nicely with my Harbor install, but I haven't validated it against ChartMuseum.
Cheers! D