Here’s a concise version you can copy directly into a Harness support or product ticket: ⸻ Title: Enhancement Request – Expand /har/api/v2/copy to Support All Artifact Types Description: The current Harness Artifact Registry Copy API (/har/api/v2/copy) only supports RPM artifacts. Attempts to copy other types such as NuGet, PyPI, Docker, or Generic return: {"code":"500","message":"validation failed: source artifact is not an RPM"} This limitation prevents unified automation for multi-format artifact migrations and forces separate tooling for each ecosystem. Request: Enhance the /har/api/v2/copy endpoint to support all artifact types managed by HAR, including NuGet/Chocolatey, PyPI, Docker, Generic, npm, and others. The API should validate based on packageType rather than reject non-RPMs, and return a consistent structured response for all types. Business Justification: • Enables consistent, automated artifact migration workflows from JFrog to HAR. • Reduces manual re-publishing and error risk. • Provides feature parity with other enterprise artifact registries. Priority: High — required for enterprise-scale migrations involving multiple package formats.
