-
Notifications
You must be signed in to change notification settings - Fork 64
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adding Basic Auth to access Helm repo #41
Comments
Your changes sound sensible. Overall I would prefer the code to use the helm libraries, but I understand if that is more effort than your time would allow. |
Sorry, I am a bit lost! by using the helm libraries, you mean? |
yes vs using a raw http.NewRequest. |
sorry, I wasn't clear in my previous question. I don't understand why using the Helm libraries to perform a GET call to the Chart Museum to get back the index.yaml. I normally use the Helm libraries to interact with k8s. |
The helm libraries natively understand index management and authentication to those indexes along with supporting non-http indexes such as s3 index via plugins. You would get all of these features built-in. |
ok, I'll have a look! Thanks |
@DomenicoS-sdet do you have any WIP for this issue, I'd like to pick up and fix it, since we are using private helm repo here as well? |
Hi, no I don't have anything. We adapted for our needs, but wasn't touched since then.🙂 |
Hi everyone. Is someone currently working on this? |
@PPACI no one is actively working on adding this feature. |
Hi,
Great idea the override, however it returns a 401 Unauthorised if the repo has authentication implemented (like mine). I cloned the code and added a basic Authentication to the Get request to download the index.yaml file from the override, and now I am able to get the file.
Below an example of the config.yaml file, where for each Helm repo it is possible to specify its own authentication as Env variables. These can then be passed as k8s secret, or CI env variable at deploy.
Then the code for the new request is quite easy
If it sounds sensible I can open a PR with all the changes to introduce the authentication
The text was updated successfully, but these errors were encountered: