Skip to main content

Secondary Registry

This page explains how to enable a secondary registry endpoint.
This function pushes a copy of the container image artifact to the defined OCI registry.

In order for Secondary Registry to work properly, you must follow the next steps:

1. Add Variable (in CI platform)​

shamanops_secondary_registry_url *
This value is provided by the customer and refers to the secondary container registry specific URL.
Example: us-east1-docker.pkg.dev/sbox-shamanops/shamanops-sbox

shamanops_secondary_registry_user *
This value is provided by the customer and refers to the username to access the secondary container registry.
Example:   _json_key_base64

2. Add Secrets 🔒 (in CI platform)​

shamanops_secondary_registry_password *
This value is provided by the customer and refers to the token to access the secondary container registry.

note

If you are going to use a Google Artifact Registry please check de Important Points section