Visitar URL original
Support for invoking a password-supplying command · Issue #32836 · helm/helm · GitHub
Skip to content

Support for invoking a password-supplying command #32836

Open

Description

@fbauzac

What would you like to be added?

Hello,

FYI, Helm stores my personal password in clear in the
file ~/.config/helm/repositories.yaml

This is a known Helm issue since 2018 and it has never been really
solved: #4723

At the moment, the secure way is not user-friendly: invoke helm with
the --password-stdin commandline option, and piping the secret in.

(Putting a secret as a commandline parameter is not secure, as it
would be visible by anyone else on the system with e.g. "ps -ef")

I would certainly prefer a configfile setting where we can specify a
command helm could run and get its stdout. This would be both easy to
implement and generically usable with whatever password store is in
use. In the repositories.yaml file, it could be something like:

password_command: "pass show the_password"

Could you please consider implementing such a feature?

Thanks a lot!

Best regards
Fabrice

Why is this needed?

End users should not have to choose between security and convenience. The helm commandline should remain simple, and no password should be stored in clear.

Activity

  1. irajatpandey commented on Nov 7, 2026

    @irajatpandey

    Hi @fbauzac,

    I have submitted PR #32861 implementing support for password_command:

    • CLI Flag: Adds --password-command to helm repo add, enforcing mutual exclusivity with --password and --password-stdin.
    • Dynamic Password Resolution: When communicating with the chart repository (index downloads and chart fetching), Helm invokes the configured command on demand via the system shell (sh -c on Unix, cmd.exe /c on Windows), trims trailing newlines, and bounds execution with a 30s timeout.
    • Security: The resolved secret is never stored on disk; repositories.yaml preserves password_command while leaving the password field empty.
    • Backward Compatibility: Fully preserved — static passwords in repositories.yaml or via --password continue to work with zero overhead.

    Feel free to take a look and share any feedback!

  2. irajatpandey commented on Nov 10, 2026

    @irajatpandey

    /assign

  3. irajatpandey commented on Nov 10, 2026

    @irajatpandey

    Gentle ping to maintainers (@TerryHowe, @gjenkins8, @joejulian, @marckhouzam, @mattfarina):

    PR #32861 is open and ready for review to resolve this issue. All CI checks and DCO validations have passed, unit tests are included, and full backwards compatibility is preserved.

    Whenever you have a moment, could someone please take a look? Thank you!

  4. irajatpandey commented on Nov 11, 2026

    @irajatpandey

    /assign

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions