Using Vendor-Specific APIs

Upload resources into JFrog Artifactory and Sonatype Nexus repositories during transfer, using each server's own repository APIs.

Artifact servers such as JFrog Artifactory and Sonatype Nexus Repository host many repository types behind their own APIs. OCM’s vendor uploaders read the type of the target repository from the server and upload each resource the way that repository type expects, so consumers fetch it with their usual tools.

Choose your server

ServerRepository typesGuide
JFrog Artifactoryhelm, maven, npm, genericJFrog Artifactory
Sonatype Nexus Repository 3helm, maven2, npm, rawSonatype Nexus

How vendor uploaders work

  1. An uploader rule matches resources by their access type in the source component version. The first matching rule wins, see Uploader configurations.
  2. At upload time the uploader reads the repository type from the server.
  3. It uploads the resource the way that repository type expects.
  4. It rewrites the resource in the target component version to a Helm/v1 access for charts, or a Wget/v1 access for files and packages. A genericBlobDigest/v1 SHA-256 or SHA-512 source digest is verified.
JFrog Artifactory
Upload resources into JFrog Artifactory helm, maven, npm and generic repositories during transfer, with credentials and overwrite rules.
Sonatype Nexus
Upload resources into Sonatype Nexus Repository 3 hosted helm, maven2, npm and raw repositories during transfer, with credentials and overwrite rules.