From f1d69b0a7a03c119582ccd05c9f55a3cd3c4688d Mon Sep 17 00:00:00 2001
From: Viktor Barzin <vbarzin@gmail.com>
Date: Thu, 7 May 2026 22:38:14 +0000
Subject: [PATCH] [wealthfolio] Flip wealthfolio-sync CronJob image to Forgejo
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

The CronJob has been broken since registry-private lost the
wealthfolio-sync image (last successful run 36+ days ago). The image
is built from /home/wizard/code/broker-sync (the brokerage data sync —
Trading 212, Schwab, Fidelity, IMAP-CSV → wealthfolio).

Set up: viktor/broker-sync repo on Forgejo with .woodpecker/build.yml
that pushes to forgejo.viktorbarzin.me/viktor/wealthfolio-sync. Until
Woodpecker recognises the new repo's webhook, the image was bootstrapped
via 'docker pull viktorbarzin/broker-sync:latest && docker tag … &&
docker push forgejo.viktorbarzin.me/viktor/wealthfolio-sync:latest' so
the CronJob unblocks immediately.
---
 stacks/wealthfolio/main.tf | 7 ++++++-
 1 file changed, 6 insertions(+), 1 deletion(-)

diff --git a/stacks/wealthfolio/main.tf b/stacks/wealthfolio/main.tf
index 672f4ca1..4cbdb010 100644
--- a/stacks/wealthfolio/main.tf
+++ b/stacks/wealthfolio/main.tf
@@ -515,7 +515,12 @@ resource "kubernetes_cron_job_v1" "wealthfolio_sync" {
             }
             container {
               name  = "sync"
-              image = "registry.viktorbarzin.me/wealthfolio-sync:latest"
+              # Phase 4 of forgejo-registry-consolidation 2026-05-07 +
+              # post-cutover wealthfolio-sync rebuild: image is now
+              # produced by /home/wizard/code/broker-sync (Forgejo
+              # viktor/broker-sync, DockerHub viktorbarzin/broker-sync,
+              # Forgejo viktor/wealthfolio-sync as the cluster pull path).
+              image = "forgejo.viktorbarzin.me/viktor/wealthfolio-sync:latest"
               env {
                 name = "IMAP_HOST"
                 value_from {