Move non-secret runner env vars to deployment spec #181

Merged

eblume merged 1 commit from feature/runner-env-refactor into main

2026-02-13 10:29:24 -08:00

eblume commented

2026-02-13 10:28:37 -08:00

Owner

Summary

Move FORGEJO_URL, RUNNER_NAME, and RUNNER_LABELS from ExternalSecret template to deployment env vars
ExternalSecret now only contains the actual secret (RUNNER_TOKEN)
Image version changes in RUNNER_LABELS now trigger automatic pod rollouts

Deployment

Merge this PR
argocd app sync forgejo-runner — the deployment spec change will auto-roll the pod

No manual restart needed — that's the whole point :)

🤖 Generated with Claude Code

## Summary - Move FORGEJO_URL, RUNNER_NAME, and RUNNER_LABELS from ExternalSecret template to deployment env vars - ExternalSecret now only contains the actual secret (RUNNER_TOKEN) - Image version changes in RUNNER_LABELS now trigger automatic pod rollouts ## Deployment 1. Merge this PR 2. `argocd app sync forgejo-runner` — the deployment spec change will auto-roll the pod No manual restart needed — that's the whole point :) 🤖 Generated with [Claude Code](https://claude.com/claude-code)

eblume added 1 commit

2026-02-13 10:28:37 -08:00

Move non-secret runner env vars from ExternalSecret to deployment f0822ad878

FORGEJO_URL, RUNNER_NAME, and RUNNER_LABELS are not secrets — they were
bundled into the ExternalSecret template for convenience. Moving them to
the deployment spec means changing the image version (in RUNNER_LABELS)
will trigger an automatic pod rollout instead of requiring a manual restart.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>