Skip to content
For the complete documentation index, see llms.txt. This page is also available as Markdown.
ArtifactsHc Cli

Copy a version

Copy a single artifact version to another Harness registry in a different project or organization, without re-pushing from your local machine.

Copy Version moves one artifact version from a source registry to a target registry within Harness. Use it to promote a validated image from a development registry to a staging registry, or to make an artifact available in a different project without pushing again from your machine.

The artifact's name and version identifier are preserved in the target registry. The operation copies the version data only; it does not copy registry configuration, policies, or metadata from the source registry.

If you need to use a different artifact name in the target registry, download the artifact and push it under the new name.

Before you begin

To copy a version, your role must include:

  • View permission on the source registry

  • Create/Edit permission on the target registry

If the Copy Version option does not appear, ask your account administrator to review your role assignments. Go to RBAC and permissions for the full permission list.

Copy a version

1

Open the artifact's version list

In the left navigation, select Artifacts. Click the artifact name to open its version list.

Alternatively, navigate to the source registry, select the Packages tab, and click the artifact.

2

Open the row menu for the version

Find the version you want to copy. Click the three-dot menu (⋮) at the end of that row.

Copy Version vs Copy Command

The row menu shows both Copy Version and Copy Command. Copy Command copies the client pull command text to your clipboard. Copy Version opens the dialog to move the version to another registry. Select Copy Version.

3

Choose the target registry

The Copy Version dialog shows the source registry, artifact name, and version as read-only fields.

Under Target, select the Organization, Project, and Registry where the version should be copied. If the Registry dropdown is empty, select an organization and project first; the registry list is scoped to the project you choose.

The target registry must be the same package type as the source. A Docker version can only be copied to another Docker registry.

4

Confirm the copy

Select Copy Version to start the operation, or Cancel to exit without changes.

When the copy completes, the version appears in the target registry under the same artifact name and version identifier.

Copy with the hc CLI

To copy versions from the command line or from automation, use the hc CLI. Go to CLI reference for syntax and examples.

For Docker images, you can also use skopeo to copy between registries. Authenticate to each registry using the identity token from Setup Client, with your email as the username. Go to the skopeo documentation for installation and usage.

Troubleshooting

Can I rename the artifact while copying it?

No. Copy Version preserves the original package name and version identifier. To use a different name, download the artifact and push it under the new name in the target registry.

Can I copy more than one version at a time?

No. Copy Version copies one version at a time. For bulk operations, repeat the copy for each version or use skopeo for Docker images.

The target Registry dropdown is empty

The dropdown shows only registries that match the package type of the source artifact and exist in the selected project. Create a registry of the matching type in the target project, then retry the copy.

Copy Version fails with a permissions error

Your role on the target registry may not include Create/Edit. Ask your account administrator to assign a role with Create/Edit permission on that registry. Go to RBAC and permissions to review what permissions are required.

Next steps

Last updated

Was this helpful?