🚀 Jfrog: Add support for non-Docker artifact types (Helm, RPM, Maven, npm, etc.)

[karthikjeeyar]

Workspace

jfrog-artifactory

🔖 Feature description

The current JFrog Artifactory plugin only supports Docker/container images. Many organizations use Artifactory as a universal artifact repository storing various artifact types including:

• Helm Charts
• RPM Packages
• Maven/Gradle artifacts
• npm packages
• Generic binary artifacts
• Go modules

These artifacts are integral to development workflows, and users need visibility into them through Backstage

Current Behavior

The plugin is hard-coded for Docker images:

• Uses docker://${imageName} package ID format in GraphQL queries
• Looks for Docker-specific files (manifest.json)
• Displays Docker-specific properties (manifest digest, image layers, etc.)

There is no supported method to display other artifact types.

🎤 Context

This is a critical enhancement for organizations using Backstage with JFrog Artifactory as their universal artifact repository. The current Docker-only limitation significantly reduces the plugin's value for many users.

✌️ Possible Implementation

Extend the plugin to support multiple artifact types through a new annotation:

metadata:
  annotations:
    'jfrog-artifactory/artifact-name': 'my-helm-chart'
    'jfrog-artifactory/artifact-type': 'helm'  # or 'rpm', 'maven', 'npm', 'generic', etc.
    'jfrog-artifactory/repository-name': 'helm-local'

Use Cases

• Helm Chart visibility: DevOps teams need to see which Helm chart versions are available for their services
• RPM package tracking: Infrastructure teams managing RHEL/CentOS deployments need RPM visibility
• Library dependencies: Development teams need visibility into internal library versions (Maven, npm, PyPI)

👀 Have you spent some time to check if this feature request has been raised before?

• I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

• I have read the Code of Conduct

Are you willing to submit PR?

None