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

helm push/pull support #2807

Open
carneirofc opened this issue Dec 27, 2024 · 0 comments
Open

helm push/pull support #2807

carneirofc opened this issue Dec 27, 2024 · 0 comments
Labels
feature request New feature or request

Comments

@carneirofc
Copy link

carneirofc commented Dec 27, 2024

Is your feature request related to a problem? Please describe.

Currently, the JFrog CLI does not support Helm chart uploads, which becomes a problem when you have a standardized way of building CI/CD pipelines and need to authenticate with Artifactory.

In my use case, for example, I simply cannot use Azure DevOps service connections. Instead, I have to deal with tokens and various workarounds. This becomes a significant issue when managing hundreds of pipelines across multiple projects and organizations.

This may seem simple if you focus solely on the Helm chart itself, but when you have hundreds of actions being performed, the sole reason for needing another authentication method on the platform is the lack of Helm chart support. This situation becomes cumbersome and difficult to maintain.

Describe the solution you'd like to see

Ideally, the JFrog CLI should support Helm chart uploads, especially when using OCI registries. Even if it’s just a wrapper around the tool that forwards the arguments and passes the corresponding token.

Describe alternatives you've considered

I could use the old Helm chart registry or simply handle the .tar.gz files, which would allow me to leverage the existing functionality of the JFrog CLI and JFrog Azure DevOps tasks, but this is not an ideal solution. Another option would be generating an access token, creating a secret for each Azure project, and loading it into the pipelines, but this introduces another point of failure and an additional component to track. While I could use a key vault, it adds yet another layer of complexity that was not needed before.

Additional context

None.

Related to: #2275

@carneirofc carneirofc added the feature request New feature or request label Dec 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant