jf helm push with build-info fails to set properties on virtual Helm OCI repositories (404)

Open
#3,663 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
go
Domain
api, cli

Research direction

Start at the jf helm push build-info flow described in the issue, then compare how jf docker resolves a virtual repository before setting build properties, including the referenced jfrog-cli-core PR #1393. Reproduce the command against virtual and local Helm OCI repositories; done means the virtual-repository push attaches build properties without a 404 and local-repository behavior still works.

Written by the indexing model from the issue text.

Description

bug

Is your feature request related to a problem? Please describe.
Yes. When jf helm push is run against a virtual Helm OCI repository with --build-name and --build-number, the Helm push succeeds, but the post-push build-info step fails to attach build properties and returns 404.

example:
jf helm push my-app-1.2.3.tgz \ oci://artifactory.example.com/helm-virtual \ --build-name my-app-build --build-number 42

Observed behavior:

  1. OCI push succeeds.

  2. CLI collects build info and resolves artifacts via AQL against helm-virtual.

  3. CLI calls the Storage Properties API against the virtual repo key:
    PUT /api/storage/helm-virtual/my-app/1.2.3?properties=build.name=...;build.number=...

  4. Artifactory returns 404 Not Found.

  5. CLI logs:
    Failed to set build properties on manifest folder: server response: 404

  6. Build info is saved locally, but build properties are not attached to the artifacts.
    The same command works when pushing directly to a local Helm OCI repo (helm-dev-local, helm-release-local), where the property PUT returns 204.

Describe the solution you'd like to see
When jf helm push is used with build-info flags against a virtual Helm OCI repository, the CLI should resolve the physical local repository before setting build properties — similar to existing behavior already supported in 'jf docker' in the CLI. ( for Docker in jfrog-cli-core PR #1393, which filters virtual-repo layer handling to the default deployment repository when setting build properties. Helm OCI build-info should follow the same principle.)

Dominant language
Go
Stars
595
Forks
307
Avg merge
4d 17h
Merged PRs (30d)
17

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from jfrog/jfrog-cli

All issues in jfrog/jfrog-cli

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.