Files
test/resources/image_manifests/stx-test-images.yaml
Andrew Vaillancourt 54d11e5f39 Add path_prefix support for registry separation
Enables organizational separation within registry hosts by adding
optional path_prefix configuration. This supports common use cases
like Harbor projects, private registry namespaces, and organizational
hierarchies.

Key changes:
- Add path_prefix field to Registry class with automatic slash
  normalization
- Update DockerSyncImagesKeywords to construct URLs with path prefixes
- Enhance configuration documentation with path_prefix examples
- Add unit tests for path_prefix handling and URL construction

Examples:
- Harbor projects: "project-x/test" -> harbor.com/project-x/test/busybox
- Team namespaces: "team-a" -> registry.com/team-a/my-image

The path_prefix field is optional and trailing slashes are normalized
automatically, making configuration flexible while ensuring correct
URLs.

Change-Id: I4784bc10e61840901baeaef2b69f323956bc23c3
Signed-off-by: Andrew Vaillancourt <andrew.vaillancourt@windriver.com>
2025-08-08 04:35:04 -04:00

28 lines
1.5 KiB
YAML

# ------------------------------------------------------------------------------
# Image Manifest: `stx-test-images.yaml`
#
# This manifest defines Docker images to be synchronized from a source registry
# (e.g., DockerHub) into the local StarlingX registry (e.g., `registry.local:9001`).
#
# Notes:
# - Each image entry must include both `name` and `tag`.
# - Image names must include their full namespace (e.g., `starlingx/stx-platformclients`).
# - Registry URLs and credentials are not listed here. They are defined in:
# `config/docker/files/default.json5`
# - `source_registry` values must match a registry name defined in the Docker config file
# (e.g., "dockerhub", "k8s", "gcr" - not URLs like "docker.io")
#
# Registry resolution priority:
# 1. `manifest_registry_map` with `override: true` (uses registry specified in manifest mapping in config, ignores source_registry in this file)
# 2. `source_registry` field on individual image entry (if override=false or no manifest mapping exists, must match registry name in config)
# 3. `manifest_registry_map` with `override: false` (fallback for images without source_registry)
# 4. `default_source_registry` (final fallback)
# ------------------------------------------------------------------------------
images:
- name: "starlingx/stx-platformclients"
tag: "stx.11.0-v1.0.1"
# source_registry: "dockerhub" # Optional field to specify a custom source registry
- name: "starlingx/stx-keystone"
tag: "master-debian-stable-20250530T120001Z.0"