Skip to content

Add helm registry login command #487

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

Open
franpog859 opened this issue Jan 21, 2025 · 3 comments
Open

Add helm registry login command #487

franpog859 opened this issue Jan 21, 2025 · 3 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@franpog859
Copy link

What do you want to see?

I'd benefit from being able to log into a private registry so I can install private charts in my e2e test.

I created the command myself but it'd be much cleaner if done the same way as the rest of the helm commands.

registryLoginCommand := fmt.Sprintf("helm registry login %s -u %s -p %s", cfg.RegistryServer, cfg.RegistryUsername, cfg.RegistryPassword)
proc := exec.NewProcWithVars(registryLoginCommand, vars.New().Vars(""))

var stderr bytes.Buffer
proc.SetStderr(&stderr)

_ = proc.Run().Result()
if !proc.IsSuccess() {
  return ctx, fmt.Errorf("%s: %w", strings.TrimSuffix(stderr.String(), "\n"), proc.Err())
}

Extra Labels

No response

@franpog859 franpog859 added the kind/feature Categorizes issue or PR as related to a new feature. label Jan 21, 2025
@cpanato
Copy link
Member

cpanato commented Jan 21, 2025

@franpog859 thanks for the issue
are you willing to contribute this feature?

@franpog859
Copy link
Author

I could check it out in some free time ^^ I guess it's nothing critical, @cpanato

@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 22, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

No branches or pull requests

4 participants