ci: inject TUNNEL_TOKEN from secrets into deploy env before scp #132
No reviewers
Labels
No labels
architecture
backend
bug
ci
config
database
docker
documentation
duplicate
enhancement
frontend
help wanted
invalid
issue-25
issue-26
issue-42
issue-65
issue-67
issue-82
migrations
p0-critical
p1-high
p2-medium
p3-low
performance
quality
question
security
state-management
testing
timezone
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
fastie81/honbu-manager!132
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix/inject-tunnel-token"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Fix: deploy-prod was overwriting prod's .env.prod with the repo copy, which lacks the Cloudflare tunnel token, so every CI deploy recreated the tunnel with an empty token and it crash-looped (observed: RestartCount=8). Same latent issue in deploy-test.
Change: render secrets.TUNNEL_TOKEN into .env.prod / .env.test in both deploy jobs (alongside the existing Google secret rendering) before scp, so the tunnel always receives its token on deploy. The token lives in the Forgejo Actions secret TUNNEL_TOKEN.
This was surfaced by running the full pipeline to prod for the first time (v3.4.4).