Is there no support for helm chart uploads using the jfrog CLI?

[bedge]

https://jfrog.com/help/r/jfrog-artifactory-documentation/deploy-helm-charts states:

Deploying Helm charts is done using cURL, Wget, JFrog CLI or any of the ways described in Deploying Artifacts.

However the page that references: Deploying Artifacts has no reference to using the jFrog CLI to upload helm charts.

The only reference I found was a closed problem ticket in this repo: #686 (comment)

suggesting

curl -f -k -s -u USERPASSWD ARTIFACTORY-URL -T path_to_chart_and_index

While I'm able up upload helm charts in this manner, there's no indication of how to provide the other metadata one generally uses the jFrog CLI for, eg: for a docker image I can specify additional metadata fields:

    jf docker push ${tag_url} --build-name=${BUILD;_NAME} --build-number=${REVISION} --module="${serviceName}" --project=${projectName} --detailed-summary=true

For helm charts, the fact that one must use curl, prevents any such metadata from being added.
Or, are these amended via headers?

Plus, the upload lacks a checksum so this error is left on the console:

Regardless, the lack of support for helm charts is notable and feels like a missing component in the CLI.

I'm running:

➜ jf --version
jf version 2.36.1

[bedge]

I found https://github.com/JFrog/helm - is this supposed to be the thing to use with artifactory?

Although, it appears to be an abandoned fork:
This branch is 6 commits ahead, 3511 commits behind helm:main.

[bedge]

The JFrog Artifactory HA cluster deployment in Kubernetes using Helm Charts:

Also shows only how do upload via curl, where one cannot specify any additional metadata, like jfrog properties, build-id, build-name, or, as mentioned above, provide a verified checksum.

[carneirofc]

Ideally, the JFrog CLI should support Helm 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.

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

It would be a significant improvement for the ecosystem—and especially for end users—to have first-class support for Helm charts.

[bedge]

I'll re-iterate that this is still an issue for me too.
The inconsistent support of features for artifact types is an ongoing problem.
That said I have little hope that this will change as a result of user requests. I have never seen jFrog fix even proven bugs let alone respond to an improvement request.