tools/get_image_refs.py: remove the proxy part for the OCI artifacts to keep only the real artifact source (!7810) · Merge requests · Sylva-projects / sylva-core

What does this MR do and why?

Remove the proxy part of the oci artifact references and replace them by the upstream registry.

It is already implemented by the normalize_oci_url function, but it requires to pass to get_image_refs an input file describing the mapping between the "proxied" oci URL and the "normalized" oci URL (--url-remap-config parameter). When the input file is missing, the function proposes a default mapping but it won't work all the time, depending on the actual values used for the deployment.

This MR proposes to normalize the oci URL based on the definition of the registry mirrors passed in the values, when the input file is not provided.

Closes #4038 (closed)

Test coverage

Result in https://gitlab.com/sylva-projects/sylva-core/-/jobs/14354451273

{
    "oci_artifacts": {
        "kustomizations": [
            "oci://registry.gitlab.com/sylva-projects/sylva-core/kustomize-units:0.0.0-git-bbc0bc1c"
        ],
        "helm_charts": [
            "oci://registry.gitlab.com/sylva-projects/sylva-core/sync-openstack-images:0.8.1",
            "oci://registry.gitlab.com/sylva-projects/sylva-core/workload-team-defs:0.7.5",
            "oci://registry.gitlab.com/sylva-projects/sylva-core/oauth2-proxy:10.0.0",
            "oci://registry.gitlab.com/sylva-projects/sylva-core/tenant:v7.1.1",
...

CI configuration

Below you can choose test deployment variants to run in this MR's CI.

Click to open to CI configuration

Legend:

Icon	Meaning	Available values
☁️	Infra Provider	`capd`, `capo`, `capm3`
🚀	Bootstrap Provider	`kubeadm` (alias `kadm`), `rke2`, `okd`, `ck8s`
🐧	Node OS	`ubuntu`, `suse`, `na`, `leapmicro`
🛠️	Deployment Options	Deployment option list and description
🎬	Pipeline Scenarios	Available scenario list and description
🟢	Enabled units	Any available units name, by default apply to management and workload cluster. Can be prefixed by `mgmt:` or `wkld:` to be applied only to a specific cluster type
🔴	Disabled units	Any available units name, by default apply to management and workload cluster. Can be prefixed by `mgmt:` or `wkld:` to be applied only to a specific cluster type
🏗️	Target platform	Can be used to select specific deployment environment Available platform list and description
⚡	Pipeline control	`autorun`, `manual` or `blocking`. Can be used to override global config and start a deployment pipeline the required way

Global config for deployment pipelines

autorun pipelines
allow failure on pipelines
record sylvactl events

Notes:

Enabling autorun will make deployment pipelines to be run automatically without human interaction
Disabling allow failure will make deployment pipelines mandatory for pipeline success.
if both autorun and allow failure are disabled, deployment pipelines will need manual triggering but will be blocking the pipeline

Be aware: after configuration change, pipeline is not triggered automatically. Please run it manually (by clicking the run pipeline button in Pipelines tab) or push new code.

Edited May 28, 2026 by Thomas Morin

tools/get_image_refs.py: remove the proxy part for the OCI artifacts to keep only the real artifact source

What does this MR do and why?

Related reference(s)

Test coverage

CI configuration

Global config for deployment pipelines

Merge request reports