From 98b7ef40fd6a69bee9220a1290fbfe5ce171dfac Mon Sep 17 00:00:00 2001 From: Viktor Barzin Date: Sun, 17 May 2026 00:36:23 +0000 Subject: [PATCH] broker-sync(fidelity): un-suspend monthly CronJob The provider now emits delta gains-offset DEPOSITs (broker-sync@98c4729) which is the simple accumulate-gains approach Viktor signed off on: each monthly scrape captures (current_pot, real_contribs), and we emit a single DEPOSIT/WITHDRAWAL sized to growth-since-last-scrape. dav_corrected handles the dashboard math. Next scheduled run: 2026-05-20 05:00 UK. Manual trigger via 'kubectl -n broker-sync create job fid-now --from=cronjob/broker-sync-fidelity'. --- stacks/broker-sync/main.tf | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/stacks/broker-sync/main.tf b/stacks/broker-sync/main.tf index f36579d0..59cbcdb1 100644 --- a/stacks/broker-sync/main.tf +++ b/stacks/broker-sync/main.tf @@ -668,8 +668,13 @@ resource "kubernetes_cron_job_v1" "fidelity" { concurrency_policy = "Forbid" successful_jobs_history_limit = 3 failed_jobs_history_limit = 5 - # Suspended until the broker-sync image ships with Playwright + Chromium. - suspend = true + # Unsuspended 2026-05-17 after the delta gains-offset emission landed + # (broker-sync @98c4729). Manual trigger: + # kubectl -n broker-sync create job fid-now \ + # --from=cronjob/broker-sync-fidelity + # NB: storage_state expires every 30-90 days — see code-r9n for the + # chrome-service-driven re-seed runbook. + suspend = false job_template { metadata {} spec {