Skip to content
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

Issue with Using vals for Credentials in Helmfile #511

Open
sule26 opened this issue Sep 4, 2024 · 0 comments
Open

Issue with Using vals for Credentials in Helmfile #511

sule26 opened this issue Sep 4, 2024 · 0 comments

Comments

@sule26
Copy link

sule26 commented Sep 4, 2024

I'm trying to access a Helm chart from a private repository within my company, and I've followed the Helmfile documentation for passing credentials. However, I encountered an issue where I could only retrieve the Helm chart when the username and password were specified as plain text.

Since vals is a project associated with Helmfile, it seems logical to integrate vals directly within Helmfile for handling sensitive information. Here's how I've attempted to configure it:

repositories:
  - name: bdc-helm
    url: https://private-chart
    username: ref+awssecrets://test?region=us-east-1#/username
    password: ref+awssecrets://test?region=us-east-1#/password
    passCredentials: true
...

In this configuration, I'm using ref+awssecrets to reference credentials from AWS Secrets Manager. However, it appears that this approach does not work as expected for authenticating with the private repository.

Is there a recommended way to use vals with Helmfile for securely passing credentials, or am I missing something in the configuration? Any guidance or suggestions would be appreciated.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant