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

Make retryingRoundTripper type public #13052

Open
Valgueiro opened this issue May 21, 2024 · 3 comments
Open

Make retryingRoundTripper type public #13052

Valgueiro opened this issue May 21, 2024 · 3 comments
Labels

Comments

@Valgueiro
Copy link

Valgueiro commented May 21, 2024

Hello team,

My team encountered an issue in Fluxcd (fluxcd/flux2#4804) that seems to be related to an issue that was already solved here (#11426). When trying to replicate the solution there, I saw on the code that the retryingRoundTripper is private to the helm cli package (https://github.com/helm/helm/blob/main/pkg/cli/roundtripper.go#L27).

Can we make it public? Do you guys see any issues on doing this?

@jnummelin
Copy link

plus one on this one

We also use Helm as library in our project and having to "inline" the retryingRoundTripper would be unwanted.

@gjenkins8
Copy link
Contributor

Thinking out aloud -- would it make more sense to expose a public helper in https://github.com/kubernetes/cli-runtime ?

Agree, that if this code might provide utility across multiple projects, then it could be made public. But I think that the Helm repo is probably not the best place to expose generic Kubernetes code from. Thoughts?

@jnummelin
Copy link

In our case we use helm functionality as a library. That means we have to construct the actions client separately and thus we cannot easily use the roundtripper as it's private. We did find a workaround to get it but it's not really pretty. I'd rather have used it directly. https://github.com/k0sproject/k0s/pull/4515/files

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

No branches or pull requests

3 participants