Skip to main content

What's Supported with Artifact Registries

Last updated on
info

To enable Harness Artifact Registry in your account, contact your sales representative or reach out to the team at ar-interest@harness.io.

Registries​

Harness Artifact Registry supports a variety of registry types, and new ones are often added. We currently support the registry types listed below.

Supported registry types​

These are the currently supported registry types.

  • Docker: Your go-to for container images.
  • Helm: Perfect for managing Kubernetes applications.
  • Generic: Flexible for all your needs.
  • Maven: Essential for Java projects.
  • Python: For your Python packages using pip, Poetry, or uv.
  • NPM: JavaScript package management.
  • NuGet: .NET package manager.
  • RPM: Red Hat package management.
  • Gradle: Streamline your build automation.
  • SBT (Scala Build Tool): Tailored for Scala and Java projects.
  • Dart: For all your Dart and Flutter packages.
  • PHP Composer: Private Composer packages with Packagist-compatible workflows.
  • Go: Support for Go modules.
  • Cargo: Rust package management.
  • Hugging Face: Machine learning models and datasets.
  • Conda: To support your Python and R packages.

Coming Soon​

  • Alpine: Alpine Linux packages.
  • RubyGems: Ruby packages.
  • Conan: C/C++ packages.

Platform Support​

Harness Artifact Registry (HAR) is seamlessly integrated with the Harness Platform, offering you robust features and capabilities.

Role-based Access Control (RBAC)​

HAR has full RBAC support. Simply go to your project settings, create a new role, and scroll to the bottom to find the supported HAR resources.

This comes with 3 roles automatically created for you:

  • Artifact Registry Viewer: Bind to this role to allow a user to view registries and its contents.
  • Artifact Registry Contributor: Bind to this role to allow a user to push and pull from registries.
  • Artifact Registry Admin: Bind to this role to allow a user full admin access to the AR module.

Continuous Integration (CI)​

HAR provides native support for pushing images to Docker registries, eliminating the hassle of managing external connections. To set up, use the Build and Push to Docker step in a CI stage and select Harness Artifact Registry as your registry type. From there, simply choose the registry and image you want to use from convenient, pre-populated lists in the fields below.

Learn more about streamlining your CI process with our guide to Build and Push to Docker

Dependency Firewall​

Dependency Firewall is how Harness Artifact Registry applies supply chain guardrails when you use upstream proxy registries. External packages are checked against your organization’s policies before they are cached in Harness, so you can enforce rules on things like vulnerabilities, licenses, and package age in one place instead of only relying on downstream scans. It is part of the same Policy as Code model used across the platform.

For a full description of how it works, the dashboard, and how to configure policies, go to Dependency Firewall.

Harness CLI​

The Harness CLI (hc) is the command-line way to work alongside Artifact Registry: you can inspect and manage registries and artifacts, handle metadata and lifecycle operations where supported, evaluate dependencies against your registry’s security rules, and configure local package manager clients (for example npm) to talk to Harness registries. It is intended for automation, scripts, and day-to-day tasks without opening the UI for every change.

Install the CLI from Install the Harness CLI. For Artifact Registry–specific commands and examples, go to Manage artifacts and registries with the CLI.

Continuous Deployment (CD)​

Speed up your deployment process by using HAR as your Artifact sources in CD without the need for separate registry connectors.

Learn more about CD services.