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
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.
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
Next steps
Last updated
Was this helpful?