Viktor Barzin 4a3ca572e8 fire-planner: imagePullPolicy=Always on alembic-migrate init container ... After a rollout-restart, the main container (default Always for :latest) pulled the new image with alembic 0003, but the init container defaulted to IfNotPresent and reused a cached old image lacking 0003 → "Can't locate revision identified by '0003'" → CrashLoopBackOff. Setting Always on the init container so both containers stay in lockstep across rollouts. Longer term we should switch the deployment to 8-char git-SHA tags per the cluster policy in .claude/CLAUDE.md, but this unblocks the Wave 1 deploy in the meantime.		2026-05-22 14:16:40 +00:00
..
main.tf	fire-planner: imagePullPolicy=Always on alembic-migrate init container	2026-05-22 14:16:40 +00:00
terragrunt.hcl	fire-planner: add stack, Vault DB role, dashboard, DB	2026-04-25 17:27:19 +00:00