fix(deploy): stop the panel from pointing at a tag the build dropped
ci / lint-compose (push) Successful in 3s
ci / lint-actionlint (push) Successful in 1s
ci / lint-shellcheck (push) Successful in 2s
ci / lint-prettier (push) Successful in 3s
ci / lint-ruff (push) Successful in 1s
ci / lint-yaml (push) Successful in 2s
ci / lint-dockerfiles (push) Successful in 1s
ci / scan-deps (push) Successful in 15s
ci / test-backend (push) Successful in 7s
ci / test-frontend (push) Successful in 11s
ci / validate (push) Successful in 3s
renovate-ci / validate-renovate (push) Successful in 12s
ci / build (push) Successful in 37s

USERBOT_IMAGE named userbot:latest, but the build stopped pushing latest when
images became :prod. render_pinned resolves every gcr.forust.xyz reference it
finds in a manifest, not just the ones it rewrites, so that env var made the
whole apply abort with "cannot resolve userbot:latest; applying nothing".

Naming it :prod also makes the build job rebuild userbot, which is what
restores forust/userbot:prod - the tag is listed in the registry but its
manifest 404s, so the image: field in userbots.yaml had nothing to resolve
either.

Found by resolving every digest apply-k8s will need before spending a run on
it: 6 of 8 resolved, and both failures were userbot.
This commit is contained in:
forust committed 2026-09-27 16:14:43 +02:00
1 parent f54589a05c
commit ac0f845da6
1 file changed
+3 -1
+3 -1
View File
@@ -208,7 +208,9 @@ spec:
- name: USERBOT_LEGACY_NAMESPACES - name: USERBOT_LEGACY_NAMESPACES
value: default value: default
- name: USERBOT_IMAGE - name: USERBOT_IMAGE
value: gcr.forust.xyz/forust/userbot:latest # The build pushes main/prod only. The deploy resolves every gcr ref in
# this file, so a :latest here aborts the whole apply as unresolvable.
value: gcr.forust.xyz/forust/userbot:prod
- name: USERBOT_STORAGE_CLASS - name: USERBOT_STORAGE_CLASS
value: local-path-retain value: local-path-retain
- name: USERBOT_DOWNLOADS_HOST_PATH - name: USERBOT_DOWNLOADS_HOST_PATH