Skip to content

ci: mirror synmetrix images to registry.fraios.dev#60

Open
acmeguy wants to merge 1 commit into
mainfrom
fix/registry-mirror
Open

ci: mirror synmetrix images to registry.fraios.dev#60
acmeguy wants to merge 1 commit into
mainfrom
fix/registry-mirror

Conversation

@acmeguy

@acmeguy acmeguy commented Jul 7, 2026

Copy link
Copy Markdown

Enables the registry.fraios.dev mirror so the ArgoCD Image Updater can track synmetrix images (its only configured registry is registry.fraios.dev; the Docker Hub quicklookup/* names have no registry entry, so auto-deploy never fired). Matches the working fraios app pattern (data-services, memory-service). Uses FRAIOS_REGISTRY_USERNAME/FRAIOS_REGISTRY_PASSWORD. Trailing Dockerfile comments force a one-time rebuild of cube/actions/hasura to populate the registry.

Prerequisite: the FRAIOS_REGISTRY_USERNAME/FRAIOS_REGISTRY_PASSWORD repo secrets must be set before merge, or the build's registry login fails.

🤖 Generated with Claude Code

Enable the registry.fraios.dev mirror in the build pipeline so the ArgoCD
Image Updater (whose only configured registry is registry.fraios.dev) can
track synmetrix images by digest — the Docker Hub quicklookup/* images have
no registry entry in the updater config, so auto-deploy never fired for them.

Every built image now pushes to BOTH Docker Hub (existing deployments) and
registry.fraios.dev/fraios/synmetrix-* (matches the working fraios app
pattern: data-services, memory-service, etc.). Uses the FRAIOS_REGISTRY_*
secrets, same as the other fraios build workflows.

The trailing Dockerfile comments force a one-time rebuild of cube/actions/
hasura so they populate registry.fraios.dev under this pipeline.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant