Skip to content
For the complete documentation index, see llms.txt. This page is also available as Markdown.
Artifact RegistryGetting StartedRegistry Types

Create a registry

Create a registry to store and manage artifacts of any supported format, at account, organization, or project scope, and set up client access.

A registry is the storage unit in Harness Artifacts. Each registry holds artifacts of a single format: Docker images, Maven packages, npm modules, Helm charts, and so on. You create one registry per format and give it a name that is unique within its scope.

Registries can be created at Account, Organization, or Project scope. The scope determines who can see and use the registry. Navigate to the scope you want before you create the registry.

Before you begin

Your role must include Create/Edit permission on Artifact Registry at the scope where you want to create the registry. Go to RBAC and permissions to review permission requirements.

Create a registry

  1. In the left navigation, select Registries.

  2. Select Create registry.

  3. In the Create a new artifact registry drawer, select the registry type that matches the package format you want to store.

  4. Enter a Registry Name.

    Registry names must start with a letter and can only contain lowercase letters, numbers, underscores (_), hyphens (-), and periods (.).

  5. Optionally, enter a Description.

  6. Set Visibility to Private or Public.

    • Private: Only users or service accounts with the required permissions can view and pull from this registry.

    • Public: Anyone can view the registry contents and pull artifacts without authentication.

    Public visibility requires a feature flag

    The Public option is gated by the PL_ALLOW_TO_SET_PUBLIC_ACCESS feature flag. If the option does not appear, contact Harness Support to enable the flag, then go to Account Settings > Authentication and turn on Allow public resources. Both steps are required.

  7. Select Create registry.

The new registry opens immediately. Select Setup Client from the row menu to get the authentication commands for your format.

Supported registry types

Harness Artifacts supports the following formats. Select the type that matches your toolchain when you create the registry.

Format
Use for

Docker

Container images (OCI-compatible)

Helm OCI

Helm charts stored as OCI artifacts

Helm HTTP

Classic Helm chart repositories (helm repo add / helm pull)

Maven

Java packages (Maven, Gradle, SBT)

npm

JavaScript and Node.js packages

Python / PyPI

Python packages (pip, Poetry, uv)

NuGet

.NET packages

Cargo

Rust packages

Go

Go modules

Generic / Raw

Arbitrary files by path

RPM

Red Hat, CentOS, Fedora packages

Debian / APT

Debian and Ubuntu .deb packages

Alpine / APK

Alpine Linux packages

Wolfi / APK

Wolfi Linux packages

Terraform

Infrastructure as Code modules and providers

Terraform Backend

Terraform remote state backend

Hugging Face

Machine learning models and datasets

Conda

Python and R packages (Anaconda-compatible)

Dart

Dart and Flutter packages

PHP Composer

PHP packages (Packagist-compatible)

Swift

Swift packages (SwiftPM)

Conan

C and C++ packages

Ruby / RubyGems

Ruby gems

R / CRAN

R packages (CRAN-compatible)

Puppet

Puppet modules (Puppet Forge-compatible)

Go to Supported formats for the full list with protocol details and client setup links.

What's next

Last updated

Was this helpful?